[null,null,[],[[["The Attribution Reporting API does not send reports immediately after a conversion; instead, the browser schedules them with a delay."],["Aggregatable reports are sent with a random delay of up to 10 minutes or shortly after the browser restarts."],["Event-level reports for view-through conversions are sent about one hour after the view event is no longer eligible for attribution."],["Click-through conversion reports are sent at least two days after the conversion, with specific windows at 2, 7, or 30 days post-click depending on when the conversion occurs."],["Report delivery is contingent upon the browser being online and running, with retry attempts after failures, but eventual deletion if not successful."]]],["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"]]
