Google's certified CMP requirement: what AdSense publishers need for EEA, UK and Swiss traffic
Key takeaways
- AdSense, Ad Manager and AdMob publishers must use a Google-certified consent management platform (CMP) integrated with the IAB TCF to serve personalized ads to users in the EEA, the UK and Switzerland.
- The requirement took effect on 16 January 2024 for the EEA and the UK, and on 31 July 2024 for Switzerland.
- Traffic from a non-certified CMP is not eligible for personalized ads; Google says it may still be eligible for non-personalized ads or limited ads.
- EEA, UK or Swiss ad requests with no TCF signal at all are reported as error 10.1, and Google attempts to serve limited ads.
- Google's own European regulations message in Privacy & messaging is a certified CMP (TCF CMP ID 300).

To serve personalized ads to visitors in the European Economic Area (EEA), the United Kingdom or Switzerland, AdSense requires a consent management platform (CMP) that Google has certified and that integrates with the IAB Europe Transparency and Consent Framework (TCF). The rule has applied since 16 January 2024 for the EEA and the UK, and since 31 July 2024 for Switzerland. Without it, those visitors only get non-personalized or limited ads.
This guide explains what the requirement covers, what happens to your ad requests in each scenario, and how to check that your setup qualifies. It describes Google’s product rules, not the law itself, and is not legal advice.
What exactly does Google require?
Google’s help article for publishers states that partners using AdSense, Ad Manager or AdMob “are required to use a consent management platform (CMP) that has been certified by Google and integrates with the IAB’s Transparency and Consent Framework (TCF) when serving personalized ads” to users in the covered regions. Google presents this as the way to comply with its EU user consent policy, which asks you to obtain legally valid consent for cookies or local storage where legally required, and for the collection, sharing and use of personal data for ads personalization.
| Region | Certified TCF CMP required from | Covered countries |
|---|---|---|
| EEA | 16 January 2024 | EU member states plus Iceland, Liechtenstein and Norway |
| United Kingdom | 16 January 2024 | UK |
| Switzerland | 31 July 2024 | Switzerland |
Two points are often misread:
- The requirement is about personalized ads. It does not ban ads for visitors without consent. It decides which serving mode your traffic is eligible for.
- Certification is narrow. According to the CMP-facing version of the page, Google assesses CMPs “against certification criteria focused on TCF compliance” and “does not check CMPs for full compliance with the TCF or applicable privacy laws”. CMPs must recertify at least every twelve months.
What happens to ads in each scenario?
The table below combines Google’s requirement page with the error codes in its TCF troubleshooting article. It applies to requests from the EEA, the UK and Switzerland.
| Your setup | Best serving mode available | What Google reports |
|---|---|---|
| Certified CMP, user consents to everything Google needs | Personalized ads | No error |
| Certified CMP, user refuses personalization but consents to Purpose 1 | Non-personalized ads | No error |
| Certified CMP, user refuses Purpose 1 (device storage) | Limited ads, if enabled | Error 1.2 |
| Non-certified CMP that writes a valid TC string | Non-personalized or limited ads | Error 9.1: Google “will attempt to serve non-personalized ads” |
| No CMP, no TCF signal on the request | Limited ads, if enabled | Error 10.1: Google “will attempt to serve limited ads” |
| Malformed or unparseable TC string | Limited ads, or none | Errors 2.1a to 2.2c (see note) |
Note: the troubleshooting article says Google “will attempt to serve limited ads” for misconfiguration errors, while Google’s TCF integration article states “We do not serve an ad if the TC string is invalid”. Treat any parsing error as a revenue risk and fix it.
Limited ads are on by default in AdSense and can be turned off under “Brand Safety”, then “Blocking controls”, then “Ad serving”. If you turn them off, the rows that fall back to limited ads may get no ads at all. The personalized, non-personalized and limited ads guide explains what each mode collects and why their revenue differs.
How do I check whether my CMP is certified?
Google publishes the list of certified CMPs inside the publisher article and says it is “updated weekly”. Each row gives three things:
- Certified CMP: the vendor name. Entries marked “(Private)” are in-house CMPs run by a single publisher group and are not for sale.
- TCF CMP ID: the number IAB Europe assigned to the CMP. It is written into every TC string, which is how Google recognizes the CMP on each ad request.
- Platform: “Web”, “App”, “CTV” or combinations. A CMP certified only for app does not cover your website.
When we checked the list on 18 November 2026 it had 146 entries. Examples include Google LLC CMP (ID 300), UserCentrics (5), Sourcepoint Dialogue (6), Didomi (7), OneTrust / CookiePro (28), Iubenda (123), Cookiebot (134), Complianz (332) and CookieYes (401). The list changes, so always check the live page rather than a copy.
To confirm what your site actually sends, decode a real TC string. Open your page from an EEA connection or with your CMP’s test mode, run __tcfapi('addEventListener', 2, (d) => console.log(d.cmpId, d.tcString)) in the browser console, and compare the cmpId with the list. If it does not match the vendor you think you use, a plugin or theme may be loading a second CMP.
Do I have to use Google’s own CMP?
No. Google’s How the Google CMP works page says the choice between Google’s CMP and a third-party CMP is “up to you”. The trade-offs:
| Option | Strengths | Limits |
|---|---|---|
| Google’s European regulations message (Privacy & messaging) | Free, certified, already wired to AdSense, supports TCF and Google’s Additional Consent specification | Needs the AdSense code on the page; limited styling; does not block your other scripts (analytics, embeds) |
| Commercial certified CMP | Manages all your vendors and cookies, script blocking, consent logs, multi-site dashboards | Paid plans for most traffic levels; you must configure Google (vendor ID 755) correctly |
| In-house CMP | Full control | Must register with IAB Europe, then apply to Google for certification |
If you choose Google’s message, the Privacy & messaging GDPR guide walks through each setting.
Which TCF version must the CMP support?
The certification sits on top of the TCF, and the TCF moved on after the requirement launched:
- TCF v2.3: Google’s AdSense help states that “TCF v2.3 is mandatory for all TC strings generated on or after March 1, 2026”. Strings created after that date without the “Disclosed vendors” segment, or without Google in it, are reported as error 1.4, and Google says such requests may default to limited ads. Until the end of February 2026, Google treated v2.3 strings like v2.2 strings without validating that segment; v2.2 strings created before March 1, 2026 remain accepted.
- TCF v2.4: IAB Europe’s notice of 16 July 2026 set 23 October 2026 as the deadline for CMPs to implement the new disclosures on websites (23 February 2027 for apps and CTV). Google’s “About European regulations messages” article says its own messages now support TCF v2.4.
Commercial CMPs handle these upgrades for you, but only if you run a current version of their script. A CMP snippet pasted years ago and never updated is a common cause of 1.4 errors. The TCF for publishers guide covers purposes, legal bases and the TC string in detail.
How do I move to a certified CMP?
- List where your EEA, UK and Swiss traffic lands and which scripts set cookies there (ads, analytics, video, social embeds).
- Pick a CMP from Google’s list that is certified for your platform (“Web” for a website).
- Add Google Advertising Products (vendor ID 755) to the CMP’s vendor list, with consent for Purposes 1, 3 and 4 and legitimate interest or consent for Purposes 2, 7, 9 and 10, which is what Google’s TCF integration article lists for personalized ads.
- Load the CMP stub before the AdSense tag. AdSense reads the TC string automatically from a TCF CMP on the page; you do not pass it by hand.
- Remove any old banner that also writes TC strings, so only one CMP runs.
- Check the Policy center for TCF errors after a few days. Google says it shows errors detected over the last 7 days, with the domain, error code and error count.
What do Google’s consent audits check?
Separately from the automatic TCF checks, Google runs periodic audits of sites under the EU user consent policy. Its audit help page says reviewers visit a site “as a user would” and lists the issues they flag, including a missing banner, no mention of “ads personalization” on the first layer, no affirmative consent action, no link to Google’s Business Data Responsibility site (business.safety.google/privacy), cookies set before consent, and a CMP that is not certified or not set up correctly.
If a publisher does not fix the issues within the timeframe given, Google says that “only Limited Ad / programmatic limited ads will be eligible to serve (if programmatic limited ads are enabled)”. Regulatory issues of this kind appear in the Policy center.
Common mistakes
- Two CMPs on one page. A WordPress plugin banner plus Google’s message, for example. The TC string you get may come from the wrong one.
- Google not in the vendor list. Error 1.1 means Google, as a vendor, had neither consent nor legitimate interest. Some CMPs require you to add vendors manually.
- Using a cookie banner that is not a TCF CMP. A generic accept/reject banner produces no TC string, so EEA traffic falls into error 10.1. See why open-source banners are not certified CMPs.
- Geo-blocking the banner to the EU only. The UK and Switzerland are covered too, and the EEA includes Iceland, Liechtenstein and Norway.
- Assuming certification equals legal compliance. It does not, as Google states explicitly.
Frequently asked questions
Do I need a Google-certified CMP if I have no visitors from Europe?
The requirement only applies to ad requests from users in the EEA, the UK and Switzerland. If none of your traffic comes from those regions, it has no practical effect. Most public sites receive at least some European visits, though, and those visits would be treated as having no TCF signal, so Google would attempt to serve limited ads to them.
Is Google's own Privacy & messaging consent message certified?
Yes. Google lists "Google LLC CMP" with TCF CMP ID 300 in its list of certified CMPs, and the AdSense help center states that the European regulations message in the Privacy & messaging tab is certified under the requirement. It is free to use inside AdSense, but it only covers sites tagged with your AdSense code.
What happens to my ads if my CMP loses its certification?
Requests carrying a TC string from a CMP that Google has not certified are flagged with error 9.1 in the Policy center, and Google says it will attempt to serve non-personalized ads to them. Certified CMPs must recertify at least every twelve months, so check the list periodically and ask your vendor about its status.
Does a certified CMP make my site GDPR compliant?
No. Google states that it assesses CMPs against criteria focused on TCF compliance and does not check them for full compliance with the TCF or with privacy laws. Certification makes your traffic eligible for personalized ads; legal compliance of your banner, texts and practices remains your responsibility.
Sources
- Google consent management requirements for serving ads in the EEA, the UK, and Switzerland (for publishers) · Google AdSense Help
- Google consent management requirements for serving ads in the EEA, the UK, and Switzerland (for CMPs) · Google AdSense Help
- EU user consent policy · Google
- Troubleshooting IAB EU TCF v2.3 implementation · Google AdSense Help
- Fix issues with your EU User Consent Policy consent audit · Google AdSense Help
Related guides
- 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.
- AdSense Privacy & messaging: building the European regulations (GDPR) message
Build the GDPR consent message in AdSense Privacy & messaging: every setting, the two- vs three-button layout, testing, troubleshooting and what it cannot do.
- Personalized, non-personalized and limited ads: the three AdSense serving modes compared
How AdSense picks personalized, non-personalized or limited ads from consent signals, what each mode still collects, the ad code switches and the setting to check.
- UK and Switzerland: cookie consent rules and what AdSense requires
How UK PECR, as amended in February 2026, and Swiss law on cookies differ from EU rules, and why Google still requires a certified TCF CMP for both countries.
- Open-source cookie banners with AdSense: what they can and cannot do
Klaro, CookieConsent and tarteaucitron.js are solid free banners, but none writes a TCF string or is Google-certified. What that means for AdSense in Europe.