Intent to Ship: Attribution Reporting Feature: Aggregatable Named Budgets

Currently the API has a concept of “L1 contribution budget.” This budget limits the total amount of information that can be attributed to any single ad impression (i.e. an ad click or view). The current L1 contribution budget is 65,536 and API callers can use this budget across various conversion events based on their own allocation choice.

This change makes it easier for API callers to pre-allocate how much of the L1 contribution budget they would like to allow for measuring different types of events. With this change API callers can specify the maximum amount of L1 contribution budget they would like to allow for any given type of conversion event, directly addressing API caller feedback.

Explainer/Spec changes

Explainer & Spec: https://github.com/WICG/attribution-reporting-api/pull/1422

Risks
Interoperability and Compatibility

This is a fully backwards compatible change and an optional feature that requires API callers to set new fields in order to use the feature. This feature does not break any pre-existing API or web functionality.

Gecko: No signal (Original request: https://github.com/mozilla/standards-positions/issues/791)

WebKit: No signal (Original request: https://github.com/WebKit/standards-positions/issues/180)

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

No

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

Is this feature fully tested by web-platform-tests?

No, currently the behavior around aggregatable named budgets is not covered in WPT due to difficulty of adding significant coverage for the feature because of API-mandated delays and noise. However, the feature is covered by comprehensive integration tests (commonly referred to as “interop tests”) that are also reusable by other implementations.

Estimated milestones

This feature is anticipated to ship as part of Chrome 132.

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5325966648541184

Links to previous Intent discussions

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

Intent to Ship: Attribution Reporting features M125

Intent to Ship: Attribution Reporting features M126

Intent to Ship: Attribution Reporting features M127

Intent to Ship: Attribution Reporting features M128 (1)

Intent to Ship: Attribution Reporting features M128 (2)

Intent to Ship: Attribution Reporting feature M130

Mike Taylor

unread,

Nov 6, 2024, 9:22:06 AMNov 6

to Akash Nadan, blink-dev

On 11/5/24 3:33 PM, 'Akash Nadan' via blink-dev wrote:

Contact emails
akash...@google.com, lin...@chromium.org, john...@chromium.org

Explainer
Attribution Reporting with event-level reports

Attribution Reporting API with Aggregatable Reports

Aggregation Service for the Attribution Reporting API

Specification
https://wicg.github.io/attribution-reporting-api/

Blink component
Internals > AttributionReporting

TAG review
Still under review under the original I2S for the Attribution Reporting API

TAG review status
Pending

This should be updated to "declined" (as well as the ar_debug intent), at least in prose (seems chromestatus doesn't support that particular resolution).

Summary
We are landing the following change to the Attribution Reporting API focused on:

Making it easier to predefine contribution budget allocation for aggregate reports

This change is based on API caller feedback and the need for more control over the contribution budget allocation.

Currently the API has a concept of “L1 contribution budget.” This budget limits the total amount of information that can be attributed to any single ad impression (i.e. an ad click or view). The current L1 contribution budget is 65,536 and API callers can use this budget across various conversion events based on their own allocation choice.

This change makes it easier for API callers to pre-allocate how much of the L1 contribution budget they would like to allow for measuring different types of events. With this change API callers can specify the maximum amount of L1 contribution budget they would like to allow for any given type of conversion event, directly addressing API caller feedback.

Explainer/Spec changes

Explainer & Spec: https://github.com/WICG/attribution-reporting-api/pull/1422

Reading diffs isn't a great experience for reviewing - could you please put together a minimal explainer or provide hyperlinks to the spec and explainer bits that have landed? That would be great for any future intents as well.

--
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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4a1a03ee-0a34-4131-8754-7694635cf5f4n%40chromium.org.

Akash Nadan

unread,

Nov 6, 2024, 2:12:27 PMNov 6

to blink-dev, Mike Taylor, blink-dev, Akash Nadan

Hi Mike,

Thanks for flagging. We will make sure the TAG review status is updated to "declined" going forward.

And regarding the Explainer and Spec links, we have landed the changes and I have linked to the exact Explainer section below (we will make sure to link the exact sections going forward as well):

Explainer: https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md#optional-named-budgets

Thanks,

Akash

Akash Nadan

unread,

Nov 7, 2024, 3:33:26 PMNov 7

to blink-dev, Akash Nadan, Mike Taylor, blink-dev

Hi All,

Slight update to one of the I2S questions:

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

This feature is expected to be supported in Android WebView in the future alongside Android platform support.

Thanks,

Akash

Chris Harrelson

unread,

Nov 13, 2024, 11:12:27 AMNov 13

to Akash Nadan, blink-dev, Mike Taylor

LGTM1

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/14964873-7865-42ef-b990-da4e633a4c4bn%40chromium.org.

Mike Taylor

unread,

Nov 13, 2024, 12:32:41 PMNov 13

to Chris Harrelson, Akash Nadan, blink-dev

LGTM2

TAMURA, Kent

unread,

Nov 19, 2024, 8:32:41 PMNov 19

to Akash Nadan, blink-dev, Chris Harrelson, Mike Taylor

LGTM3.

To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d66c8098-b706-4879-8555-ef731b490249%40chromium.org.