I am kind of confused as well. I also on not showing the consent dialog as it is intruding and most likely users will not even read it and just accept to continue using the app. And because of that, just set the hasUserConsent flag to false.
Wow, that is terrible. I think might stop providing my apps to Europe or at least stop advertising there. I had not read that.
How are you going to tell if someone is from the EU?
I am going to stop offering the game in the EU by turning off the country or regions in the app store. I already did it on Amazon. I am also going to turn off the country on Gamesparks. Gamesparks records the country based on ip. This is the best that I can do.
How about users who already downloaded your app?
I have a mechanism in Gamesparks to show a message at startup. They’ll get a message when they start the game stating that it is no longer available in that country. Probably get a bunch of bad reviews, but I have wasted way to much time on this already. I didn’t start making games to spend most of my time working on consents.
Agramonte: Halfway down their SDK and privacy policy: http://kidoz.net/website-and-kidoz-sdk-privacy-policy/
My Medium post discusses how to identify EU users and how I ask for consent, although it is more like disclosure given that it is for non-personalized ads.
I don’t really see it in that document. They say they collect personal and non-personal information and that consent is required if it is “required by law”. I also sent an e-mail to support and Kiddoz and they responded with basically the identical sentence. My question was: Do you collect personal information and do I need to ask for consent.
This is the personal information they collect:
Type of InformationHow Do We Use It? Approximate GEO location data We will use this information solely in order to determine the User’s country and to target the applicable advertising campaign. Meaning, if the User is located in a country where the official language is Spanish, the advertisement represented shall be in that language. Identifiers
· We will use the Identifiers we collect for two purposes: (i) targeting the applicable advertising campaign (for example, to enable ad frequency capping); and (ii) maintaining or internally analyzing the functioning of our Services.
· In any event, we use the Identifier solely for internal support purposes and/or in compliance with COPPA regulations
In any case, you do what you feel comfortable doing.
What is the difference between applying the consent parameters the current way vs waiting on the Consent SDK that Admob has. Do we have a rough ETA on the consent SDK update for the Admob plugin?
Also, does anyone think that Admob will eventually handle this server side, or are they indefinitely putting it on the developer to handle consent?
I would think eventually they could offer settings in the dashboard where we could handle this, OR they could do what Applovin is doing and just remove personalized ads from all EU countries. Seems like such a simple approach.
Not sure why they are so adamant about putting the burden on the developer when it seems like so much more work.
I am wondering if this feature is working correctly - because for my native iOS/Android apps I can see an obvious change on May 25th in AdMobs performance, but not for my app built with Corona.
Just to be sure - the parameter works for every request (including banners?).
Best regards!
Not possible to handle on the backend because even with non personalized ads, users need to consent to it. Basically users can say totally no to ads though you will need to provide them an alternative to access your service.
Hi everyone,
Please goto the 4th point in this article from Superawesome.
"…Now that you’ve covered the basics of compliance (parts 1-3), we can look at how to maximise advertising revenue from your kids audience without collecting any data, as required by COPPA and GDPR-K.
If you had previously written off your under-13 audience as ‘zero revenue’, think again. Provided you (1) set up your ad-serving infrastructure to be compliant, (2) offer a great ad experience for users, and (3) tap into age-appropriate demand, you should be able to generate more revenue per user than before."
In summary, I believe GDPR/GDPR-K does not intend to remove ad revenue from developers, rather enforces that we do it the right way by getting consent if personal identifiable information (PII) is needed for delivering personalized ads. Correct me if i am using the terms wrongly, non-personalized ads are basically contextual ads.
So, if we’re sending hasUserConsent as false to ad networks, does that not mean we only want to serve contextual ads which is not use PII to deliver ads? I am making the assumption that we’re only taking about ad network plugins.
If you’re practicing the above, but you have push notification, analytics plugin that is collecting PII, without getting user consent then that is a clear violation.
Ben.
p/s is there anyone here who is already serving ads to users with hasUserConsent as false to share their experience?
I think they are working on it or it is on the list.
Google is not letting people use these new features until May 25th. We can’t release our plugin early because of this.
Rob
Hi Rob,
the feature I mentioned is actually usable with older AdMob SDKs as well, however, the “npa” parameter seems to have no effect before May 25th.
So I don’t see why Corona could not implement the [request registerNetworkExtras: extras] function in its plugin before May 25h?
Best regards!
Hi,
I’m not sure what you meant by “the feature I mentioned is actually usable with older AdMob SDKs as well, however, the “npa” parameter seems to have no effect before May 25th.”
As stated on Admob’s documentation site:
Note: The Consent SDK will be made available by mid-May. The functionality, however, will not take effect until May 25, 2018. Please do not attempt to use these APIs before May 25, because they may disrupt ad serving on your app.
I can highlight this: Please do not attempt to use these APIs before May 25, because they may disrupt ad serving on your app.
Since Corona is providing access to Admob to a large amount of developers and not just implementing SDK to one app, it would be irresponsible for us to go against Google’s directions.
Or maybe I don’t understand you right? Can you elaborate on this topic?
I can. You don’t need the consent SDK for GDPR for google. I don’t plan on using it. All I did for my native app on iOS (read non corona app) is add this:
GADExtras \*extras = [[GADExtras alloc] init]; extras.additionalParameters = @{@"npa": @"1"}; [request registerAdNetworkExtras:extras]; [\_bannerView loadRequest:request];
The code for Android is also very similar although I don’t have it handy. This is supported in most recent versions of Admob including the one you are using currently in the plugin.
Edit:
Here is the Android Version for Admob:
Note: The code in this section can be used with any version of the Google Mobile Ads SDK. It can also be used regardless of whether you used the Consent SDK to gather consent.
The default behavior of the Google Mobile Ads SDK is to serve personalized ads. If a user has consented to receive only non-personalized ads, you can configure an AdRequest object with the following code to specify that only non-personalized ads should be returned:
Bundle extras = new Bundle();
extras.putString(“npa”, “1”);AdRequest request = new AdRequest.Builder()
.addNetworkExtrasBundle(AdMobAdapter.class, extras)
.build();
From the Google documentation the DFP version for iOS:
Note: The code in this section can be used with any version of the Google Mobile Ads SDK. It can also be used regardless of whether you used the Consent SDK to gather consent.
The default behavior of the Google Mobile Ads SDK is to serve personalized ads. If a user has consented to receive only non-personalized ads, you can configure an DFPRequest object with the following code to specify that only non-personalized ads should be returned:
DFPRequest *request = [DFPRequest request];
GADExtras *extras = [[GADExtras alloc] init];
extras.additionalParameters = @{@“npa”: @“1”};
[request registerAdNetworkExtras:extras];
Well then, it’s a good news! We’ll include the implementation in the next update.
Thanks for the info!
Thanks agramonte, this is what I meant.
Can you tell if this update will be released early enough for us to update our apps till May 25th?
Because - just to point that out - since there will be no option in AdMob’s dashboard to serve only non-personalized ads, this will be the only way for us to make our apps with AdMob compliant till May 25th. Without that option, AdMob will still always serve personalized ads.
Best regards!
We have a really tight schedule, but I’ll see what I can do. But isn’t it would be better to just wait for Admob consent specific apis to become available to you on 25th and then update your apps accordingly?