← Back to release summary

Attribution Reporting API Feature (Aggregatable Named Budgets)

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

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

Motivation

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.

Standards & signals

Explainers: https://github.com/WICG/attribution-reporting-api/pull/1422

View on chromestatus.com