demo · v150

Header Probe

Probes the network-level entry points for the Attribution Reporting API — the attributionsrc attribute and the Attribution-Reporting-Eligible request header. In v150+ these are being wound down: the JavaScript surface may still parse, but registrations are no longer accepted.

Each probe attempts to opt the document into the API at a different network entry point and reports what came back.

Click "Run probes" to begin.
// JS surface — still parses, but registrations are ignored in v150
fetch('/path', { attributionReporting: { eventSourceEligible: true } });

// HTML surface — attribute is recognised but inert
<a href="/click" attributionsrc>Ad</a>

// Network surface — header still legal, no callback fires
Attribution-Reporting-Eligible: event-source, trigger

what to migrate to

The Privacy Sandbox roll-back means there is no in-browser replacement. The realistic alternatives are server-side conversion APIs (Conversions API, server-side GTM), hashed-email identity solutions, and contextual targeting. The Attribution Reporting JS, HTML, and header surfaces will remain feature-detectable for several releases before full removal.

see also

implementation reference

Need the exact API surface, compatibility boundaries, errors, lifecycle, and source links? Read the matching gendn reference ↗