Hi,
Thank you for contacting the Mobile Ads SDK Support team.
Please find the responses to your queries below:
1) If I set .setTagForUnderAgeOfConsent(true) to true then UMP SDK will not ask for consent of the user under 18 years old and will not collect his data and show him ads?
Ans: As per this Tag for under age of consent, set setTagForUnderAgeOfConsent (TFUA). When you set TFUA to true, the UMP SDK doesn't request consent from the user. If your app has a mixed audience, set this parameter for child users to ensure consent is not requested.
You can still get ads once setting setTagForUnderAgeOfConsent(true). See more details in https://support.google.com/admob/answer/6223431?hl=en .
2) Or do I need to set .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) and then UMP SDK will not ask for consent from a user under 18 years of age and will not collect his data and show him ads?
Ans: In your ad request configuration for MobileAds.getRequestConfiguration().toBuilder():
TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE: Means the ad request should receive treatment for EEA users under the age of consent, this disables personalized ads and AAID transmission.
3) Or do I need to set .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_FALSE ) and then UMP SDK will not ask for consent from a user under 18 years of age and will not collect his data and show him ads?
Ans: TAG_FOR_UNDER_AGE_OF_CONSENT_FALSE: Means the ad request is not flagged as for under-age-of-consent users. Personalized ads and AAID may be used unless otherwise restricted by other flags.
4) What is the difference between .setTagForUnderAgeOfConsent(true) and .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_FALSE ) ? And what do I need to set in order not to collect data from a user under 18 years of age and not show him ads?
Ans: Referring to our Targeting documentation [Android | iOS], setting `tagForChildDirectedTreatment` to `true` prevents the transmission of AAID or IDFA and prevents showing consent dialog for under-age users. Enables limited ads flow.
As per this documentation, Call setTagForUnderAgeOfConsent() with TAG_FOR_UNDER_AGE_OF_CONSENT_FALSE to indicate that you want the ad request to not receive treatment for users in the European Economic Area (EEA) under the age of consent.
I hope this helps, if you have any concerns, please reach out to us.
![]() |
Mobile Ads SDK Team |
[2025-08-12 04:06:03Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sye5l:ref" (ADR-00329339)
Hi,
Thank you for getting back to us.
1) What do I need to install so that Admob does not collect user data from Europe under 18 years old and does not show the consent window, .setTagForUnderAgeOfConsent(true) or .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE?
Ans: To ensure AdMob does not collect user data from users under the age of consent (typically 18 in Europe) and to prevent the consent message from showing, you need to use the setTagForUnderAgeOfConsent() method with TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE. This also prevents the transmission of the Android advertising identifier (AAID).
2) What is the difference between .setTagForUnderAgeOfConsent(true) and .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE?
Ans: setTagForUnderAgeOfConsent(true) is for the UMP SDK. When you set TFUA to true, the UMP SDK doesn't request consent from the user. If your app has a mixed audience, set this parameter for child users to ensure consent is not requested.
setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) indicate that you want the ad request to receive treatment for users in the European Economic Area (EEA) under the age of consent. This also prevents the transmission of the Android advertising identifier (AAID). You use this to tell AdMob and its ad partners to treat the user as a minor and serve restricted, non-personalized ads.
3) If my application is installed from the age of 18 and I install setTagForUnderAgeOfConsent(true) or .setTagForUnderAgeOfConsent(RequestConfiguration.TAG_FOR_UNDER_AGE_OF_CONSENT_TRUE) for safety, then this will not violate the rules of Google Play and my account or application will not be deleted?
Ans: No, this will not violate Google Play or AdMob policies. As your app is rated 18+ on Google Play, the expectation is that your audience is adults. However, because a user can technically download and use an 18+ app even if they are younger, your extra safety measure is a responsible way to handle potential edge cases.
I hope this helps! Let me know if you have any other questions.
![]() |
Mobile Ads SDK Team |
[2025-08-14 18:36:53Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01sye5l:ref" (ADR-00329339)