If you are using Google consent management solutions but do not see messages showing on your app in the EEA, the UK, and Switzerland, then you can follow these steps to help troubleshoot message deployment.
Google UMP SDK
- Ensure that you have implemented UMP SDK correctly in your app (Android instructions, iOS instructions). You can also watch this video with a step-by-step guide or check out the FAQ page (Android FAQs, iOS FAQs).
- Verify that you are waiting for consent to be collected prior to requesting ads. Ad requests sent prior to the user making a consent selection will not include a TC string; you can use the
canRequestAdsmethod of the SDK to simplify the process of waiting for consent (Android instructions, iOS instructions).
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.