attribution-reporting-api icon indicating copy to clipboard operation
attribution-reporting-api copied to clipboard

Attribution Reporting API

Results 221 attribution-reporting-api issues
Sort by recently updated
recently updated
newest added

To match the spec. Fixes #1321.

headers-validator

I'm trying to follow along with the documentation both here and in Android docs and I'm not quite sure how or if the following works, or if it does, how...

app-to-web
developer-input

1. Can we configure the aggregation service instances for organization-wide security screening and log collections, such as Splunk and Hubble? 2. Can we configure the setup for the monitoring, metric...

aggregate
developer-input

Per https://wicg.github.io/attribution-reporting-api/#parse-attribution-destinations, the size of the `destination` field is supposed to be checked after URL-to-site transformation and deduplication, but the validator checks the size of the JSON list itself, causing...

bug
headers-validator

how to maintain versioning of aggregatable reports , if any keyset changes or some become obsolete , we will need versioning to filter or choose right domain files otherwise extra...

aggregate
developer-input

In [step 2 of "trigger event-level attribution"](https://wicg.github.io/attribution-reporting-api/#ref-for-attribution-source-randomized-response%E2%91%A6) we return early with a `trigger-event-noise` verbose debug report when the attributed source has a non-zero-report randomized response, but we do **not** return...

bug
debugging-monitoring
documentation

Currently the attributed reporting origin limit (https://wicg.github.io/attribution-reporting-api/#should-block-processing-for-reporting-origin-limit) may be called twice, once for event-level triggering and once for aggregatable triggering. We should consider whether there's any privacy concern if this...

Per https://wicg.github.io/attribution-reporting-api/#clear-site-data-integration, the effective owner of a source or a report (event-level or aggregatable) is the *reporting origin* that registered it, as only the reporting origin can clear it. But...

documentation
Looking for feedback

We are seeking feedback on consolidating coordinator services for attribution reporting and other workloads. Please review and comment on the main issue posted on the https://github.com/WICG/protected-auction-services-discussion/issues/69 repository.

Looking for feedback