demo · v130

Migration checklist

For ad-tech teams shipping the Attribution Reporting API. Pick the scenario your debug pipeline is currently in; the page outputs a tailored before/after log diff and a checklist of what to change in code and dashboards before Chrome 130 reaches stable.

pick your current debug setup

before Chrome 130 (your current log row)

after Chrome 130 (browser-stripped)

migration checklist

what to tell your team

the code

// The browser will now omit source_debug_key and trigger_debug_key from
// the attribution_destination report when the corresponding party lacks
// 3p-cookie access. Don't rely on them being present.
if (report.source_debug_key && report.trigger_debug_key) {
  // safe path — both sides opted in
} else {
  // expected for most users post-Chrome-130: build dedup keys from
  // first-party identifiers + report timestamps instead.
}

see also