UMP EU Consent Form targeting 'everywhere' only loading within UK/EEA

[Zippy]

Hi,

As the title states. If I set my EU Consent form to target the UK/EEA only, then everything works OK. In the UK/EEA, the EU Consent form loads and my revocation button appears. Furthermore, in the regulated US States, the form button appears and users can change their preferences from there.

However, if I set the targeting of my EU consent form in AdMob to 'everywhere', then it appears to be the same. When testing from outside the UK/EEA/US Regulated States, no form shows (and therefore no revocation button shows either).

UserMessagingPlatform.showPrivacyOptionsForm returns 'No Privacy Options form is required' when outside UK/EEA & Regulated US States (tested using ConsentDebugSettings.DebugGeography.DEBUG_GEOGRAPHY_OTHER).

I noticed in AdMob, it shows this message within the Geography section:

'GDPR Everywhere will only work for apps with the full UMP SDK. Otherwise, messages will only be shown in GDPR-impacted regions (EEA + UK + Switzerland)'

If I click the 'learn more' link, the page it takes me to doesn't elaborate on this. What is meant by the 'full UMP SDK'?

I'm using this in my build.gradle file:

implementation("com.google.android.ump:user-messaging-platform:3.1.0")

I'm using 'showPrivacyOptionsForm' and 'loadAndShowConsentFormIfRequired' to show the forms.

Why isn't this working, and what do I need to do to get 'everywhere' targeting working?

Thanks!

[Mobile Ads SDK Forum Advisor]

Hi,

Thank you for contacting the IMA SDK support team.

It is expected behaviour.The consent form is expected to be displayed only when EEA/US locations are selected. For non-EEA locations, the consent form will not be shown.

Kindly use this link to changing location and getting the consent form.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-03-03 10:57:37Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH5El:ref" (ADR-00290827)

[Zippy]

Hello,

Thanks for you reply. However I'm not sure my question was understood.

You say that the EU Consent form should be displayed only to UK/EEA users. However in AdMob, there is a Geography section which allows you to change the targeting from only showing the EU consent message in 'Countries subject to GDPR (EEA, UK and Switzerland)' or to all app users ('Everywhere', regardless of location). Here is what I mean (taken from AdMob):

If you click the 'Learn more' link, you are taken to a page which basically confirm this:

1. In the 'Targeting' section, select one of the following options:
   • Countries subject to GDPR (EEA and UK): Display the European regulations message to app visitors in the EEA, the UK and Switzerland.
   • Everywhere: Display the European regulations message to all app visitors.

It does not however elaborate on the message shown in AdMob (see image above), in that it does not explain what is meant by 'the full UMP SDK'.

So as you can see, there is the option to display the EU consent message to all users, regardless of their location. However for me, it is not working. So just to clarify, my questions are:

1. What is meant by 'full UMP SDK'? Full compared to what?
2. Why isn't the 'everywhere' targeting working in my case?
3. What do I need to do to get GDPR Everywhere working in my app?

The link you sent in your reply is about ConsentDebugSettings.DebugGeography which as I stated in my original post, I'm already using for testing. This does not answer the query.

I would be grateful if you could address each of the 3 question above. Thanks again!

[Mobile Ads SDK Forum Advisor]

Hi,

I will check with our team regarding your query and one of my team members will reach out to you once we have an update on this. Meanwhile, your patience is highly appreciated.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-03-04 10:09:54Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH5El:ref" (ADR-00290827)

[Zippy]

Any update on this? Thanks.

[Mobile Ads SDK Forum Advisor]

Hello,

When using DebugGeography.OTHER, it is another way of force suppressing messaging. What you are experiencing is the current intended behavior. If the form is showing up when using DebugGeography.EEA and you have GDPR everywhere enabled, you should be fine. 
 

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-03-18 13:34:17Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH5El:ref" (ADR-00290827)

[Zippy]

Hello. Thank you for the reply.

You said:

'When using DebugGeography.OTHER, it is another way of force suppressing messaging'

1) Could you please elaborate on what you mean here as it's not quite clear to me. Are you saying that using DebugGeography.OTHER simply prevents any consent forms from appearing and does not actually simulate you being in an area other than the EEA/US Regulated state?

If this is the case, is there no other way of testing to make sure the form does indeed appear for 'other' areas? I would like to confirm that this is working before publishing.

2) Also, please could you confirm what is meant by 'GDPR Everywhere will only work for apps with the full UMP SDK'? 'Full' compared to what?

3) Finally, one other related question. If GDPR everywhere is set, what is the intended behaviour for users in US regulated states? Do they see the GDPR form only, or both the GDPR and US Regulated State forms?

Thanks again!

[Mobile Ads SDK Forum Advisor]

Hello,

1.) Yes, that is today's current behavior. We intend to update that behavior to reflect the behavior in a production application. To test in the immediate-term, if it's showing up with EEA and you have GDPR everywhere enabled, you should be fine.

2.) The "full" wording needs updating, this refers only to the UMP SDK itself. There is no "full" or "not full" SDK. You can ignore. 

3.) If you've set up a US States form in your AdMob UI and the user is in a US regulated states, the US States form will show. Otherwise, the GDPR form will show. 

Thanks,
 

Justin Malandruccolo Mobile Ads SDK Team

Feedback
How was our support today?
               

[2025-03-19 21:13:08Z GMT] This message is in relation to case "ref:!00D1U01174p.!5004Q02vH5El:ref" (ADR-00290827)