attribution-reporting-api
attribution-reporting-api copied to clipboard
Allow attribution to be scoped smaller than destination site
Currently, when a trigger is registered the browser looks up all sources which are registered within the destination site to perform attribution.
Once the matching source is found, the filtering feature can be used to control whether or not that attribution should continue. This has a number of short comings.
For example let's consider an advertiser site which hosts multiple stores and the following events: shop1.example.com and shop2.example.com
Source 1 registered publisher.test -> shop1.example.com Source 2 registered publisher.test -> shop2.example.com
Trigger -> shop1.example.com
If we are using last touch attribution, source 2 will be matched to the trigger, even though source 1 should get attribution credit.