RE: [google-admob-ads-sdk] handling ump gdpr consent choices

[Mobile Ads SDK Forum Advisor]

Hi ,

Thank you for contacting the Mobile Ads SDK Support team.

Question 1: After the GDPR consent form is shown, can I initialize the AdMob SDK regardless of the user's consent choices?

Answer: Yes , As per the Get Started, Consent must be handled before SDK initialization, otherwise preloaded ads may not respect user preferences or regulatory requirements.You can check the Google sample application for a reference implementation.

Question 2: Once the SDK is initialized, do I need to manually evaluate individual consent flags (purpose 1, 2, 3, etc.) to determine which ad type to request, or can the developer simply call standard ad loading/showing methods and let AdMob automatically serve the appropriate ad type (personalized, non-personalized, limited, or no ad) based on the stored consent choices?

Answer: Once GDPR consent has been collected, the consent choices are stored locally on the device. You don't need to evaluate the individual consent flags (like TCF purposes 1, 2, 3, etc.). The UMP SDK automatically determines the appropriate ad type to serve based on the stored preferences. The Google Mobile Ads SDK retrieves the user's stored consent choices from local storage (the TCF string).

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-08-11 18:23:52Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01syfjl:ref" (ADR-00329501)