Option for reports to be sent to click-destination also #48
Comments
|
Hi! This has been mentioned earlier and our intention is for the modern JavaScript reporting API to allow for reports to either endpoint or both. |
|
@johnwilander I wonder if this is an opportunity to align with our conversion measurement proposal which has a separate field for registering a reporting endpoint on the ad impression side. In our case we want to allow arbitrary reporting endpoints but for Safari's implementation it could be a restricted subset which just includes the source or destination site. In our case there was a goal to have the two parties (publisher / advertiser) agree where the reports were sent which is why there are mechanisms on both impression / conversion registration for configuring this. |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the advertiser (click-destination controller) will often be paying the publisher for conversions shouldn't they also receive the conversion reports? As usual no cookies, asynchronous delivery etc. so no privacy impact, but it would help with getting agreement with what is owed, especially once the fraud detection is there.
This may have been mentioned before, for which apologies if so.
The text was updated successfully, but these errors were encountered: