Do You Need a Google-Certified CMP? What Google's Requirement Actually Means

TL;DR:

You need a Google-certified CMP if you show ads through Google AdSense, Ad Manager, or AdMob to users in the EEA, the UK, or Switzerland. It is a consent tool Google has approved that integrates with the IAB Transparency and Consent Framework (TCF, now v2.3). If instead you are an advertiser running Google Ads to your own website, you do not need a certified CMP, but you do need Google Consent Mode v2 configured correctly. The confusion between those two situations is what this article clears up.

Note: This is general information about Google's policies and consent practices, not legal advice.

"Do we need a Google-certified CMP?" is one of the most confused questions in digital advertising, because the honest answer is: it depends on which side of the ad transaction you are on. A lot of businesses either panic and think they need something they do not, or ignore a requirement that genuinely applies to them. Let us sort out exactly who needs what.

What a Google-certified CMP actually is

A Google-certified CMP is a consent management platform that Google has verified against its certification criteria. To be certified, a CMP must integrate with the IAB Europe Transparency and Consent Framework (TCF), send consent signals to Google's systems before tags fire, and maintain audit logs of consent decisions.

Google publishes an official list of certified CMPs. If a tool is not on that list, it is not certified, no matter what its marketing says.

Who actually needs one: publishers

Here is the group the requirement is really aimed at. If you use Google AdSense, Google Ad Manager, or Google AdMob to show ads on your site or app, and you serve personalized ads to users in certain regions, you must use a Google-certified CMP.

The regions and dates:

• EEA and UK: required since 16 January 2024.
• Switzerland: required since 31 July 2024.

If you are a publisher in this situation and you do not have a certified CMP, Google restricts or downgrades your ad serving to those users (often to "limited ads"), which directly reduces your programmatic revenue.

Who does not (technically) need one: advertisers

This is the part that trips people up. If you are an advertiser, meaning you pay Google to run Google Ads campaigns that drive traffic to your own website, and you are not showing AdSense, Ad Manager, or AdMob ads, then the certified-CMP requirement does not technically apply to you.

That does not mean you have nothing to do. If you advertise to or measure users in the EEA or UK, you still need Google Consent Mode v2 set up correctly, which is a different requirement. And if you have no EEA, UK, or Swiss traffic at all, a certified CMP is not required, though a solid consent setup is still best practice for privacy compliance.

The distinction that clears up the confusion

Put simply:

• Are you showing Google ads (AdSense, Ad Manager, AdMob) to EEA, UK, or Swiss users? You need a Google-certified CMP with TCF integration.
• Are you buying Google Ads to bring people to your own site? You need Consent Mode v2, not a certified CMP.
• Both? You need both.

Getting this right saves you from either over-buying a solution you do not need or, worse, losing ad revenue because you missed a requirement that did apply.

Where Consent Mode v2 fits

Consent Mode v2 is how Google's tags respond to a user's consent choice. When someone declines, it stops Google's tags from storing cookies, and Google models the conversions and behavior it can no longer directly observe.

There are two versions, basic and advanced. Advanced mode recovers significantly more measurement data. Google's own figures indicate advanced consent mode recovers a large share of the ad-click-to-conversion journeys that basic mode loses entirely, which matters a lot if you run paid campaigns in the EEA.

Whether you are a publisher or an advertiser, Consent Mode v2 depends on your consent banner sending the correct signals, which is exactly what a good CMP handles.

A note on TCF v2.3

The framework a certified CMP must support is the IAB TCF, and it has moved to version 2.3. As of 1 March 2026, Google requires newly generated consent strings to use TCF v2.3. A CMP still generating older strings risks having ad requests downgraded, so if you are a publisher, confirming your CMP is on v2.3 matters.

How to comply

If the requirement applies to you:

• Choose a CMP from Google's official certified list. Being certified is not optional or something you can self-declare.
• Make sure it integrates with the current TCF version (v2.3) and supports Google's Additional Consent specification for ad vendors outside the TCF list.
• Configure Consent Mode v2 so measurement respects consent.
• Confirm consent signals fire before tags, and that consents are logged.

Where ConsentBit fits

ConsentBit is a Google-certified CMP, listed on Google's official register of certified consent management platforms. It integrates with the IAB TCF, supports Google Consent Mode v2, and blocks tags until a visitor has given consent, so publishers can keep serving ads in the EEA, UK, and Switzerland, and advertisers can keep their measurement accurate and compliant. If the certified-CMP requirement applies to you, using a tool that is actually on Google's list is the point.

Frequently asked questions

1. Who needs a Google-certified CMP?

Publishers who show ads through Google AdSense, Ad Manager, or AdMob to users in the EEA, UK, or Switzerland. It has been required since 16 January 2024 for the EEA and UK, and since 31 July 2024 for Switzerland.

2. Do advertisers running Google Ads need a certified CMP?

Not technically. The certified-CMP requirement applies to publishers showing Google ads. Advertisers running Google Ads campaigns to their own site instead need Google Consent Mode v2 configured for users in the EEA and UK.

3. What happens if a publisher does not use a certified CMP?

Google restricts or downgrades ad serving to users in the affected regions, often limiting ads, which reduces programmatic revenue. Missing valid consent signals can also cause request failures.

4. Is Consent Mode v2 the same as a certified CMP?

No. A certified CMP is a Google-approved consent tool integrated with the IAB TCF, required for publishers. Consent Mode v2 is the mechanism by which Google's tags respond to consent, relevant to both publishers and advertisers. They are related but different requirements.

5. How do I know if a CMP is really Google-certified?

Check Google's official list of certified CMPs. If a provider is not on that list, it is not certified, regardless of its marketing claims. ConsentBit, for example, is on Google's certified list.

Need a CMP that is actually on Google's list?

If you serve ads in the EEA, UK, or Switzerland, using a genuinely certified CMP is not optional. ConsentBit is a Google-certified CMP with IAB TCF integration and Consent Mode v2 support, so your ad serving and measurement stay compliant.