AdSense Privacy & messaging: building the European regulations (GDPR) message
Key takeaways
- AdSense's Privacy & messaging tab includes a European regulations message, a consent banner that Google lists as a certified TCF CMP (Google LLC CMP, ID 300).
- The message can show two buttons (Manage options, Consent) or three (Do not consent, Consent, Manage options); the "Do not consent" button can be enabled per country.
- When users reopen the message to change their choice, it always shows the three options, which Google says is an IAB TCF requirement.
- The message only appears on pages carrying the AdSense code from the same account, and it fails if the site's referrer policy blocks the cross-origin Referer header.
- You can preview the published message anywhere by adding ?fc=alwaysshow&fctype=gdpr to a page URL.

AdSense includes a free consent banner for European visitors: the European regulations message, built in the “Privacy & messaging” tab. It is a Google-certified, IAB TCF-based CMP that asks EEA, UK and Swiss users for consent on behalf of Google and the ad partners you select, then passes their choices to your AdSense ads. It is the quickest way to meet Google’s certified CMP requirement, with real limits on design and scope.
This walkthrough follows Google’s help center as of November 2026. Google states that “it is your responsibility to make sure your messages meet legal requirements”; nothing here is legal advice.
What does the European regulations message do?
According to Google’s About European regulations messages, the message “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 your own use of data. Under the hood it writes a TCF string, plus a string in Google’s “Additional Consent” format for ad partners not registered in the TCF. Google says the messages now support the IAB TCF v2.4 specification.
Google lists it as “Google LLC CMP” with TCF CMP ID 300 in its list of certified CMPs, so EEA, UK and Swiss traffic that consents through it is eligible for personalized ads.
What do users see: two buttons or three?
The layout depends on the “Do not consent” setting.
| Element | Two-button message | Three-button message |
|---|---|---|
| First layer buttons | “Manage options” and “Consent” | “Do not consent”, “Consent” and “Manage options” |
| “Manage your data” screen | Purposes, all deselected by default, with “Accept all” and “Confirm choices” | Same |
| “Vendor preferences” / “Confirm our vendors” | Vendors, deselected by default | Same |
| Closing without choosing | Only if you enable the close icon, which counts as “do not consent” | Same |
Three rules come from the IAB TCF and cannot be changed:
- Purposes and vendors on the second layer start deselected. Google’s IAB requirements page says each toggle must default to “no consent”, “no opt-in” or “off”.
- The “Consent” button text can be edited, but it must express a clear affirmative choice. Google’s example: “Yes, I consent” is acceptable, “Proceed to site” is not.
- If a user clicks “Confirm choices” without changing anything, consent purposes stay unconsented and legitimate-interest purposes stay on.
When a user reopens the message (from a revocation link or your privacy settings), it always shows “Do not consent”, “Consent” and “Manage options”, and previous choices appear reset to “Do not consent”. Google says this standardized display “is an IAB TCF requirement”.
How do I set up the account-level settings first?
Before building a message, review “Privacy & messaging”, then the European regulations card, then “Settings”. Google’s CMP setup article describes the main choice:
- Ad technology providers: keep the “Commonly used set of ad technology providers” (the default) or pick a “Custom set”. Selected providers, including Google, may use data for ads personalization and measurement. Fewer providers make a shorter vendor list, but may reduce competition for your inventory.
- Optional creative checks: you can choose to check reservation and RTB creatives for consent, with custom ad partner URLs to avoid filtering unknown ones.
- Consent Mode: an option to let Google’s CMP pass users’ choices to other Google products (see below).
These settings apply to AdSense for content. AdSense for Search has its own instructions.
How do I create the message?
Google’s creation steps, in order:
- Make sure the AdSense code is on your site and the site is added to your account.
- Go to “Privacy & messaging”. On the “European regulations” card, click “Create” (first message) or “Manage”, then “Create message”.
- Click “Select sites”, choose sites, and “Confirm”.
- Choose a default language and any “Additional languages”. The message is shown in the language matching the user’s device. “English (en)” and “English (en-GB)” are separate languages to edit.
- Under “User choices”, turn the “Do not consent” option on or off, and pick the countries where it appears.
- Optionally turn on “Close (do not consent)” to add a close icon that declines consent.
- Optionally turn off “Optimize my consent message” if you do not want Google to automatically show a message optimized for your visitors.
- Give the message an internal name, edit the text and styling, and review every language.
- Enter your privacy policy URL. Your privacy policy should match what the message says.
- Click “Publish” (or “Save draft”).
How do I test the message?
Google’s Privacy & messaging overview lists URL parameters that force a published message to display regardless of the visitor’s region:
| Parameter | Shows |
|---|---|
?fc=alwaysshow |
Any published message (use when only one type is published) |
?fc=alwaysshow&fctype=gdpr |
The European regulations message |
?fc=alwaysshow&fctype=ab |
The ad blocking recovery message |
Test in a browser that clears cookies, such as an incognito window, otherwise a stored choice hides the message. The parameters preview the look and feel; to verify signals, check the TC string in the console with __tcfapi('addEventListener', 2, console.log).
How does it interact with Consent Mode?
In the message settings you can enable Consent Mode. Google explains that the CMP then interprets EEA, UK and Swiss choices for Consent Mode’s advertising purposes (ad storage, personalization, user data) and analytics storage, so tags like Google Analytics and Google Ads respect them. It applies to all your European regulations messages on web and apps, not to AMP.
Two caveats from Google’s page: the CMP only updates consent for users who see the European message, so you must set default consent states for everyone else; and if another CMP already sends Consent Mode signals, enabling this could conflict. The Consent Mode v2 guide explains why Consent Mode is not what AdSense itself reads.
Why is my message not showing?
Google’s troubleshooting article lists four causes:
| Symptom | Cause | Fix |
|---|---|---|
| No message anywhere | Outdated or missing AdSense tag | Use the current AdSense code on every page |
| No message on some sites | Tag belongs to another AdSense account | Configure the message in the account whose tag is on the page |
| No message, no error | Referrer policy blocks the Referer on cross-origin requests | Allow it; the default strict-origin-when-cross-origin is sufficient |
| No message on embedded pages | Tag runs inside an iframe | Place the tag in the top-level window |
Also check that you are testing from (or forcing) a covered region, that no other CMP already stored a choice, and that the page is not AMP, since AdSense European regulations messages “don’t support Accelerated Mobile Pages (AMP)”.
What are the limits of Google’s message?
- It covers Google’s ad stack, not your whole site. It does not block analytics, video embeds or social widgets before consent. If those set cookies, you need another tool or your own conditional loading.
- It depends on the AdSense tag. Pages without your AdSense code get no message.
- Design is constrained. You can edit text, colors, fonts and logo, not the structure required by the TCF.
- Messages are shared across products. If you also use Ad Manager or AdMob, Google notes that changes in one account affect the others.
- Legal review is yours. Google gives the tool; you decide whether its wording, button choices and vendor list fit the rules where your visitors live.
If you need a single banner for all your scripts, a commercial certified CMP is usually the better fit. If AdSense is your only third-party script, Google’s message is often enough. The same tab also hosts the ad blocking recovery message.
Frequently asked questions
Is the AdSense European regulations message free?
Google does not charge for Privacy & messaging. The message is part of your AdSense account and Google lists it among certified CMPs as "Google LLC CMP" with TCF CMP ID 300. The cost is functional: it only shows on pages with your AdSense code and does not block your other cookies or scripts.
Should I enable the "Do not consent" button?
Google lets you choose, and you can enable it only for selected countries. Some European regulators expect refusing to be as easy as accepting on the first layer, so check the guidance that applies to your audience. Expect a higher refusal rate with three buttons; refusing users can still receive limited ads if that setting is on.
Why does my European regulations message not show up?
Google's troubleshooting list: the page needs an up-to-date AdSense tag from the same account where the message is configured, the referrer policy must allow the Referer header on cross-origin requests (the default strict-origin-when-cross-origin works), and the tag must run in the top-level window, not inside an iframe. Messages also do not support AMP.
Can the AdSense message also manage my Google Analytics consent?
Partly. In the message settings you can enable Consent Mode, so Google's CMP passes EEA, UK and Swiss users' choices to other Google tags such as Google Analytics and Google Ads. It does not block non-Google scripts, and you still need default consent states for users outside those regions.
Sources
- About European regulations messages · Google AdSense Help
- Create a European regulations message · Google AdSense Help
- How IAB requirements affect European regulations messages · Google AdSense Help
- Troubleshooting European regulations messages · Google AdSense Help
- About Privacy & messaging · Google AdSense Help
- Set up and manage your Consent Management Platform (CMP) · Google AdSense Help
Related guides
- Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Since 2024 AdSense needs a Google-certified TCF CMP for personalized ads in the EEA, UK and Switzerland. Dates, what happens without one, how to check yours.
- IAB TCF v2.3 for publishers: what Google requires, what changed from v2.2, and v2.4
TCF v2.3 is mandatory for TC strings created since March 1, 2026. What changed from v2.2, Google's dates, the purposes AdSense needs, and the v2.4 update.
- Consent mode v2 and AdSense: two consent signals, one site
Google consent mode v2 explained for AdSense sites: why AdSense reads the TCF string, not consent mode, and how to keep Analytics and AdSense signals aligned.
- Ad blocking recovery in AdSense: asking visitors to allow ads
How the ad blocking recovery message in AdSense Privacy & messaging detects ad blockers, asks visitors to allow ads, and where policy and UX limits apply.
- Writing a privacy policy for a site that shows AdSense ads
What a privacy policy must say on a site running AdSense: Google as a party, cookies, the link Google requires, consent withdrawal, US opt-outs and a template.