Attribution Reporting API
¿Qué es 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.
● Ejemplos
- 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.
● Preguntas frecuentes
¿Qué es 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. Pertenece a la categoría de Privacidad y protección de datos en ciberseguridad.
¿Qué significa 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.
¿Cómo funciona 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.
¿Cómo defenderse de Attribution Reporting API?
Las defensas contra Attribution Reporting API combinan habitualmente controles técnicos y prácticas operativas, como se detalla en la definición.
¿Cuáles son otros nombres para Attribution Reporting API?
Nombres alternativos comunes: ARA, Attribution Reporting.
● Términos relacionados
- 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
Privacidad diferencial
Marco matemático que cuantifica la pérdida de privacidad al publicar estadísticas o entrenar modelos, añadiendo ruido calibrado para acotar de forma demostrable la influencia de cualquier individuo.
- privacy№ 1263
Cookie de terceros
Cookie creada por un dominio distinto al que aparece en la barra del navegador, usada históricamente para rastrear a los usuarios entre sitios.
- privacy№ 266
Rastreo entre sitios
Práctica de vincular la actividad de un usuario en varios sitios no relacionados para construir un perfil de comportamiento duradero.
- cloud-security№ 1300
Entorno de Ejecución Confiable (TEE)
Contexto de ejecución seguro y aislado dentro del procesador donde el código y los datos están protegidos en confidencialidad e integridad, incluso frente al SO y al hipervisor.