johnwilander
commented
5 years ago Hello everyone,
not sure if that was covered by any of the other issues that were raised, but what happens if a conversion event is scheduled but the browser is not used at this time?
In the case of our implementation, it's a timer and it will fire as soon as it can after it's scheduled.
E.g. lets say the conversion happens on a friday, the event is scheduled for saturday but the browser is only used on monday again. that could lead to a different kind of issues.
Hence: wouldn't it be better if the conversion is not fired by the browser but by a server that belongs to the browser company?
We include the browser vendor in the threat model and do not think the vendor should have insights into all users' ad clicks and conversions.
in this case the conversion could be fired immediatly or near-immediatly and would not have issues with the topic if the browser is still "active". also it would solve the problem with transmitting the IP address of the user ...
Except now the browser vendor gets the IP address and all ad clicks + conversions by that user. We don't want that.
Hello everyone,
not sure if that was covered by any of the other issues that were raised, but what happens if a conversion event is scheduled but the browser is not used at this time? E.g. lets say the conversion happens on a friday, the event is scheduled for saturday but the browser is only used on monday again. that could lead to a different kind of issues.
Hence: wouldn't it be better if the conversion is not fired by the browser but by a server that belongs to the browser company? in this case the conversion could be fired immediatly or near-immediatly and would not have issues with the topic if the browser is still "active". also it would solve the problem with transmitting the IP address of the user ...