Attribution-Reporting-Eligible header
Deprecated
To be removed
This feature is pending removal from browsers. Using it now may lead to broken functionality in future updates. Following the announcement that Chrome will maintain its current approach to third-party cookies, Chrome decided to withdraw certain Privacy Sandbox features including the attribution reporting API.
Non-standard: This feature is not standardized. We do not recommend using non-standard features in production, as they have limited browser support, and may change or be removed. However, they can be a suitable alternative in specific cases where no standard option exists.
The HTTP Attribution-Reporting-Eligible request header indicates that the corresponding response is eligible to register an attribution source or trigger.
This header is never set manually and is instead sent by the browser in response to various HTML element or JavaScript request settings. Depending on the allowed registrations specified in the Attribution-Reporting-Eligible value, the server is expected to respond with either an Attribution-Reporting-Register-Source or Attribution-Reporting-Register-Trigger header to complete the registration of an attribution source or trigger, respectively.
See the Attribution Reporting API for more details.
| Header type | Request header |
|---|---|
| Forbidden request header | No |
Syntax
Attribution-Reporting-Eligible: <allowed-registrations>
Directives
<allowed-registrations>-
A structured-header dictionary representing the registrations allowed in the corresponding response. Possible keys are:
event-source-
An event-based attribution source can be registered.
-
A navigation-based attribution source can be registered.
trigger-
An attribution trigger can be registered.
Every response in a redirect chain can register at most one source or one trigger.
Examples
Attribution-Reporting-Eligible: trigger