admob.load hasUserConsent parameter

Getting Started Newbie Questions
#1

hi - I just launched an app that uses admob on Google Play the other day, and I’m working through getting it ready for GDPR (it’s not for sale in Europe yet). I just noticed there’s a “hasUserConsent” param for admob.load. Is that brand new? I don’t recall seeing it the other day. 

What’s the default behaviour if this parameter is not used (presumably hasUserConsent = true?)

Also, if the param is set to false, how does the app behave differently? Does it stop showing ads altogether, or just shows generic ones? Thanks.

#2

I don’t think that it is that new. 

By default, hasUserConsent = false. The GDPR legislation requires that the user has to explicitly consent to you processing their personal information. Many games seem to do this by simply presenting a pop up when the app starts, briefly stating something like “In order to play this game, you have to consent to our terms of service and privacy policy.” and then offer only a single button “I agree” or “I consent”. That means that they can either consent or not play, which means you’ll be in the clear.

If you don’t get user’s consent, but you let them play your game anyway, then it is as you said, i.e. the advertiser(s) will serve only generic ads.

#3

I think I read somewhere that with admob even the non-targeted ads require user consent under GDPR.

#4

I haven’t used admob in a long while, but if that is the case, then it would mean that you can’t serve any ads via admob to users in the EEA unless the user first consents. Without having read more about the admob specific case, I can’t say whether this is correct or not.

#5

That is correct Admob requires user consent even for ads that are not targeted. It doesn’t make much sense to me. Why would you show non-targeted ads after getting consent?

#6

Yeah, it’s all baffling. Anyway, this is what it says: “Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA”

https://developers.google.com/admob/android/eu-consent

#7

I don’t think that it is that new. 

By default, hasUserConsent = false. The GDPR legislation requires that the user has to explicitly consent to you processing their personal information. Many games seem to do this by simply presenting a pop up when the app starts, briefly stating something like “In order to play this game, you have to consent to our terms of service and privacy policy.” and then offer only a single button “I agree” or “I consent”. That means that they can either consent or not play, which means you’ll be in the clear.

If you don’t get user’s consent, but you let them play your game anyway, then it is as you said, i.e. the advertiser(s) will serve only generic ads.

#8

I think I read somewhere that with admob even the non-targeted ads require user consent under GDPR.

#9

I haven’t used admob in a long while, but if that is the case, then it would mean that you can’t serve any ads via admob to users in the EEA unless the user first consents. Without having read more about the admob specific case, I can’t say whether this is correct or not.

#10

That is correct Admob requires user consent even for ads that are not targeted. It doesn’t make much sense to me. Why would you show non-targeted ads after getting consent?

#11

Yeah, it’s all baffling. Anyway, this is what it says: “Ads served by Google can be categorized as personalized or non-personalized, both requiring consent from users in the EEA”

https://developers.google.com/admob/android/eu-consent