The Mobile Advert plugin is not compatible with the latest changes in AdMob SDK regarding user consent for GDPR...

I guess we should report this to Scirra team. Any idea how to do it?

Targeted Ads are different than normal ads?

Yes.

So users will stil get normal ads but not get ads specifically targeted to them? This will kill revenue fckk

In the context of AdMob: yes. It will be interesting to see in the coming days/weeks the best practices used by others publishers to invite their users to give their consent... But it will be limited as I think you cannot convince your users by rewarding them

Yes, GDPR is affecting the ad business. You must get the user consent to display targeted ads.

Regarding Google/Admob (which is the ad provider behind the Mobile Advert plugin in Construct), they will stop displaying targeted ads if you don't have the user consent. The impact for the publisher is hard to say: maybe you will have less ad revenue without the user consent but higher ad revenue with user consent...

If you plan to display ads using the Mobile Advert plugin, i see the following actions:

For you, the publisher:

• if the user is based in Europe
• at app launch, you display a popup asking the user to confirm if he agrees to see targeted ads
• you store the user consent locally to avoid displaying the popup at every app launch
• you add a submenu in the settings of your app to allow the user updating his consent

For Scirra/Construct:

• to update their Mobile Advert plugin to comply with the new AdMob SDK (more info here:

  developers.google.com/admob/and ... le_ads_sdk)

In a nutshell, with the new GDPR compliant AdMob SDKs the publisher can forward the user consent flag. This way Google/AdMob can stop displaying targeted ads.