Permissions-Policy: attribution-reporting directive
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 the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
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 Permissions-Policy header attribution-reporting directive controls whether the current document is allowed to use the Attribution Reporting API.
Specifically, where a defined policy blocks the use of this feature:
- Background
attributionsrcrequests won't be made. - The
XMLHttpRequest.setAttributionReporting()method will throw an exception when called. - The
attributionReportingoption, when included on afetch()call, will cause it to throw an exception. - Registration headers (
Attribution-Reporting-Register-SourceandAttribution-Reporting-Register-Trigger) in HTTP responses on associated documents will be ignored.
Syntax
Permissions-Policy: attribution-reporting=<allowlist>;
<allowlist>-
A list of origins for which permission is granted to use the feature. See
Permissions-Policy> Syntax for more details.
Default policy
The default allowlist for attribution-reporting is *.