Hi everyone,
I'm seeing an issue where AdvertisingIdClient.getAdvertisingIdInfo(context).isLimitAdTrackingEnabled always returns false, even when Ad personalization is turned OFF at https://myadcenter.google.com/personalizationoff.
Test setup:
Devices: Pixel 9 (emulator, API 36) and a physical Android 11 phone
Same result on multiple Google accounts (not this one)
Play Services version: 25.40.31 (260800-816341114)
Library: com.google.android.gms:play-services-ads-identifier:18.2.0
Summary:
Using simple code:
Result on all tested devices:
adId=<redacted> limitTracking=false
Additional checks:
Reset Advertising ID → no change
Rebooted device → no change
Waited over 7 days since personalization OFF → no change
Single user, no managed/work profile
Verbose logs from AdIdService, AdvertisingIdClient, and AdIdRaw confirm the binder returns limitTracking=false consistently.
Context:
I already filed a bug report in the Android Issue Tracker, but Google closed it with status:
“Won’t Fix (Infeasible) – please contact Google Mobile Ads SDK forum.”
So, I’m checking here to see if anyone else has encountered the same issue.
Questions:
Should isLimitAdTrackingEnabled still reflect the user’s opt-out setting in My Ad Center?
If not, how are other developers handling the “opt-out of ad personalization” case in Android apps today?
It seems this flag might no longer be synchronized with the user’s Ad Center preferences or has changed behavior in recent Play Services versions.
Thanks in advance for any insights or confirmations!
Thank you for contacting the Mobile Ads SDK Support team.
The AdvertisingIdInfo value is tied to Device OS level and this value will not change whether personalization ads are turned ON or OFF in the Ad Center.
Additionally, please note that our support channel can only best assist you with regards to Google Mobile Ads SDK implementation and technical issues.
If you have any questions about usage of the Google Mobile Ads SDK, please feel free to reach out.![]() |
Mobile Ads SDK Team |
[2025-11-05 11:20:41Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01vSL0q:ref" (ADR-00338078)