← Back to release summary

Attribution Reporting Feature: Remove Aggregatable report limit when trigger context ID is non-null

Category
Miscellaneous
Type
New or changed feature
Status
Enabled by default (Chrome 134)
Intent stage
None

Summary

We are landing the following change to the Attribution Reporting API focused on: * Removing aggregatable report limit when trigger context ID is non-null

Motivation

This change is based on API caller feedback and the need for being able to measure a higher number of conversion events for certain user flows. Currently the API has a limit that allows up to 20 aggregatable reports to be generated per source registration which is restrictive for use cases where a user may have a longer user journey. This change removes the aggregatable report limit when a trigger context ID is provided as part of the registration. The removal of this limit is restricted to only when the trigger context ID is specified, because when it is specified the API applies a higher rate of null reports which helps to protect against cross-site information leaking through report counts. Additionally, aggregatable reports will still be bound by other limits that restrict the total amount of information that can be measured, such as the L1 contribution budget (65,536) per source and the attribution rate limit.

Standards & signals

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

View on chromestatus.com