demo · v132
Ad-tech migration checklist
If you ran an Attribution Reporting debug pipeline before Chrome 132 you almost certainly set up an ar_debug cookie loop. The new relaxation means most of that ceremony is dead code. Tick each box; the progress bar tells you how far through cleanup you are.
0 / 7
- Remove the
Set-Cookie: ar_debug=1; Path=/; Secure; HttpOnly; SameSite=Noneresponse from your debug-eligible endpoints.The cookie is no longer required when third-party cookies are partitioned. Sites with partitioning enabled get verbose reports without it. - Audit your cookie-banner logic for ar_debug carve-outs.If your CMP rejected the cookie under "necessary only" mode you can drop the special case — the API no longer hard-depends on it.
- Update your privacy disclosure / cookie policy.Drop the
ar_debugline from the cookie table on your site. Most policy generators now omit it by default. - Re-test verbose reports under storage partitioning.Open chrome://attribution-internals, fire a registration in an iframe under partitioning, confirm the verbose debug report still arrives at
/.well-known/attribution-reporting/debug/verbose. - Update your ARA debug dashboard to surface the
partitioned-cookies-onlystream.Reports may now arrive withoutsource_debug_key/trigger_debug_keyfields when ar_debug is absent. Make sure your decoder doesn't crash on missing fields. - Document the new eligibility rule for your buyer-side integration team."Cookie-based debug is now available if third-party cookies are AVAILABLE (including partitioned) AND the caller is enrolled." Pin this to your internal wiki.
- Drop ar_debug from your end-to-end test fixtures.If your e2e suite forces the cookie in CI to enable debug output, you can remove that fixture step now — partitioning gives you the same result.
progress saved to localStorage