Troubleshooting European regulations messages

If you are using Google consent management solutions but do not see messages showing on your site or app in the EEA, the UK, and Switzerland, then you can follow these steps to help troubleshoot message deployment.

Web

  • Google consent management solutions cannot serve if the site’s referrer policy does not allow the referrer to be included in cross-origin requests. 
    • Resolution: Publishers should ensure that their referrer policy allows the HTTP referrer header to be included in cross-origin requests. The default strict-origin-when-cross-origin is sufficient.
  • Google consent management solutions can only serve from the top-level window.
    • Resolution: Ensure that your gpt.js script tag or Privacy & messaging tag is placed on the top-level window.
      Privacy & messaging tag guidance is only relevant for publishers also using ad blocking recovery messages.

Apps

Google UMP SDK

Ad unit deployment

  • Ad unit-deployed messages are only able to show in an app open or interstitial ad unit; if your app does not use these formats, you are not eligible to use ad unit deployment. If you do not request these formats until late in your user flow and you request other formats before that, you may not be a good fit for ad unit deployment and should implement the UMP SDK or any other Google-certified CMP.
  • Your app must use the latest version of the Google Mobile Ads SDK: version 22.5.0+ for Android or version 10.8.0+ for iOS. You can use the GMA SDK reporting dimension in your AdMob account to check this information.
  • Ad unit deployment works best for publishers that use AdMob as their mediation platform. Off-platform publishers should implement the UMP SDK or any other Google-certified CMP.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
12239277328298265893
true
Search Help Center
true
true
true
true
true
148
false
false