After you add your apps to Ad Manager , create the European regulations message for eligible EEA (European Economic Area), UK, and Swiss users of your app.
Ensure you've added the Google User Messaging Platform SDK
to your app to enable it to gather consent.
Jump to
Create a European regulations message for your app
-
Sign in to Google Ad Manager.
-
Click Privacy & messaging.
-
Create a new message. On the European regulations message type card:
- Click Createif this is your first European regulations message.
- Click Manageif you've previously created an European regulations message. Then, click Create message.
- Select the apps in which this message will be displayed:
- Click Select apps.
- Select the desired apps.
- Click Confirm.
- Select the languages to display this message:
- Default language: Select the default language for when the user’s device cannot determine the language.
- Additional languages: Select additional languages for the message. Additional languages are shown if they match the user's device language. Languages should match your available app languages. You can edit the message text
for each of the "Additional languages." Example
If "Dutch" is selected as an additional language, a user's device set to Dutch shows the European regulations message in Dutch.
- In "User choices," make a decision for the "Do not consent" option.
- ON: This message will present users with a choice to not consent to your ad partners and your ad partners' purposes with a single click on the first page of the message. You can specify the countries in which the "Do not consent" button is displayed.
- OFF: This message will not display the "Do not consent" option to users.
- (Optional) Turn on Close (do not consent) to add a close button to your message. Users can click close to dismiss the message and decline consent to the use of their personal data.
- In the "Targeting" section, select one of the following options:
- Countries subject to GDPR (EEA, UK, and Switzerland): Display the European regulations message to site visitors in the EEA, the UK, and Switzerland.
- Everywhere: Display the European regulations message to all visitors.
- In the "Message name" field, enter a descriptive message name that will help you identify the message later. The name is shown only in the Privacy & messaging page and won't be visible to users.
- (Optional) Edit and format
the message to match your editorial and visual standards. If the message will be shown in more than one language, review the message in all of the selected languages before publishing.
- Add a privacy policy URL .
- When you're ready, click Publish. Alternatively, click Save draftto save a draft of the message.
Frequently asked questions for European regulations messages
Below are answers to some of the most frequently asked questions about European regulations messages.
What TCF version does the Google UMP SDK support?
The Google UMP SDK is IAB-certified for TCF v2.3.
What happens if I implement the Google UMP SDK and users do not consent?
Limited ads
serving applies if there is no consent for IAB TCF
Purpose 1 in accordance with the EU user consent policy
.
How can I report on TCF errors?
What is the ad-serving behavior for a user who sees the consent message in the EEA, UK, and Switzerland and then travels outside the region?
The Google Mobile Ads SDK will ensure that European regulations consent decisions from users apply only within EEA, UK, and Switzerland. This means a user who makes a consent decision in France then travels to Canada will not have GDPR treatment applied while they're in Canada.
How does AC String version 2 impact waterfall mediation for traffic from the EEA, UK, and Switzerland?
Google checks that ad technology providers and other programmatic demand sources don’t violate Google policy and have at least one legal basis for processing data prior to including them in the mediation waterfall.
Changes for Additional Consent v2 include an update to support vendors disclosed in the CMP. Disclosed vendors are eligible to participate in the mediation waterfall.Does the GDPR consent message populate the user’s previous selection?
The GDPR consent message visually displays the default consent choices and selections every time the message is displayed. However, the user’s consent choices are saved to local storage after the user makes a consent decision.
