attribution-reporting-api
attribution-reporting-api copied to clipboard
Attribution Reporting API
For example, multiple-pass querying, different privacy accounting schemes, different batching schemes.
Publishers will need to check pages for level of user risk before activating. Set the permission policy to default off, so that high risk tracking is less likely to happen...
What other models, such as outputting buckets and values if the value exceeds a noisy threshold, may be considered in future iterations?
Hi, I am looking for solutions to support multiple attribution sources at the event level. For example, we have a.com and b.com both can support the measurement for click/impression/conversions. When...
For awareness campaigns that won't expect an immediate click, the proposed 30 day maximum window is too short - especially for industries that have longer sales cycles. Can the attribution...
Source types can be one of `event` and `navigation`; this may be confusing, as all sources generically as _event_ sources. Proposal: `event` -> `view` `navigation` -> `click` ?
Currently, the Attribution-Reporting-Filters header allows a reporting origin to prevent the browser from generating reports based on trigger time signals and trigger time signals. This is not sufficient in cases...
The aggregate API explainer [says](https://github.com/WICG/conversion-measurement-api/blob/main/AGGREGATE.md#aggregatable-reports) that source_registration_time will be rounded to the nearest day boundary. The explainer does not explicitly specify a time zone, but the assumption is we'll round...
Hello! Regarding the [app-to-web proposal ](https://github.com/WICG/conversion-measurement-api/blob/main/app_to_web.md), I have a few questions on what type of scenarios are planned (or feasible) to be supported. (Keep in mind I'm not an Android...
How should we choose appropriate parties to act as coordinators and how can we ensure that the coordinator(s) can be trusted?