demo · v130

Debug Key Privacy simulator

In v130, Attribution Reporting only includes source_debug_key / trigger_debug_key in reports when ad-tech debug cookies are set on both source and trigger sites. Toggle the cookie state below and see what the browser would emit.

requires the Attribution Reporting API Live reports require the Privacy Sandbox APIs enabled. This simulator implements the spec rules client-side so you can explore the debug-key inclusion logic.

resulting attribution report


  


  

    
the rule


// Both source and trigger must opt in via the ar_debug cookie
// and both source_debug_key + trigger_debug_key must be non-null.
// Cross-app/web reports lose them because the cookie boundary can't
// be crossed.

if (
  sourceCookie &&
  triggerCookie &&
  sourceDebugKey !== null &&
  triggerDebugKey !== null &&
  !crossAppWeb
) {
  report.source_debug_key  = registeredSourceDebugKey;
  report.trigger_debug_key = registeredTriggerDebugKey;
} else {
  // both stripped
}

  


  

    
see also