[null,null,[],[[["The Attribution Reporting API on Android is expanding to support app-to-app, app-to-web, web-to-app, and web-to-web attribution, requiring updates for ad techs, apps, and web views."],["Apps now register web sources and triggers via new API calls, enabling cross-surface attribution but necessitating careful handling of redirects and adherence to allowlist requirements for WebView integration."],["Browsers integrate by sending request headers that signal API support and trigger source/trigger registration, while ad techs utilize specific headers for initiating secondary API calls from WebViews."],["Privacy and security are addressed through rate limits, allowlisting for web source registration, and app-level user controls for data deletion, but ongoing considerations include browser measurement integration and destination validation."],["Transitional debugging reports offer more detailed attribution insights when advertising ID is available, with varying availability based on context and specific enabling conditions."]]],["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"]]