We want to update our apps as soon as possible, before May 25th.
If the NPA flag is already available and usable now, adding support for it now gives us the ability to start rolling out updates.
In the other forum post you said you had implemented this AdRequest configuration already (https://forums.coronalabs.com/topic/72096-gdpr-compliance/page-6?hl=gdpr).
Hence, if it is already implemented, and it works with your current AdMob version, please roll it out.
Hi perflubron,
As a second thought I can agree that adding this ability earlier should not harm anyone. Will give it more priority on a task system.
Thanks for your feedback, guys.
So glad to hear this!
Best regards!
Hey guys, sorry for a delay, updated plugin was released. You can check docs to learn more about gdpr compliance, it’s basically just one new parameter to load() options.
https://docs.coronalabs.com/plugin/admob/index.html
(Docs should be updated some time in the future, when our servers will be a little less busy)
Thank you guys!
Could you please provide the syntax here, since the docs don’t contain it yet?
Best regards!
Yeah, sure. Now you have additional parameter inside options table in load() method, called hasUserConsent. If you’ve got a user consent to use his data (to be gdpr compliant), just set this to true, set false otherwise.
Thanks! So hasUserConsent = false will send the AdMob-request with the extra “npa": "1” (?).
Is there a way to verify in the Corona Simulator console output that I am using the correct version of the AdMob-plugin, which “knows” the parameter?
Best regards!
So hasUserConsent = false will send the AdMob-request with the extra “npa”: “1” (?).
Correct.
Is there a way to verify
Sure, version of updated Corona Admob plugin is 1.2.4 for both iOS and Android. Basically, if you try to load an ad with hasUserConsent parameter with any value and plugin/sdk is too old, there will be an error in console log, saying that hasUserConsent is not a valid parameter.
thank you very much.
How are you guys (devs) planning to implement this? Are most of you going to have the consent pop-up (if so, how are you going to word it for AdMob?), or going to enable NPA (hasUserConsent=false) all the time?
@dislam: No pop-up for me for Ads. I set hasUserConsent=false. The user can always go to the consent page and grant me consent. At some point I might ask them for consent for some in-game reward and I am showing more ads when the consent is false.
I prefer your approach. I’m just wondering how much this would affect our revenue if we always set consent=fase and show non-personalized ads?
I’m trying to get an answer about the revenue question. There may not be a precise answer since there are many factors in what goes into the eCPM calculation.
Rob
What is the default for hasUserConsent ?
The Consent SDK is not in the latest Admob plugin yet right? Just want to confirm this.
Dislam, regarding revenue: in AdMob you can filter a report by targetting type. For me it looks like revenue will drop by around 5% by converting all personalized ads to context-based.
What is the default for hasUserConsent ?
It has no default value on Admob’s side, so there’s no default value for Corona plugin, it’s an optional parameter. Like, you may distribute your app to countries, that don’t fall for GDPR restrictions, so there is no need in user consent.
The Consent SDK is not in the latest Admob plugin yet right?
That’s correct, due to some limitations, ConsentSDK implementations is planned to future plugin updates.
Without the Consent SDK in place, the app is considered non-compliance right? I think it is not possible to know if the users are from EU or not.
Without the Consent SDK in place, the app is considered non-compliance right?
We’ve implemented all needed APIs to be GDPR compliant, it’s just not Consent SDK, it serves a slightly different purpose.
Am I right to say without the Consent SDK, we can only default the value of hasUserConsent to false?