John Delaney
John Delaney
Another idea for discussion would be adjusting the limit while keeping the concept of limiting "simultaneous" sources: > 100 distinct destination sites per-{source site, reporting origin}, applied at source time...
> Impression should be an event source. I suppose we can have 2 1*1 pixels to register both attribution sources. Please correct me if I am wrong. Here is the...
I think this has very clear benefits still. We can file a layering issue against PCM as it would increase a large difference in API shape.
Generally, the party responsible for serving the ads to the page is the one that gets reports. And similarly they are responsible for setting the impression and conversion data fields....
> Say a publisher and advertiser do a direct deal and the adops team on publisher's side set a campaign for this in Google Ad Manager. The campaign runs on...
Per your comment above, if the impression origin and the reporting origin agree on an id to use that is understandable by both parties, I can see how this would...
To clarify on my above [comment](https://github.com/WICG/conversion-measurement-api/issues/96#issuecomment-806330826), by "conversion event info" I was specifically referring the the 3 bits of metadata set by the advertiser site. Sorry for any confusion due...
One simpler alternative is to just use HTTP caching to allow for key rotation: The browser would parse keys of the format: ``` [{ id: "key_1", key: "" }, {...
Would it be possible to document limits either in the explainer/spec as part of this change? Ideally we could put it in the spec, although I am not sure if...
Agreed on the points above. To go a step further, I wonder if we could just accept expiry as an integer number of days. The View explainer requires expiries to...