attribution-reporting-api issues

Additional Debugging Asks For Attribution Reporting Api

3

The attribution reporting API has a set of mechanical and privacy-oriented restrictions, which introduces discrepancies between existing third-party cookie based conversion measurement and api-based conversion measurement. Some restrictions such as...

chandan-giri

Consider applying filtering before prioritization during attribution step

3

Related to https://github.com/WICG/attribution-reporting-api/issues/491 The browser first finds the highest priority impression, then checks if it matches filters before attributing it. This means, if there are two impression with the same...

johnivdel

possible-future-enhancement

Decouple Impression Expiry and Reporting window for Event level Attribution API

**Problem** Today we have the last reporting window for event-level reports coupled with the impression expiry. The max expiry that Chrome supports is 30 days. However, many consumers of the...

chandan-giri

Specify shared info and aggregation service payloads for aggregatable report

*** Preview | Diff

linnan-github

Specify aggregatable report delivery

*** Preview | Diff

linnan-github

Specify aggregatable source and trigger parsing

*** Preview | Diff

linnan-github

Specify aggregatable report triggering algorithm

2

Introduce aggregatable attribution report struct and spec the algorithm to trigger aggregatable attribution. *** Preview | Diff

linnan-github

Permissions-Policy limitations

While the permissions policy comes with important security/anti-fraud benefits (prevent arbitrary third-parties from registering sources without the publisher’s knowledge), it comes with the following limitations for API users: ### Limitations...

maudnals