attribution-reporting-api
attribution-reporting-api copied to clipboard
WICG
Attribution Reporting API
Currently, we have a single rate-limit which counts the overall attribution (either event or aggregate or both) of the trigger. This change separates the attribution counts for event & aggregate...
The "Max source reporting origins per source reporting site" limit is per reporting site, therefore it's less concerned from security perspective. We already report other rate-limits scoped by reporting site...
Move computation of channel capacity out of parsing algorithm for explicit verbose debug reporting. *** Preview | Diff
To better mitigate security concerns with security concerning checks, e.g. max source reporting origins per rate-limit window and max destinations per reporting window, the debug data sent in the report...
Hello privacy sandbox team, we are currently exploring the Attribution Reporting API with [debugging reports](https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#optional-transitional-debugging-reports). Despite confirming the cookie's presence in the response header, we observed that the debugging keys...
To preserve the protection of user’s browser history, and also to mitigate utility concern with dropping new sources, we propose to apply FIFO rule to this limit instead of the...
The current attribution logic in the Attribution Reporting API may not be ideal for use-cases where an ad-tech needs more fine grain control over the attribution granularity (i.e. campaign, product,...
https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#attribution-success-debugging-reports
Today, if a debug key is present on a trigger and is otherwise valid, it is present on the corresponding event-level report. However, with the [Flexible event-level configurations proposal](https://github.com/WICG/attribution-reporting-api/blob/main/flexible_event_config.md), a...
For precision when the number of states exceeds the maximum integer representable by number.