Skip to Content
Platform.Ontology

Attribution Reporting API on Android

A built-in way for ad tech to count conversions with noise and limits, without ad IDs.

Used to track youAds and install trackingAndroid Privacy SandboxAndroid and iPhoneWhile you use itIn the background

In one line

Can't count on this Android ad counting tool, since Google announced it is retiring it

A built-in way for ad tech to count conversions with noise and limits, without ad IDs.

Event-level and summary reports with caps and delays; Google announced in Oct 2025 it would retire it while standards work continues at W3C.

What it can and can't do

What the user does: Nothing. It was a background feature, and Google announced its retirement on 17 Oct 2025

It can

  • Have counted ad results with noise and limits, without ad IDs (Android 13 and later)
  • Have sent event level and summary reports
  • Keep working until Google sets a removal date

It cannot

  • Run on iPhone; it is not an Apple feature
  • Count on it long term, since most of Privacy Sandbox is being retired
  • Show a removal date; none was named

How it differs between platforms: Android only. iPhone never had it.

On Android and iPhone

AndroidiPhone
StatusRemovedNot supported
First versionAndroid 13 (API 33)Not available
Permission or entitlementandroid.permission.ACCESS_ADSERVICES_ATTRIBUTIONNot listed
Protection levelnormalnone
How access is grantednot-exposednot-exposed
What the user seesNot listedNot listed
How long it lastsNot listedNot listed
How to take it backNot listedNot listed
Store policyPrivacy Sandbox status page lists as scheduled for phaseout (page updated Aug 2026)None listed
APIMeasurementManager.registerSource/registerTriggerNot listed
NotesGoogle announced on 17 Oct 2025 it is retiring this along with most Privacy Sandbox APIs. No Android removal date was stated in the announcement.Not an Apple feature.

Data you get

What comes back: Not available going forward
Shape: none
How often: n/a

No individual data fields. The signal is the access itself.

Technical limits

  • Retired: do not build new features on this
  • Ad ID stays the main cross-app identifier

The story

What it is

Google's built in way to count ad conversions with noise, instead of using an ad ID.

For you

You would not see it. It would have let advertisers learn that an ad led to a sale, with random noise and no ID.

For makers

It offered event level and summary reports with caps and delays. Google announced the retirement in October 2025 while the same ideas continue as a web standard.

Where you see it

TypeExampleApps
adsAn ad network measures how many installs a video ad produced without the advertising ID.Google Ads
gamesA game maker checks whether a banner drove paying players, with noisy counts.None named
shoppingA retailer gets a daily report of purchases per ad, and cannot see who bought.None named
analyticsA measurement firm tests summary reports against the old ID based totals.None named
securityCaps on data bits make it harder to track one person across apps.None named
developerA developer joins a beta to test the API and later must plan for its retirement.None named

Risks

  • Retired, so less reliable
  • Noise hides small campaigns

Android and iPhone in short

  • Android: Announced in October 2025 to be retired, and mostly not widely used.
  • iPhone: iOS uses SKAdNetwork and AdAttributionKit for the same job.

What the platform says

Good uses and abuse

Legitimate uses

  • Was meant as an ID-free ad system

Known abuse

  • Low adoption

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility1 of 5How useful it is to honest apps
Friction1 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

History

  • 2022-02, Android Android 13 (API 33): Measurement API in preview
  • 2025-10, Android Android 16: Retirement announced; interoperable standard continues at W3C PATWG

Same idea on the web

Sources

How well checked: Checked against real behavior.

On this page