- From: Martin Thomson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 27 Feb 2024 23:12:42 +0000
- To: public-patcg@w3.org
The [PDF of the report](https://iabtechlab.com/wp-content/uploads/2024/02/Privacy-Sandbox-Fit-Gap-Analysis-PUBLIC-COMMENT-RELEASE.pdf) might be a more useful link. Google have also provided a [response](https://docs.google.com/document/d/10608Tp57alonCiBN9D2-0UfV_C6FFLsV5nh6sBaA5rA/preview?__s=ek7glnvk3e0k2iq1ig0f) that might contain useful corrections. In looking into this, the report primarily concentrates on Protected Audience, so while there are concerns about attribution, they are buried. The section on reporting includes things like reach and frequency. The first direct discussion of attribution starts on page 50, so I recommend starting there. My takeaways: * Because this is primarily about Protected Audience, the attribution reporting stuff is a little garbled. * This only talks about event-level and summary reports in ARA. * Delays are undesirable. * Noise is undesirable. * Rounding/quantization is undesirable. * Cross-device attribution is desirable. * Multi-touch attribution is desirable. * App-to-web attribution is desirable. * Anti-fraud mitigations are desirable. -- GitHub Notification of comment by martinthomson Please view or discuss this issue at https://github.com/patcg/meetings/issues/167#issuecomment-1967882113 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 27 February 2024 23:12:43 UTC