Set up a consent banner and consent mode for your app ads

This article helps you to set up a consent banner and consent mode for your app ads for compliance with the EU user consent policy (EUUCP). Learn more About consent banner and consent mode for app ads.

How consent banner and consent mode work

When a user opens your app, a consent banner is displayed to give consent to software development kits (SDKs) that will read and write mobile identifiers. Once the consent banner is properly configured to collect user consent, and meets EU user consent policy (EUUCP) requirements, consent mode is activated and sends signals about consent status. If the user has consented, then SDKs will collect data for personalised ads. If the user doesn’t consent, identifying information won’t be sent. Instead, conversion modelling will leverage Google AI to solve for unknowns in the customer journey and provide more accurate reporting and optimisation.

Note: Consent mode is only required if you’re targeting audiences within the European Economic Area (EEA), however, it can be used by any advertiser who wants to provide their users with consent options.

Prepare for consent mode

You, along with your legal team, will need to determine what data you’re willing to send to Google, and choose advanced or basic consent mode, based on your requirements. If you’re working with remarketing audiences, remember to pass back consent signals for personalised advertising. If you have extensive customer data, you can consider adopting Customer Match. Ensure to send the correct consent signals by using the latest version of the consent mode API in your in-app code implementation.

You can also gain greater insights into how users interact with your app by better integrating SDKs into your app, empowering data-driven decisions that optimise user experience and performance.

Ensure that you’ve implemented and updated the Google Analytics for Firebase SDK. Default consent is optional, but can be set within the app manifest and will apply the setting automatically to any new users. Implement the setConsent in consent mode for different operating systems and programming languages.

If you're using a CMP, update the CMP SDK. Learn more about Google Analytics for Firebase SDK.

If you're working with an AAP, you will need to implement consent separately for the AAP SDK. Learn more about tracking app conversions with an App Attribution Partner.

Create a consent banner using a consent management platform (CMP)

If you want to set up a consent banner with one of the consent management platform (CMP) Partner programmes, then follow your CMP’s instructions to configure the banner. This will help you manage consent banners and proceed quickly through the consent management process. The CMP communicates to the SDK via consent mode, and the SDK adjusts its behaviour accordingly. Using a CMP Partner helps to ensure compliance with our privacy policies.

Create a custom consent banner

If your organisation requires you to build your own consent banner, you can set up a custom consent banner with a non-partner CMP or an in-house solution. To do this, you’d need to integrate with Google’s consent API yourself.

View this checklist to avoid common mistakes when implementing a consent mechanism that is compliant with the EU user consent.

Ensure that your consent banner complies with the EU user consent policy (EUUCP).

Integrate a custom banner with consent mode

Learn how to set up consent mode for iOS and Android.

Was this helpful?

How can we improve it?