← Back to release summary

Attribution Reporting API Feature (Change To ar_debug Cookie Requirement)

Category
Miscellaneous
Type
New or changed feature
Status
Proposed (Chrome Proposed)
Intent stage
None

Summary

We are landing the following change to the Attribution Reporting API focused on: * making it easier to receive API cookie-based debug reports

Motivation

Currently the API allows cookie-based debug reporting only if third-party cookies are available AND the API caller sets the special unpartitioned ar_debug cookie. This change makes it easier for API callers to use the API’s cookie-based debug reporting by allowing them to receive cookie-based debug reports as long as they have third-party cookie accessibility on the source/destination sites, and they no longer need to actually set the ar_debug cookie. Third-party cookie accessibility is equivalent to the API caller’s ability to set the ar_debug cookie. This change makes it easier for API callers to receive cookie-based API debug reports (i.e. lower chance of misconfigured ar_debug cookies).

Standards & signals

Explainers: https://github.com/WICG/attribution-reporting-api/issues/1440

View on chromestatus.com