Thanks Akash.
LGTM1 % sending out an email to the
[email protected] group.
On 11/6/23 4:52 PM, Akash Nadan wrote:
Hi Mike,
I've spot checked some popular publisher sites, and can see that the
ar_debug cookie is being set on these sites. Additionally, we are
planning on sending out an email to the
[email protected] email group later this
week, to notify them of the upcoming change.
Thanks,
Akash
On Monday, November 6, 2023 at 9:40:50 AM UTC-8 Mike Taylor wrote:
On 11/3/23 6:12 PM, 'Akash Nadan' via blink-dev wrote:
Contact emails
[email protected], [email protected]
Explainer
Attribution Reporting with event-level reports
<https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md>
Attribution Reporting API with Aggregatable Reports
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md>
Aggregation Service for the Attribution Reporting API
<https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATION_SERVICE_TEE.md>
Specification
https://wicg.github.io/attribution-reporting-api/
<https://wicg.github.io/attribution-reporting-api/>
Blink component
Internals > AttributionReporting
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting>
Summary
We plan on landing one change to the Attribution Reporting API
focused on:
*
further gating for trigger verbose debug reports
o
Trigger verbose debug reports were only gated by the
presence of the ar_debug cookie (3PC) at trigger
registrations. To improve privacy, this change further
gates trigger verbose debug reports by the presence of
the ar_debug cookie at source registrations. Therefore,
in order to receive trigger verbose debug reports, the
ar_debug cookie needs to be present at both source and
trigger registrations.
Explainer changes
*
Require ar_debug cookie presence on source registrations for
trigger verbose debug reports
<https://github.com/WICG/attribution-reporting-api/pull/1088>
Spec changes
*
Require ar_debug cookie presence on source registrations for
trigger verbose debug reports
<https://github.com/WICG/attribution-reporting-api/pull/1088>
Risks
Interoperability and Compatibility
This change is backwards incompatible as developers need to
ensure the special ar_debug cookie is present at source
registrations as well in order to receive trigger verbose debug
reports. We consider this less concerning as it’s very likely
that developers already set the ar_debug cookie on source
registrations for debugging purposes while third-party cookies
are available. Developers may expect to receive fewer trigger
verbose debug reports in a more privacy-preserving way.
Is there any way for you to do a spot check on some sites that are
known to use the API to confirm this intuition? Have we done any
outreach or considered added something like a DevTools issue to
tell developers why they're no longer receiving verbose debug reports?
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
All except Android WebView
Is this feature fully tested by web-platform-tests
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?
Yes
Estimated milestones
Chrome 120
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5092796566601728
<https://chromestatus.com/feature/5092796566601728>
Links to previous Intent discussions
Previous I2S:
Intent to Ship: Attribution Reporting API
<https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY>
Intent to Ship: Attribution Reporting features M117
<https://groups.google.com/a/chromium.org/g/blink-dev/c/nWF61c8xu-M/m/uMmH1ewcAQAJ>
Intent to Ship: Attribution Reporting features M118
<https://groups.google.com/a/chromium.org/g/blink-dev/c/Mh-mJiyJZFk/m/HlgzpphYBQAJ>
Intent to Ship: Attribution Reporting features M119
<https://groups.google.com/a/chromium.org/g/blink-dev/c/6e44SBtEtcQ>
--
You received this message because you are subscribed to the
Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/db5ba937-4a1e-4dc1-a2ef-44559f967a9en%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/db5ba937-4a1e-4dc1-a2ef-44559f967a9en%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/35095c70-3f45-47aa-bfc0-b1ed4d0da78e%40chromium.org.
