attribution-reporting-api
attribution-reporting-api copied to clipboard
WICG
Attribution Reporting API
The existing key id is actually longer than the limit and will fail. *** Preview | Diff
In https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md#limiting-the-number-of-unique-destinations-covered-by-pending-sources, we propose a limit on the number of sources that can be registered as "pending" at one time; > Strawman: 100 distinct destination sites per-{source site, reporting origin},...
Setting the Permission-Policy will require some sites to make an administrative change, with impact on either: * **If the default was off**: Small publishers and retailers that want attribution tracking...
https://wicg.github.io/attribution-reporting-api/#delivery-time Consider making some of the event-level report delivery time parameters vendor-specific in the spec, e.g. the early deadlines.
**Storage limits** The browser may apply storage limits in order to prevent excessive resource usage. Strawman: **_There should be a limit of 1024 pending aggregatable reports per destination site._** 1....
Currently, the event explainer only denotes that not_filters is supported in a JSON comment. It is not entirely clear how these filters are handled. It could be worth adding a...
This issue tracks the open question the aggregatable explainer: https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md#hide-the-true-number-of-attribution-reports To solve this, I believe we will need to have a mechanism that allows us to either randomize the true...
The TEE version of the [Aggregation Service for the Attribution Reporting API](https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATION_SERVICE_TEE.md) proposal states that: > Decryption and aggregation of raw aggregatable report data happens within a secure and isolated...
Since we only care about the response headers, and not the body. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/HEAD
