- From: Erik Taubeneck via GitHub <sysbot+gh@w3.org>
- Date: Sun, 15 May 2022 18:15:37 +0000
- To: public-patcg@w3.org
The primary consideration here is _cross site_ activity, which currently (or previously, for some user-agents) rely on third party cookies / device identifiers. Attribution - typically formalized as joining a _source event_ on one site a _trigger event_ on another site - is a clear instance of cross site activity. The reason I separate out "click attribution measurement" and "impression (click, view, etc) attribution measurement" is just reflecting the current proposed APIs treat this differently. [Private click measurement](https://privacycg.github.io/private-click-measurement/) only supports attributing _trigger events_ after a click, and the [event level attribution API](https://github.com/WICG/conversion-measurement-api/blob/main/EVENT.md) allows for more entropy to be included post click than post view. Reach and frequency is also a use case that is worth considering here, as the goal is to count the unique number people to which impressions are shown, cross site (and often cross platform.) Are there use cases for "basic reporting" that require cross site activity? It seems like the ones listed (views, clicks, CTR, viewability etc.) could be handled within the first party context. -- GitHub Notification of comment by eriktaubeneck Please view or discuss this issue at https://github.com/patcg/meetings/issues/51#issuecomment-1126990077 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 15 May 2022 18:15:38 UTC