akash...@google.com, lin...@chromium.org, john...@chromium.org
Attribution Reporting with event-level reports
Attribution Reporting API with Aggregatable Reports
Aggregation Service for the Attribution Reporting API
https://wicg.github.io/attribution-reporting-api/
Internals > AttributionReporting
We are landing the following change to the Attribution Reporting API focused on:
applying element-level referrer policy for specific html elements
This change is based on ad-tech feedback and so that attributionsrc requests are treated like other subresources on the page.
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.
This feature is not a strictly backwards compatible change because before the change the resource-level policy was ignored, but now it is not ignored. Given this change, the value of the request's referrer header may be different than before. This breakage is unlikely, because it would require an API caller to have a different referrer policy on the document and on the resource, which is unlikely for the Attribution Reporting API.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
The attribution reporting feature will be supported on all platforms with the exception of Android WebView
Yes
This feature is anticipated to ship as part of Chrome 126.
https://chromestatus.com/feature/5191009960198144
Previous I2S:
Intent to Ship: Attribution Reporting API
Intent to Ship: Attribution Reporting features M117
Intent to Ship: Attribution Reporting features M118
Intent to Ship: Attribution Reporting features M119
Intent to Ship: Attribution Reporting features M120
Intent to Ship: Attribution Reporting features M121
Intent to Ship: Attribution Reporting features M123
Intent to Ship: Attribution Reporting features M124
Intern to Ship: Attribution Reporting features M125
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8c39d27a-ae43-40ce-bd32-4656b82fe867n%40chromium.org.
LGTM2 (and yes, please don't emit other info in future intents -
it really helps with reviews!)
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_ZDxT1FVpnCvKnTXw4CE_EiDXjUhqmOHXbfwZ02QxaCg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a90eb068-6048-4711-a1fb-531188e6663e%40chromium.org.