Announcement: 📢 M132 Chrome updates for ARA

1,180 views

Skip to first unread message

Patti Shin

unread,

Jan 7, 2025, 11:05:01 AM Jan 7

to Attribution Reporting API announcements

Greetings API testers! 👋

Wishing you a happy new year! We would like to share the following changes that are coming up in M132 Chrome for Attribution Reporting API.

What are the changes?

Removing the ar_debug requirement for cookie-based debug reporting ( Explainer )
Aggregatable named budgets ( Explainer )

How does this affect you?

Change #1: Wherever you have the following implemented in your integration to request debug reports for Attribution Reporting, it's safe to no longer set the ar_debug cookie .

Set - Cookie : ar_debug = 1 ; SameSite = None ; Secure ; Path =/; HttpOnly

Before M132 , 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.

With this change starting in M132 , you no longer need to set the ar_debug cookie! You can use the API’s cookie-based debug reporting and retrieve those debug reports as long as you have third-party cookie accessibility on the source / destination sites where you are requesting debug reporting.

Note that if your configuration continues to set the ar_debug cookie after this change is live it will not cause any errors or issues.

Change #2: Starting in M132, you can specify the maximum amount of L1 contribution budget you would like to allow for any given type of conversion event.

Before M132 , You would need to keep track of how much L1 contribution budget you plan to use across conversion events based on your allocation choice. The L1 contribution budget limits the total amount of information that can be attributed to any single ad impression (i.e. ad click or view) and currently has a limit of 65,536.

With this change starting in M132 , you can pre-allocate and specify how much of the L1 contribution budget you would like to allow for measuring different types of events.

Note that this change does not change the overall L1 contribution budget limit of 65,536 but makes it easier to pre-allocate the L1 budget across various conversion event types.

That's a wrap! If you have any questions or comments, reply to this post or open an issue in the Privacy Sandbox Dev Support repository on GitHub.