We are landing the following changes to the Attribution Reporting API focused on: * providing more control over the attribution filtering
This change is based on ad-tech feedback and the need for more fine grained filtering controls before the attribution process takes place. Currently the API performs filtering after a source is chosen based on matching <reporting origin, destination site> fields. This results in API callers either not receiving attributions reports or incorrect attribution in scenarios where there are multiple different advertisers/campaigns that all convert on the same destination site (i.e. eTLD+1). This change allows API callers to now specify a field called "attribution scopes" which will be used for filtering before starting the regular attribution flow. This allows API callers more fine grained control over the attribution granularity and the ability to receive proper attributions reports in the scenario described above (i.e. where there are multiple different advertisers/campaigns that all convert on the same destination site). This change directly addresses API caller feedback and allows them to have more control over their attribution filtering.
Explainers: https://github.com/WICG/attribution-reporting-api/pull/1282 https://github.com/WICG/attribution-reporting-api/pull/1215