After you add your sites to Ad Manager, create the European regulations message that you want to display to the eligible EEA (European Economic Area), UK (United Kingdom), and Swiss users of your sites.
Add the Google Publisher Tags (GPT) ad tag to your site to gather consent.
- Sign in to Google Ad Manager.
- Click Privacy & messaging.
-
Create a new message. On the European regulations message type card:
- Click Create if this is your first European regulations message.
- Click Manage if you've previously created an European regulations message. Then, click Create message.
-
Select the sites in which this message will be displayed:
- Click Select sites.
- Select the desired sites.
- Click Confirm.
- Select the languages for messages:
- Default language: The default language when the user’s device language is undetermined, or isn't adequately matched to “Additional languages.”
- Additional languages: Messages display to users in any of the “Additional languages” when matching the user’s device language. Languages selected should match your site's available languages. You can edit the message text for each of the "Additional languages."
Example
If you select “Dutch” in the “Additional languages” field, a user whose device is set to Dutch is shown the Dutch European regulations message.
- In “User choices”, make a decision for the Do not consent option. If turned on, this message presents your 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.
- (Optional) Turn on the Close (do not consent) option to add a close icon to your message. Users can click the close icon to dismiss the message and decline consent to your ad partners and their purposes.
- In “Targeting”, select one of the options:
- Countries subject to GDPR (EEA and UK): Display the European regulations message to site visitors in the EEA, the UK, and Switzerland.
- Everywhere: Display the European regulations message to all site 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.
Review the message in all selected languages before publishing.
- Enter your site's privacy policy URL.
- When you’re ready, click Publish. Or, click Save draft to save a draft of the message and exit the message builder without publishing.
European regulations message FAQs
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.2 across all SDK versions.
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?
You can use Error reports in the Ad Manager UI to troubleshoot TCF implementations.
What is the ad serving behavior for a user who sees the consent message in the EEA and UK, and then travels outside the EEA and UK?
The Google Mobile Ads SDK respects the user’s consent decision to apply the appropriate ad serving mode even once they leave the EEA and UK.
How does AC String version 2 impact waterfall mediation for EEA and UK traffic?
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.
