Attribution-Reporting-Eligible header
Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see thecompatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
The HTTPAttribution-Reporting-Eligiblerequest 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 theAttribution-Reporting-Eligible value, the server is expected to respond with either anAttribution-Reporting-Register-Source orAttribution-Reporting-Register-Trigger header to complete the registration of an attribution source or trigger, respectively.
See theAttribution 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-sourceAnevent-based attribution source can be registered.
navigation-sourceAnavigation-based attribution source can be registered.
triggerAnattribution trigger can be registered.
Every response in a redirect chain can register at most one source or one trigger.
Examples
Attribution-Reporting-Eligible: triggerSpecifications
| Specification |
|---|
| Attribution Reporting # attribution-reporting-eligible |