AdMob consent: set up GDPR and US state messages with the UMP SDK
Why AdMob needs consent, how to create GDPR and US state messages in Privacy & messaging, the UMP SDK flow for Android and iOS, and how to test it.

If your app shows AdMob ads to people in the EEA, the UK or Switzerland, you need to ask for their consent, using a Google-certified consent management platform (CMP). The easiest one is Google's own: create a message in AdMob's Privacy & messaging tab and show it with the User Messaging Platform (UMP) SDK. Without it, you can only serve limited ads to those users.
It doesn't matter where you live. A developer in India with users in Germany is in scope, because the rule follows the user's location. This guide covers why consent is needed, how to create the GDPR and US states messages, the SDK calls on Android and iOS, how to test, and what happens if you skip it. It reflects Google's documentation as of November 2026, and it isn't legal advice.
Why AdMob needs consent
Two sets of rules are involved.
- Google's EU user consent policy. It covers users in the European Economic Area, the UK and Switzerland. Publishers must disclose and get consent for cookies or other local storage where the law requires it, and for using personal data for ad personalization (policy).
- Google-certified CMP. To serve personalized ads in those regions you must use a certified CMP that integrates with the IAB's Transparency and Consent Framework. That has applied to the EEA and UK since January 16, 2024 and to Switzerland since July 31, 2024 (Google's requirement). Google's UMP SDK is one of the certified options, and you can use any other CMP from Google's certified list instead.
- US state privacy laws. For users in applicable states, AdMob offers a message that lets them opt out of ad personalization. The US states help page lists 24 states as of November 2026.
When the requirements aren't met, Google says you will not be eligible to serve personalized ads. Google's developer docs put it more bluntly for traffic in the EEA and UK: only limited ads can serve. Limited ads don't use cookies, user identifiers or local storage on the device, so they may earn less. Google doesn't publish by how much.
The Privacy & messaging tab
In AdMob, open Privacy & messaging in the sidebar. Google's overview describes it as the tool for creating the messages that collect consent or opt-outs under rules like GDPR and US state laws. There are three message types (Google's list):
| Message | Who sees it |
|---|---|
| European regulations | App users in the EEA, UK and Switzerland. Gathers consent. |
| US state regulations | App users in applicable US states, to opt in or out of ad personalization. |
| IDFA explainer | iOS users, shown just before Apple's tracking alert. |
Messages show at two moments: at app start (when you call requestConsentInfoUpdate) and at the privacy options entry point, a button or menu item in your own app that reopens the form. You have to build that entry point yourself.
Create a GDPR (European regulations) message
- Open Privacy & messaging, choose European regulations, then Create message.
- Select the apps, then the default and additional languages.
- Set targeting: the EEA, UK and Switzerland only, or everywhere.
- Name the message (only you see the name) and add your privacy policy URL, which is required.
- Publish, or save a draft.
Google's steps expect the UMP SDK to be in your app first.
Create a US states message
- On the US state regulations card, click Create (or Manage, then Create message).
- Select your apps and a default language: English, Spanish or Spanish (Latin America).
- Under Targeting, turn on all supported states, or pick states one by one.
- Name it, then Publish.
These are the US states message steps. The developer guide says UMP SDK 2.1.0 or higher is recommended for it, and that you must implement the privacy options entry point (US states guide).
The UMP SDK flow
The flow is the same on both platforms, and Google says to run it at every app launch:
requestConsentInfoUpdate: asks Google whether this user needs a form.loadAndShowConsentFormIfRequired(Android) orConsentForm.loadAndPresentIfRequired(iOS): shows the form only if one is needed. If none is, the callback runs immediately.canRequestAds: only then start the Mobile Ads SDK and load ads. It always returns false until you have calledrequestConsentInfoUpdate.
Android (Kotlin)
Add implementation("com.google.android.ump:user-messaging-platform:4.0.0") (the version in Google's UMP guide as of November 2026).
val consentInformation = UserMessagingPlatform.getConsentInformation(this)
val params = ConsentRequestParameters.Builder().build()
consentInformation.requestConsentInfoUpdate(
this,
params,
{
UserMessagingPlatform.loadAndShowConsentFormIfRequired(this) { formError ->
// Consent gathering is complete (formError is non-null if the form failed).
if (consentInformation.canRequestAds()) {
// Initialize MobileAds and load ads here.
}
}
},
{ requestConsentError ->
// Log it. Ads may still be allowed if consent was gathered on an earlier launch.
},
)
For the privacy options entry point, check consentInformation.privacyOptionsRequirementStatus. If it says an entry point is required, show a button that calls UserMessagingPlatform.showPrivacyOptionsForm(activity, listener).
iOS (Swift)
Google's iOS guide recommends Swift Package Manager. The names below are the current ones:
let parameters = RequestParameters()
ConsentInformation.shared.requestConsentInfoUpdate(with: parameters) { requestConsentError in
guard requestConsentError == nil else { return }
Task { @MainActor in
try? await ConsentForm.loadAndPresentIfRequired(from: viewController)
if ConsentInformation.shared.canRequestAds {
MobileAds.shared.start()
}
}
}
For the entry point, check ConsentInformation.shared.privacyOptionsRequirementStatus == .required and call try await ConsentForm.presentPrivacyOptionsForm(from: viewController) from your own button. Google says not to check consent status in any other way.
The IDFA explainer on iOS
Apple's App Tracking Transparency (ATT) alert is a one-shot system prompt. Google lets you put an IDFA explainer message in front of it, explaining why you're asking. To create one, open Privacy & messaging, choose IDFA, click Create message, select your apps and languages, then Publish (steps). It is shown immediately before the ATT alert; unpublish it and the alert no longer triggers.
You also need the NSUserTrackingUsageDescription key in Info.plist and the AppTrackingTransparency framework linked. EEA users who haven't made a consent decision see the European regulations message first. The explainer is for everyone else, but only if you use Privacy & messaging for IDFA.
Testing with a debug geography
You can pretend to be in the EEA without leaving home. Debug settings only work on test devices, and Google says to remove them before release.
// Android
val debugSettings = ConsentDebugSettings.Builder(this)
.setDebugGeography(ConsentDebugSettings.DebugGeography.DEBUG_GEOGRAPHY_EEA)
.addTestDeviceHashedId("TEST-DEVICE-HASHED-ID")
.build()
val params = ConsentRequestParameters.Builder()
.setConsentDebugSettings(debugSettings)
.build()
// iOS
let debugSettings = DebugSettings()
debugSettings.testDeviceIdentifiers = ["TEST-DEVICE-HASHED-ID"]
debugSettings.geography = .EEA
let parameters = RequestParameters()
parameters.debugSettings = debugSettings
The hashed device ID appears in the log after the first requestConsentInfoUpdate call on Android. iOS simulators are test devices by default. To see the form again, call consentInformation.reset() (Android) or ConsentInformation.shared.reset() (iOS), for testing only. For the US states message, newer UMP versions have a regulated-US-state debug geography; Google's guide names it UMPDebugGeographyRegulatedUSState and says it needs UMP 3.1.0 or higher.
What happens if you don't set it up
Google's answer is limited ads, not a ban: users in the EEA, UK and Switzerland can't be served personalized ads, and traffic from a non-certified setup is limited. You may see lower earnings from those countries. If you want to see the impact, compare an EEA country's eCPM before and after in your AdMob reports. The free AdMob revenue calculator can turn a better eCPM into monthly earnings.
If your app is aimed at children, the TagForUnderAgeOfConsent setting stops the UMP SDK from requesting consent, and Google says you are responsible for using it in line with COPPA and other rules.
Once your messages are live, Storewatch shows AdMob estimated earnings, impressions and eCPM per app, so you can watch the trend alongside your App Store proceeds. For how earnings turn into a payment, see how AdMob payments work, and use the test ads guide while you test the consent flow.
Frequently asked questions
Do I need a consent message if my users are only in India?
Google's policy applies to users in the EEA, UK and Switzerland, and to applicable US states for the US states message. If you only target users elsewhere, those messages won't be shown to anyone. If your app is available worldwide, some users may be in those places, so check your AdMob reports by country.
Do I have to use Google's UMP SDK?
No. Google says you can use any CMP from its list of certified CMPs. The UMP SDK is the one that works with AdMob's Privacy & messaging tab.
Why does canRequestAds return false?
It always returns false until requestConsentInfoUpdate has been called.
How do I let users change their choice later?
Add a privacy options entry point, such as a Settings row. Check privacyOptionsRequirementStatus, and when it is required, show the form from your own button.
Can I show ads before consent is collected?
Call requestConsentInfoUpdate on every launch and wait for canRequestAds before starting ads. If a user in the EEA hasn't consented, only limited ads are eligible.