An ad-supported site may need a consent management platform (CMP) for two separate reasons: the ad platform's own rules and the data protection expectations where your visitors are. Google requires a Google-certified CMP integrated with the IAB Transparency and Consent Framework (TCF) to serve personalized ads through AdSense, Ad Manager or AdMob to users in the European Economic Area, the United Kingdom and Switzerland. The Google page that sets this out does not state a CMP requirement for Turkey, where the data protection authority's cookie guide expects explicit consent for advertising cookies. So the answer is not one rule but a table that depends on visitor region and ad type. Nothing here is legal advice.
This guide is for publishers with ad revenue and for site owners with European or Turkish traffic. How lost consent affects analytics, and how consent mode works, is covered in a separate article on cookie consent, privacy and measurement loss. The focus here is choosing and testing a CMP while protecting ad revenue.
Why ad platforms require a certified CMP
A CMP shows visitors which cookies and similar technologies are used and why, records their choice and passes that choice to the site and to ad technology providers. The banner is only the visible part. Record keeping, reopening preferences and signalling the choice downstream are the rest of the job.
What TCF is for
IAB Europe describes the Transparency and Consent Framework (Opens in a new tab) as a voluntary standard and an accountability tool that relies on standardisation to help with parts of the ePrivacy Directive and GDPR. It names three groups: publishers, vendors such as ad servers and measurement providers, and CMPs, which build the notices and banners and record users' choices. IAB Europe says TCF v2.3 launched in April 2025 and participants had until 28 February 2026 to adopt it, a date that has now passed. Ask any CMP vendor which version it supports today.
What Google requires
Google's page on consent management requirements for serving ads in the EEA, the UK and Switzerland (Opens in a new tab) says a certified CMP integrated with the TCF is required when serving personalized ads. It dates the requirement to 16 January 2024 for the EEA and the UK and 31 July 2024 for Switzerland, and says it covers AdSense, Ad Manager and AdMob publishers. Only traffic from a certified CMP is eligible for personalized ads. Traffic from a non-certified CMP may be eligible for non-personalized or limited ads where supported. For Search Ads publisher products, the page describes a separate rule and says that without a certified CMP, and without a stated parameter, those products will not serve ads.
The page also sets two limits worth remembering. Google certifies CMPs against criteria focused on TCF compliance and does not check full TCF compliance or compliance with privacy law, so "we use a certified CMP" is not the same as "we comply with the law". And Google lists its own CMP ("Google LLC CMP", TCF CMP ID 300) while offering a certified European regulations message under "Privacy & messaging" for AdSense, Ad Manager and AdMob publishers.
Google's setup page for your CMP (Opens in a new tab) describes two steps: choose ad technology providers (a commonly used set or a custom set) and set up consent gathering, using the Google CMP, a third-party CMP or your own consent dialog. That does not make a homemade dialog sufficient in every case, because the requirements page separately says personalized ads need traffic from a certified CMP. The setup page also says the providers you pick must be clearly identified to users, and that its settings apply to AdSense for content, not AdSense for search.
EEA, UK and other regions: what changes
Two rule sets are easy to blur: the ad network's commercial requirement and the data protection rules and guidance.
The ad network rule depends on region
Google's page names the EEA, the UK and Switzerland. It states no CMP requirement for Turkey or for other regions, and the document is silent on them. That does not mean nothing applies elsewhere, because other Google policies and local law may. Do not copy region lists from articles, including this one; check Google's current page.
Turkey: the KVKK cookie guide
Turkey's Personal Data Protection Authority (KVKK) published a Guide on Cookie Practices (Opens in a new tab) (KVKK Publication No. 69, July 2025) for website operators who process personal data through cookies. It describes itself as practical, good-practice guidance and says it gives no direction on similar technologies such as pixels, fingerprinting, local storage and beacons. For an ad publisher, the points that matter are these:
- Cookies for online behavioural advertising require explicit consent. The guide includes cookies used for frequency capping, financial logging, ad affiliate arrangements, click fraud detection, research and market analysis among the advertising cookies covered by that need.
- Explicit consent is given by an active affirmative act. Entering a site does not mean consent to the cookies it runs.
- Consent must relate to a specific subject, rest on proper information and be freely given, and it must be withdrawable. A broad open-ended statement such as "I accept the processing of my personal data" is not explicit consent on its own.
- As a good-practice example the guide mentions a cookie management panel shown on entry with "accept", "reject" and "preferences" buttons presented equally in colour, size and font size, and says cookies that need explicit consent should appear passive (unticked) at first.
- On cookie walls, which block content until every cookie is accepted, the guide says they can impair free will and that consent given under them may not be valid, while noting fair alternatives are assessed case by case.
- Where third-party cookies are placed, both the site owner and the third party are responsible for informing users and obtaining consent.
- The cookie that remembers consent choices is treated as not needing separate explicit consent, with a reasonable lifetime recommended.
- Where cookies send data abroad, the transfer must follow Article 9 of Law No. 6698 and the related regulation, as the guide states.
These statements are recommendations. The sections of the guide quoted here do not set out penalties, and none are described here. A lawyer should decide what applies to your site.
Summary by region
| Visitor region | Ad platform side (Google page) | Data protection side |
|---|---|---|
| EEA, UK, Switzerland | Certified TCF-integrated CMP for personalized ads | Regional law applies separately; Google certification is not legal compliance |
| Turkey | No CMP requirement stated on that page | KVKK guide: explicit consent for advertising cookies, equal buttons as good practice |
| Other regions | Not addressed, check Google's current pages | Depends on local law |
CMP selection checklist
Judge a CMP on four axes: ad platform compatibility (certification), page performance, total cost and the visitor experience of the preference panel.
Certification and integration
First, confirm the candidate appears on Google's current certified CMP list. Second, confirm which TCF version it supports. Third, check how it manages the ad technology provider list. If your stack uses several demand sources, make sure the CMP passes the choice to all of them, not just one. When you add a new ad partner, update the list so its requests are not blocked or sent without consent.
Performance
A CMP adds script and visible interface. Measure whether the script delays ad requests, whether the banner shifts layout when it appears and how much of a phone screen it covers. These vary by vendor and configuration, so trust measurements on your own pages over marketing claims. Ads and Core Web Vitals: a publisher's balance offers a wider frame for ad weight and speed.
Cost
Pricing models differ: some limit visitors, some limit features. Google's own CMP is described on its page as an option for AdSense, Ad Manager and AdMob publishers. Count setup effort, customisation limits, support and the pain of moving stored choices if you switch vendor, not just the monthly fee. Vendor names are deliberately not ranked here because pricing and features change quickly.
Preference panel quality
Check that you can present accept, reject and preferences at equal weight, and leave a small persistent icon or link to reopen choices. The KVKK guide cites turning the consent platform into an icon or a band small enough not to block content, tucked in a corner, as a good example of easy withdrawal.
A selection rule
Work in order. If you serve personalized ads to EEA, UK or Swiss visitors, only certified CMPs stay on the list. If Turkish traffic matters, drop options that cannot show equal buttons or let visitors withdraw easily. Among the rest, pick the one that measures best on your own pages, and compare price last. If two tie, prefer the one that adds the fewest extra scripts to your existing stack.
| Criterion | Question | Red flag |
|---|---|---|
| Certification | On Google's certified list, current TCF version? | Not listed, outdated version |
| Ad stack | Does it pass the choice to every partner? | Covers only one network |
| Performance | Does it delay ad requests or shift layout? | Clear slowdown in your own measurement |
| Interface | Equal buttons and easy withdrawal? | Weak or hidden reject option |
| Cost | Visitor and customisation limits? | Surprise price jump as traffic grows |
Testing the banner after install
You only know a setup works after trying every consent state. The checks below are practical suggestions, not a procedure from Google; the setup page does not describe publishing messages or testing.
Browser checks
- Open the site in a clean profile that has never visited it. Does the banner appear, and does it avoid covering content for no reason?
- Before choosing anything, open the network panel of developer tools. Are requests that need consent already firing? The KVKK guide expects consent for such cookies before they are placed, so this check matters.
- Choose reject and reload. Do ad slots stay empty, serve non-personalized ads or break the layout? Google's page says non-certified traffic may get non-personalized or limited ads where supported, and the effect on layout of an empty slot is worth recording separately.
- Choose accept and confirm ads load.
- Choose a partial selection in preferences and verify in network requests that it was applied.
- Change your choice afterwards. Is there a persistent way to reopen preferences, and does the change stick?
- Repeat on a phone and a narrow window. Keep content and close controls reachable if the banner is large.
Region checks
If behaviour differs by region, test each one. Tools that simulate location can help trigger the right message but may not reproduce a real visitor's experience exactly. Confirm region behaviour from your CMP vendor's documentation.
The provider list
Per Google's setup page you can choose a common or a custom provider set and must clearly identify the providers to users. With a custom set, check on every new integration that the new ad partner was added. A missing provider can lead to blocked requests or to data flowing without consent.
Separate the variables
Keep CMP testing apart from file and blocker effects. For authorised seller files see what is ads.txt; for revenue lost to blockers see ad blockers and publisher revenue. If ads do not show in a test, the cause could be the CMP, ads.txt, a blocker or simply no demand. Change one thing at a time.
Reading consent rate against revenue
Consent rate is the share of visitors who accept among those who answer the banner. Google's page says only traffic from a certified CMP is eligible for personalized ads, and non-consenting or unanswered traffic may get non-personalized or limited ads. How large the revenue gap is the documents do not say, so you have to measure it on your own site.
What to read together
- Consent rate by region and device.
- Revenue per page view or per thousand impressions for the same regions.
- The dates of any banner or vendor change.
- Traffic source mix: direct, search, social.
Avoiding false conclusions
If consent rate and revenue rose in the same week, that alone does not prove cause. Seasonality, ad fill and traffic mix may have moved too. Make changes one at a time and log the date. Steering the banner to push the accept button also conflicts with the KVKK guide's equal-button example and its expectation that consent is freely given. Improving clarity of wording is reasonable; engineering the outcome is not.
Example scenario: a recipe and travel blog
The blog gets most traffic from Turkey and a smaller part from Europe, and runs AdSense. The owner installs a Google-certified CMP, designs the banner with equal buttons and separates the message by region. For two weeks the owner tracks only consent rate and revenue per visitor by region. In week three the banner wording is shortened and the date logged. At month end the owner reads the change against the traffic mix shift. The scenario shows a method, not a result.
Build or buy: your own dialog versus a ready CMP
Google's setup page lists a Google CMP, a third-party CMP or your own dialog. A homemade dialog offers full control and no subscription, but the work moves to you: storing consent records, letting people reopen choices and passing signals correctly to providers. Google's page gives separate guidance for passing ad personalization signals and TCF consent signals. Personalized ads also need traffic from a certified CMP, which a homemade dialog is not.
For a small site with Turkish traffic only and no personalized ads, a simple dialog may be enough, but that depends on architecture, ad type and legal review, and this guide does not decide it for you. As a rule, sites that depend on ad revenue, run several demand sources and have European visitors save maintenance by using a ready certified CMP.
Wording, accessibility and mobile
The KVKK guide wants notices to be clear, plain and easy to find, and says a complex privacy notice packed with other topics cannot be treated as meeting the duty. It recommends that the notice state the cookie's name, purpose and duration and whether it is first or third party.
Banner wording checklist
- Does the banner say what consent is for in a sentence or two?
- Is advertising a distinct choice, not buried in one box?
- Are cookie name, purpose, duration and party listed with an easy link to details?
- Do accept, reject and preferences look equal?
- Is there a link to the privacy and cookie notice?
Keyboard, screen readers and phones
If the banner behaves like a dialog, it should work by keyboard, keep focus inside and offer a way to close it. Button labels should make sense to a screen reader, and on phones the banner should not cover most of the page. Vendors' default designs may not meet these, so try the demo with a keyboard before committing.
Quick decision matrix
| Situation | Suggested approach | Watch out |
|---|---|---|
| AdSense with EEA or UK traffic | Install a certified CMP, confirm TCF version | Certification is not legal compliance |
| Turkey-only traffic with advertising cookies | A tool that collects explicit consent with equal buttons | The KVKK guide is advisory; get legal review |
| Several ad networks | Choose a CMP that passes choices to all | Update the provider list with each new partner |
| Revenue dropped after the banner | Separate consent rate, region and traffic mix first | Do not change several things at once |
Troubleshooting: ads are not loading
If ads fail after installing a CMP, work through causes in order. First check that the banner records the choice: does a preference cookie appear? Then check whether ad tags load before or after the CMP; tags waiting on a consent state that never resolves will never request ads. Next look at the ad technology provider set; a needed provider may be missing. Finally check your Google account for any region notice. Change one thing at a time and date it.
If the issue appears in one region only, confirm that the region-specific message is actually published. And remember that Google offers a separate User Messaging Platform SDK for apps, so a web configuration does not cover an app.
Freshness note
Google's region list, dates and certified CMP list, IAB Europe's TCF version and the KVKK guide's edition can all change. Check the current pages before you act. The edition cited here is July 2025.
Frequently Asked Questions
Does every ad-supported site need a CMP?
There is no single universal rule. For AdSense, Ad Manager and AdMob, Google requires a TCF-integrated certified CMP to serve personalized ads to users in the EEA, the UK and Switzerland. The Google page does not state a CMP requirement for Turkey, where the KVKK cookie guide expects explicit consent for advertising cookies. Ask a qualified adviser about your own site, because this answer is not legal advice.
Does a Google-certified CMP make me compliant with privacy law?
No. Google certifies CMPs against criteria focused on TCF compliance and does not check full TCF compliance or compliance with privacy law. Certification helps you meet the ad platform's requirement; it is not proof of legal compliance.
Do ads disappear if a visitor refuses cookies?
Google's page says traffic from a non-certified CMP may be eligible for non-personalized or limited ads where supported, and only certified CMP traffic is eligible for personalized ads. Whether ads disappear entirely depends on the ad product and settings; for Search Ads products the page describes a different outcome. The size of the revenue effect is not stated in the documents, so measure it on your own site.
What does the KVKK guide recommend for the cookie banner?
As a good-practice example, it mentions a panel on entry with accept, reject and preferences buttons shown equally in colour, size and font size. It also expects cookies needing explicit consent to appear unticked at first, consent to be given by an active act and withdrawal to be easy.
What is the most important factor when choosing a CMP?
Start with certification and TCF version for the regions you serve, then check that it passes choices to every partner in your ad stack, then measure page performance and interface features such as equal buttons. Compare price last. Your own measurements matter more than vendor claims.
Can I steer the banner to raise consent rate?
Avoid steering that damages the quality of consent. The KVKK guide treats equal presentation as good practice and expects consent to be freely given. Clearer wording is reasonable, and its effect should be tracked as a single change.
What should I test after installing a CMP?
Use a clean browser to check that the banner appears, that no consent-dependent requests fire before a choice, how ads behave under reject, accept and partial choices, that preferences can be changed later and that the mobile layout works. These are practical suggestions, not a Google procedure.
Related guides: Google Ad Manager for Small Publishers: Setup Guide, Paywall or Ads? Choose a Model and Mark Gated Content, Choosing Affiliate Programs for a Blog: Decision Guide.
Conclusion and Next Step
The CMP decision on an ad-supported site sits where two rule sets meet: the ad platform's region-dependent requirement and data protection expectations. If you have European traffic, check Google's certified CMP requirement. If you have Turkish traffic, keep the KVKK guide's explicit consent and equal-button example in view. Choose by certification, ad stack coverage, performance and interface in that order, test every consent state after install, and read consent rate against revenue one variable at a time. Nothing here is legal advice, so ask a qualified adviser what your site must do.
If you are also looking at where your own ads or brand could appear on other sites, see the ad spaces page for the options.
Post a comment
Please log in to leave a comment. Login