[null,null,[],[[["The Attribution Reporting API enables privacy-preserving measurement of ad effectiveness (clicks/views leading to conversions) without relying on third-party cookies."],["It offers two report types: Event-level reports for basic conversion data and Summary reports for aggregated, detailed insights."],["The API prioritizes user privacy by incorporating noise, delays, and aggregation to minimize cross-site user tracking."],["It's supported in Chrome and Android, with varying levels of support or alternative proposals from other browsers."],["The API is under development and subject to change, potentially impacting its suitability for certain billing models."]]],["The Attribution Reporting API extends to support app-to-app, app-to-web, web-to-app, and web-to-web attribution. Ad techs must enroll and update API calls, while apps/browsers must pass web source/trigger registrations to Android. Key actions include registering web sources/triggers via new API calls (`registerWebSource()` and `registerWebTrigger()`), with validation against app-specified destinations. Apps can configure WebView behavior for source/trigger handling. Transitional debugging reports are available with AdID availability. Apps can leverage an allowlist and web context API to accurately handle web attribution. The API also applies privacy-preserving rate limits.\n"]]
