Notification

Get personalized optimization tips, understand your account health and set up completion on the improved "My AdMob page".

About European regulations messages

Under Google’s EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA) and the UK, and obtain their consent for the use of cookies or other local storage where legally required and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR).

Using Privacy & messaging and its integrated Funding Choices functionality, you can create and display a message to your users to help gather consents required under the General Data Protection Regulation. The message you create with Privacy & messaging lists the ad technology providers your site or app uses, and asks users to consent to the use of data to show personalized ads and for other purposes. You can also request consent for the use of data by your own site or app. Review the Guidelines for using Privacy & messaging for more information.

It is your responsibility to make sure your messages meet legal requirements.

Structure of a message

A European regulations message contains multiple "screens" (or "pages") that are shown to users depending on which buttons and links they click in your messages. The button options presented to users can be configured on a per-country basis and are based upon your selections in the "User choices" section during message creation.

Additional information

Support for the IAB TCF specification

European regulations messages created in Privacy & messaging have been updated to support the IAB TCF v2.2 specification.

Consent Mode

Google's Consent Mode allows other Google products you use (like Google Ads and Google Analytics) to respect your users' consent choices. If enabled, Google’s CMP can interpret your existing EEA, UK, and Swiss user consent choices for consent mode’s advertising purposes (including ad storage, personalization, and user data) and analytics storage. This setting streamlines ad measurement, personalization, and product optimization that require user consent, without altering your current consent message. You can choose to enable consent mode in the settings page of your European regulations message in the Privacy & Messaging tab. If this setting is enabled, it will apply to all of your European regulations messages shown on the web and in apps, but will not apply to messages shown on AMP. 

You can determine which consent mode implementation type you prefer, Basic or Advanced. Learn more about implementation types and how to configure your chosen implementation on web and on app: 

This setting is only applicable for those who want to use Google's CMP to obtain consent and provide transparency for the use of both our publisher and advertising products. If you already use another CMP for consent mode signal collection, review your legal requirements before enabling this feature to ensure a smooth user experience. Learn more about tag behavior with consent mode.

Google's CMP will only update consent choices for users who are shown a European regulations message, so be sure to set consent mode default consent states according to your desired behavior for users outside of the EEA, UK, and Switzerland. Learn more about setting region-specific consent mode behavior on web and leveraging the eu_consent_policy default value option on app.

Using Google’s Additional Consent technical specification

Privacy & messaging European regulations messages you create using the IAB Transparency and Consent Framework utilize Google’s “Additional Consent" technical specification. This is how Privacy & messaging transmits consent decisions to vendors that are not tagged with the “TCF” icon in the IAB Europe Transparency and Consent vendor list (Ad Manager, AdMob, AdSense).

The Additional Consent specification sends transparency and/or consent signals to vendors that have not yet registered on the IAB Europe Global Vendor List (GVL) (these vendors do not have the “TCF” icon in the vendor list). This specification enables publishers, Consent Management Platforms (CMPs), and partners to gather and propagate additional consent—alongside their TCF v2.2 implementation—for companies that are not yet registered with the IAB Europe Global Vendor List but are on Google's Ad Tech Providers (ATP) list.

Learn more about "Additional Consent" in Ad Manager, AdMob, or AdSense:

TFUA

If the publisher identifies a user as being under the legal age of consent and sends the TFUA signal on apps through the UMP SDK, the European regulations message will be suppressed for that user. Learn more about how ad serving behaves for users under the age of consent

Request consent for your own use of data

You can also use the European regulations message to establish transparency and consent for a set of IAB TCF data purposes—with a basis of either consent or legitimate interest—for your own use of data. Learn how to request consent for your own use of data.

Was this helpful?

How can we improve it?
true
Show your support to promote DEI in Gaming by turning intentions into action!

Check out the newly launched Diversity in Gaming website, where you can find video stories and written pledges from global gaming developers. This campaign centers on 3 pillars: diverse teams, diverse games and diverse audiences showing how diversity is not just good for gamers, but for business as well. Show your support by taking the pledge to promote DEI in Gaming and share it on social!

Learn More

5296692577727129876
true
Search Help Center
true
true
true
true
true
73175
Search
Clear search
Close search
Main menu
false
false
false
false