Google Play Android Advertising ID policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps and SDKs using the Android advertising identifier for ads or analytics.
The advertising ID is resettable for a reason. Google restricts how it can be used, linked to other identifiers, and handled after users opt out, reset it, or delete it.
What to check
Audit SDK identity graphs and server-side joins. For advertising, don’t connect AAID to persistent device identifiers; linking it to personally identifiable information requires explicit consent. For analytics, the policy prohibits linking AAID to either personally identifiable information or persistent device identifiers.
Check personalization settings whenever accessing the ID. Test reset and deletion, including the all-zero identifier returned after deletion on supported devices.
How to address the rejection
Remove prohibited joins and stop reconstructing an identity after deletion. Don’t connect a reset ID to its previous ID or derived data without the required explicit consent. Respect opt-outs from personalized advertising while limiting remaining uses to those the policy allows.
Update privacy disclosures and verify downstream partners follow the same rules. Test both client events and backend associations; changing the mobile SDK alone may leave an impermissible server-side link in place.
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Android Advertising ID Checked 22 September 2026