← Back to release summary

Attribution Reporting API Feature (Referrer Policy for Attributionsrc Requests)

Category
Miscellaneous
Type
New or changed feature
Status
Proposed (Chrome Proposed)
Intent stage
None

Summary

We are landing the following changes to the Attribution Reporting API focused on: * applying element-level referrer policy for specific html elements

Motivation

This change is based on ad-tech feedback and so that attributionsrc requests are treated like other subresources on the page (Github issue linked below). Currently when the API is called through the use of the attributionsrc attribution as part of various html elements (i.e. <img>, <script>, <a>, or window.open), it ignores the resource-level referrer policy attribute set on the html element. With this change the attributionsrc request will now apply the same resource-level referrer policy set in the <img>, <script>, <a>, or window.open. This will allow ad-techs more control over whether or not they want to be more or less restrictive regarding the referrer information on their attributionsrc requests.

Standards & signals

Explainers: https://github.com/WICG/attribution-reporting-api/issues/382 https://github.com/WICG/attribution-reporting-api/pull/1254

View on chromestatus.com