CookieYes vs Cookiebot: two widely used CMPs compared for Tag Manager and consent mode
Both are widely installed on US websites, and both cover the basics a small or mid-sized site needs. Here are their documented settings side by side, how each connects to Tag Manager, and how to tell which fits your site.
The short answer
Both send all four consent mode signals, both have a Tag Manager template, and both can block scripts automatically. They differ in plan limits for regions, languages, scanning and number of sites, which the table below lays out. In my setups CookieYes gave me more to configure than Cookiebot. Whichever you choose, test the Tag Manager connection after setup.
On this page
Settings side by side
Every cell comes from each vendor's own documentation or pricing page, checked in November 2026. Where a vendor doesn't document a setting, the cell says so. Plans change, so check the pricing pages before you buy.
| Setting | CookieYes | Cookiebot |
|---|---|---|
| Rules by region | Separate banners by region on the Pro and Ultimate plans | Geotargeting on paid plans |
| Languages | 41 languages, on paid plans | More than 47 languages on paid plans, one on the free plan |
| Cookie scanning | Unlimited scans on paid plans, scheduled monthly on Pro and weekly on Ultimate | Monthly automated scans on paid plans, with daily scans as an add-on. The free plan gets an initial scan. |
| Automatic blocking | Blocks many common scripts automatically, and you can add others by URL | Blocks cookies automatically when its blocking mode is set to auto. Otherwise you mark up each script. |
| Consent records | A consent log with the domain, date, consent ID, location, pseudonymous IP address and each category's status | Consent records kept for up to 12 months, with export on paid plans |
| Several websites | Several domains in one account, each priced separately | One domain on the free plan, and several domains and domain groups on paid plans |
| Test before live | Not documented | Not documented |
Cookiebot is a Usercentrics product. If you're also looking at Usercentrics itself, see OneTrust vs Usercentrics.
How each connects to Google Tag Manager
CookieYes
The CookieYes CMP template in the Community Template Gallery sets consent defaults by category and region and fires on Consent Initialization, which fires before every other trigger. For tags that aren't Google's, CookieYes recommends a custom event trigger on its cookie_consent_update event. The full setup is in OneTrust vs CookieYes.
Cookiebot
The Cookiebot CMP template, published by Usercentrics, loads the Cookiebot script, sets defaults by category and country, and fires on Consent Initialization. For other tags, Usercentrics publishes a Cookiebot Consent State variable that a trigger can check. The full setup is in OneTrust vs Cookiebot.
Consent mode v2 signals
Both platforms can send all four signals: ad_storage, analytics_storage, ad_user_data and ad_personalization. CookieYes maps all four to its categories, and Cookiebot's template sends the three advertising signals from its marketing category.
| Platform | On Google's certified CMP list (TCF) | Consent Mode partner tier |
|---|---|---|
| CookieYes | Yes, as "CookieYes CMP" | Gold |
| Cookiebot | Yes, as "Cookiebot CMP" | Gold |
Copied from the table of Google's lists, which says when each list was checked.
Configuration, from my setups
In my setups CookieYes gave me more to configure than Cookiebot.
Where each fits
BuiltWith counted CookieYes on about 150,000 US websites and Cookiebot on about 113,000. Among the top 100,000 sites, Cookiebot had 2,388 and CookieYes 1,233. CookieYes has more installs overall, and Cookiebot is on more of the large sites.
BuiltWith counts as of November 5, 2026, from its US websites and top 100,000 sites reports. The full table is in CMP market share in the US.
CookieYes fits a small team that wants room to configure as the site grows. Cookiebot fits a site that wants scanning and automatic blocking with fewer settings to manage, especially with visitors in Europe.
Both publish their plans. See the CookieYes pricing page and the Cookiebot pricing page.
Test it after setup
Whichever you choose, run the banner test in a browser before and after a choice, and again with Global Privacy Control on. The Measurement & Consent Audit runs that test for every key action, and I can set up or fix either platform.
Questions about CookieYes and Cookiebot
Which is better for a small business?
It depends on what you need to set. In my setups CookieYes gave me more to configure, and Cookiebot had fewer settings to manage. Compare the settings table with your regions, languages and number of sites, then test the setup. What the law requires of your site is a question for your counsel.
Do both work with Google Tag Manager?
Yes. Each has a template in Tag Manager's Community Template Gallery that sets consent defaults before other tags fire. Tags that aren't Google's still need a trigger that waits for the visitor's choice.
