15

I recently integrated the UMP SKD according to the documentation. Now I get an error report from Adbmob which states that a lot of ad requests fail because of the error "1.1". The troubleshooting page states that "Google, as a vendor, is not allowed under consent or legitimate interest.", but this is no help either. Has anyone had a similar error when using the UMP SDK and knows to resolve it?

13
  • 2
    Same issue here, I asked the AdMob SDK development team groups.google.com/g/google-admob-ads-sdk/c/u7l59JvrKb4/m/… but did not get a response yet. Even more annoying, it seems that because of this, no ads are shown at all to users that did not consent.. Commented Sep 16, 2020 at 16:28
  • 1
    Any solution for this yet? Google is silent.
    – edhnb
    Commented Oct 5, 2020 at 18:08
  • 3
    They say they are working on it, but from the responses on the AdMob google groups forum, I get the feeling that they still don't understand our problem and keep mixing up different issues. Even if I try to ask a question as explicitly as possible, I get a completely unrelated answer. The most recent developments are here: groups.google.com/g/google-admob-ads-sdk/c/6YdKIuuvC0g Commented Oct 8, 2020 at 8:57
  • 1
    Any news about this topic @BastiaanvandenBerg ?
    – NFC.cool
    Commented Oct 27, 2020 at 1:12
  • 1
    From the link that @BastiaanvandenBerg shared, it is correct that pressing Manage consent -> Submit results in no ads loading, because users need to give permission for Purpose 1 (which is off by default) However.. even when enabling all permissions, Ads are still not loading, as if the UMP still requires vendors to be enabled manually.
    – ZeroStatic
    Commented Oct 29, 2020 at 7:29

2 Answers 2

10

From my understanding, if one of your users taps on "Manage options", then, if you want him to receive personalized ads, he has to consent to :

  • Store and/or access information on a device (Purpose 1)
  • Create a personalized ads profile (Purposes 3)
  • Select personalized ads (Purposes 4)

And to consent / enable legitimate interest to :

  • Select basic ads (Purpose 2)
  • Measure ad performance (Purpose 7)
  • Apply market research to generate audience insights (Purpose 9)
  • Develop and improve products (Purpose 10)

For non-personalized ads, he has to consent to :

  • Store and/or access information on a device (Purpose 1)

And to consent / enable legitimate interest to :

  • Select basic ads (Purpose 2)
  • Measure ad performance (Purpose 7)
  • Apply market research to generate audience insights (Purpose 9)
  • Develop and improve products (Purpose 10)

(Source)

The "Google Advertising Products" should also be toggled on in order for AdMob to work. The thing is that NO OPTION is selected by default. So, the user should MANUALLY enable those options (and let's be honest, nobody knows that, and nobody wants to do that). The only thing we can do for the moment is to wait for Google to provide us a way to select some purposes and providers by default. Because in its current state, Funding Choice is unusable on mobile.

1
  • any update on this? I am so disappointed with admob, is it same with facebook ads do you know, I will switch if its not
    – cs guy
    Commented Mar 8, 2021 at 0:20
3

For everyone that needs a workaround until Google fixes the issue:

Disable Personalized Ads for EU users in AdMob -> Blocking Controls.

https://apps.admob.com/v2/pubcontrols/eu-user-consent enter image description here

Then disable the consent form on FundingChoices.

https://fundingchoices.google.com/ enter image description here

The users won't get a consent anymore and non-personalized ads are shown.

12
  • 2
    I am no expert on this topic, so I might very well be wrong. But as far as I understood, users still need to consent to the use of cookies, even if you show them only non-personalized ads. Because Google still uses cookies in that case, and according to GDPR, you need a consent for that. See the header "Non-personalized ads" on this page: support.google.com/adsense/answer/7670013?hl=en Commented Oct 15, 2020 at 6:29
  • But AdSense is not AdMob @BastiaanvandenBerg
    – NFC.cool
    Commented Oct 15, 2020 at 8:05
  • 1
    Sorry, wrong link. The exact same information is given for AdMob here: support.google.com/admob/answer/… Commented Oct 15, 2020 at 8:23
  • @BastiaanvandenBerg have you had any trouble doing it this way?
    – SAHM
    Commented Jun 26, 2021 at 20:39
  • 1
    @SAHM I am still using the legacy consent dialog. I tried the new one in one of my apps, but reverted to the legacy because it didn't work properly back then. It might have improved since, I haven't checked it for a while. Commented Jul 3, 2021 at 6:26

Not the answer you're looking for? Browse other questions tagged or ask your own question.