Attribution Reporting API
Qu'est-ce que 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.
● Exemples
- 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.
● Questions fréquentes
Qu'est-ce que 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. Cette notion relève de la catégorie Confidentialité et protection des données en cybersécurité.
Que signifie 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.
Comment fonctionne 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.
Comment se défendre contre Attribution Reporting API ?
Les défenses contre Attribution Reporting API combinent habituellement des contrôles techniques et des pratiques opérationnelles, comme détaillé dans la définition ci-dessus.
Quels sont les autres noms de Attribution Reporting API ?
Noms alternatifs courants : ARA, Attribution Reporting.
● Termes liés
- 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
Confidentialité différentielle
Cadre mathématique qui quantifie la perte de confidentialité lors de la publication de statistiques ou de l'entraînement de modèles, par ajout de bruit calibré bornant de manière prouvable la contribution de chaque individu.
- privacy№ 1263
Cookie tiers
Cookie déposé par un domaine différent de celui affiché dans la barre du navigateur, historiquement utilisé pour pister les utilisateurs entre sites.
- privacy№ 266
Pistage inter-sites
Pratique consistant à relier l'activité d'un même utilisateur sur plusieurs sites sans lien pour construire un profil comportemental durable.
- cloud-security№ 1300
Environnement d'Exécution de Confiance (TEE)
Contexte d'exécution sécurisé et isolé au sein du processeur où code et données sont protégés en confidentialité et en intégrité, même vis-à-vis de l'OS hôte et de l'hyperviseur.