← Back to release summary

Attribution Reporting API Feature (Changes to source-destination-limit logic)

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: * Improving transmission loss through changes to the source destination limit logic

Motivation

This change is based on ad-tech feedback that we have heard regarding a current rate limit for the Attribution Reporting API. Currently the API has a limit called the source-destination-limit which allows API callers to register up to 100 distinct destinations per {source site, reporting site} applied to all unexpired sources per browser. This rate limit also uses a LIFO model (last-in-first-out) in the sense that once the limit is reached, any new source registrations will be rejected. We have heard feedback from multiple ad-techs that they are running into this limit which then causes some amount of loss in terms of not being able to register new sources.

Standards & signals

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

View on chromestatus.com