Attribution Reporting API
Was ist Attribution Reporting API?
Attribution Reporting APIA Privacy Sandbox API in Chrome and Android that lets advertisers measure ad conversions across sites without cross-site identifiers, using browser-mediated, noise-injected event-level or aggregated reports.
The Attribution Reporting API (ARA) is the Privacy Sandbox mechanism for measuring ad-driven conversions without exposing cross-site identifiers. Sources (ad clicks or views) are registered on the publisher side; triggers (conversions) are registered on the advertiser side. The browser maintains the join between them locally and, at delayed and randomized intervals, sends one of two kinds of report. Event-level reports return a noisy, low-resolution mapping from a source event to a conversion event, suitable for click attribution. Aggregatable reports go through a separate Aggregation Service running in a trusted execution environment, which adds calibrated noise (differential privacy) before returning aggregate dashboards across many users. Both report types are designed to bound the cross-site information any caller can learn. ARA is one of the central pieces of the post-third-party-cookie measurement story and a focus of regulator attention (CMA, French CNIL, German DPAs). For ad-tech and measurement vendors, integrating ARA requires substantial backend changes for noise budgets, report aggregation, and trust-establishment with the Aggregation Service.
● Beispiele
- 01
An advertiser registers click-trigger and conversion-trigger callbacks; Chrome delivers event-level reports days later, with noise to limit user-level inference.
- 02
A measurement vendor stands up an Aggregation Service in a TEE so that ARA aggregatable reports can be processed into campaign-level dashboards.
● Häufige Fragen
Was ist Attribution Reporting API?
A Privacy Sandbox API in Chrome and Android that lets advertisers measure ad conversions across sites without cross-site identifiers, using browser-mediated, noise-injected event-level or aggregated reports. Es gehört zur Kategorie Datenschutz der Cybersicherheit.
Was bedeutet Attribution Reporting API?
A Privacy Sandbox API in Chrome and Android that lets advertisers measure ad conversions across sites without cross-site identifiers, using browser-mediated, noise-injected event-level or aggregated reports.
Wie funktioniert Attribution Reporting API?
The Attribution Reporting API (ARA) is the Privacy Sandbox mechanism for measuring ad-driven conversions without exposing cross-site identifiers. Sources (ad clicks or views) are registered on the publisher side; triggers (conversions) are registered on the advertiser side. The browser maintains the join between them locally and, at delayed and randomized intervals, sends one of two kinds of report. Event-level reports return a noisy, low-resolution mapping from a source event to a conversion event, suitable for click attribution. Aggregatable reports go through a separate Aggregation Service running in a trusted execution environment, which adds calibrated noise (differential privacy) before returning aggregate dashboards across many users. Both report types are designed to bound the cross-site information any caller can learn. ARA is one of the central pieces of the post-third-party-cookie measurement story and a focus of regulator attention (CMA, French CNIL, German DPAs). For ad-tech and measurement vendors, integrating ARA requires substantial backend changes for noise budgets, report aggregation, and trust-establishment with the Aggregation Service.
Wie schützt man sich gegen Attribution Reporting API?
Schutzmaßnahmen gegen Attribution Reporting API kombinieren typischerweise technische Kontrollen und operative Praktiken, wie in der Definition oben beschrieben.
Welche anderen Bezeichnungen gibt es für Attribution Reporting API?
Übliche alternative Bezeichnungen: ARA, Attribution Reporting.
● Verwandte Begriffe
- privacy№ 960
Privacy Sandbox
Google's umbrella initiative for replacing third-party cookies and cross-site identifiers with privacy-preserving alternatives — Topics, Protected Audience (FLEDGE), Attribution Reporting, and on-device APIs — under heavy regulatory and competitor scrutiny.
- privacy№ 1286
Topics API
A Privacy Sandbox API in Chrome and Android that derives a small set of high-level interest topics from the user's recent browsing locally on the device, exposing them to participating sites instead of cross-site tracking identifiers.
- privacy№ 351
Differenzielle Privatsphäre
Mathematisches Rahmenwerk, das den Privacy-Verlust bei Statistik-Veröffentlichungen oder Modelltraining quantifiziert und durch kalibriertes Rauschen den Beitrag jeder einzelnen Person beweisbar begrenzt.
- privacy№ 1263
Drittanbieter-Cookie
Cookie, das von einer anderen Domain als der in der Adresszeile gesetzt wird und historisch zur seitenübergreifenden Verfolgung von Nutzern dient.
- privacy№ 266
Seitenübergreifendes Tracking
Die Praxis, die Aktivität eines Nutzers über mehrere voneinander unabhängige Websites hinweg zu verknüpfen, um ein langlebiges Verhaltensprofil aufzubauen.
- cloud-security№ 1300
Trusted Execution Environment (TEE)
Sicherer, isolierter Ausführungskontext im Prozessor, in dem Code und Daten in Vertraulichkeit und Integrität geschützt sind — auch vor Host-OS und Hypervisor.