We are landing the following changes to the Attribution Reporting API focused on: * improving debugging capabilities
This change is based on ad-tech feedback and the need to support debugging capabilities after 3rd party cookie deprecation. Currently the API supports debug reports that are tied to 3rd party cookies. In order for an API caller to receive a debug report of any kind they need to make sure a specific 3rd party cookie (i.e. ar_debug) is properly set. The API will check to make sure this cookie is set before providing any kind of debug report. Once 3rd party cookies are deprecated these debug reports will no longer be available. This change is so the API can continue to provide some form of debugging information after 3rd party cookie deprecation. This is a new report type that is not tied to 3rd party cookies and provides similar debug information. This feature allows API callers to request and receive debug signals in aggregate form. This feature is very similar to current Aggregate Reports supported by the API, except these new reports will be specifically for debug signals. This new feature will allow API callers to continue receiving debugging information even after 3rd party cookie deprecation.
Explainers: https://github.com/WICG/attribution-reporting-api/blob/main/aggregate_debug_reporting.md