Customer Impact

Data & Tracking

Cookiebot pricing, setup with Google Tag Manager and Consent Mode v2

Copy for AI

Cookiebot pricing starts free and rises per domain with your number of subpages.

The free plan covers one domain up to 50 subpages.

Above that you pay 7 to 90 euro per domain per month.

The verdict: most B2B sites with two languages need a paid plan. And the price matters less than the setup: install it through Google Tag Manager so Consent Mode v2 is right from the first page view.

Cookiebot is a consent management platform (CMP). It scans your cookies, shows a cookie banner, stores your visitor’s choice and passes that choice on to Google and other tags.

This guide covers one tool: what it costs, which plan fits and how to set it up correctly.

Still choosing a tool? Read our comparison of Cookiebot vs Usercentrics vs Complianz first. For the legal side, see cookie banner rules in Belgium.

What exactly does Cookiebot do?

It does four jobs you’d otherwise handle by hand:

  1. Scanning. It crawls your site and lists all cookies and trackers by category: necessary, preferences, statistics, marketing.
  2. Showing the banner. In your visitor’s language, with a refuse button as easy to use as the accept button.
  3. Storing consent. Every choice is logged, so you can show who consented to what, and when.
  4. Passing consent on. To Google through Consent Mode, and to other tags through Google Tag Manager.

Why the fourth job is the one that costs money

Since Consent Mode v2, Google expects four signals for traffic from the EEA:

  • ad_storage
  • analytics_storage
  • ad_user_data
  • ad_personalization

According to Google’s documentation, no value is set by default. You have to set those defaults yourself before your tags send data.

Cookiebot does that for you, provided it’s installed correctly.

Get it wrong and Google Ads loses conversion data.

What does Cookiebot cost? Cookiebot pricing per plan

Cookiebot charges per domain per month.

The price rises with the number of subpages on that domain.

These are the plans as Cookiebot publishes them on its pricing page, checked 4 November 2026, in euro and excluding VAT. They’re the vendor’s prices, not ours.

PlanSubpages per domainPrice per domain per month
Freeup to 50 (1 domain)0 euro
Premium Liteup to 507 euro
Premium Smallup to 35015 euro
Premium Mediumup to 3,50030 euro
Premium Largeup to 7,00050 euro
Premium XLargemore than 7,00090 euro

Here’s the same price ladder as a chart:

COOKIEBOT PRICING Euro per domain per month 0 Free 50 pages 7 Lite 50 pages 15 Small 350 pages 30 Medium 3,500 pages 50 Large 7,000 pages 90 XLarge 7,000+ pages Source: cookiebot.com pricing page, checked 4 November 2026, excl. VAT. Lime = typical bilingual B2B site.
Cookiebot's published prices per domain per month, checked 4 November 2026, excluding VAT. The highlighted plan is where many bilingual B2B sites end up.

The pricing page itself also shows the plan picker:

Three things to watch when you choose a plan

The subpage count trips people up most. Check these three points:

  • Subpages are every unique URL the scanner finds. That includes blog articles, category pages and translated versions.
  • The free plan is limited. You get the basic banner and Consent Mode, but no custom branding, one language and no geotargeting.
  • Multiple domains count separately. A .be, .nl and .fr cost three times, unless you move to a different model at Usercentrics.

For example: say your B2B site has 120 pages in Dutch and the same 120 in French. That’s 240 subpages, so you’re on Premium Small at 15 euro per month.

Add a knowledge base in three languages and you’ll pass 350 quickly.

Then it’s Premium Medium at 30 euro.

Watch out: the free plan’s single language is usually the deal-breaker for a Belgian site in Dutch and French.

Installing Cookiebot through Google Tag Manager: step by step

You can paste Cookiebot straight into the <head> of your site. But if you work with Google Tag Manager, install it there.

Then consent and tags live in one place, and GTM controls the order.

Step 1: Create an account and add your domain

Let the first scan run and check the categories.

Watch out: a marketing pixel classified as “necessary” will later load without consent.

Step 2: Copy your Domain Group ID

You’ll find it in your Cookiebot account; the GTM template needs it.

Step 3: Add the Cookiebot template in GTM

Go to Templates, search the Community Template Gallery for the official Cookiebot CMP template and add it.

Google recommends this route itself: CMPs provide templates in the Community Template Gallery to manage consent mode.

In GTM it looks like this:

Enter your Domain Group ID and choose “Consent Initialization - All Pages” as the trigger.

That trigger fires before all other triggers.

It’s the whole reason to use GTM here.

Do it for ad_storage, analytics_storage, ad_user_data and ad_personalization, at least for the EEA.

Then enable the template option that passes Google Consent Mode on.

Google tags read the consent state themselves.

Non-Google tags don’t, such as Meta, LinkedIn or Hotjar.

For those, set the required consent in GTM under the advanced settings, or use triggers on the Cookiebot events.

Cookiebot provides a script that shows the current cookie list.

Combine it with a proper privacy policy.

That covers the transparency side of a GDPR-compliant website.

With basic, Google tags only load after consent.

With advanced, they load immediately with a denied state and send cookieless pings. That lets Google model missing conversions.

Cookiebot supports both. Here’s how they compare:

Basic consent modeAdvanced consent mode
Google tags before consentBlockedLoad with denied state
Cookieless pingsNoYes
Conversion modellingLimitedYes
Fits bestStrict internal privacy policyAdvertisers who rely on paid traffic

Rule of thumb: for most B2B advertisers with paid traffic, advanced makes more sense.

It’s a trade-off between measurability and your privacy policy.

More in our guides to Consent Mode v2 and consent mode in Google Ads.

The mistakes we see most often with Cookiebot

Five errors keep coming back:

  • Loaded twice. Hard-coded in the theme, added in GTM, and a WordPress plugin on top. Result: double banners or a jumpy consent state.
  • On the wrong trigger. The tag sits on All Pages instead of Consent Initialization. Each session’s first hit goes out without a consent state.
  • Only the old signals. An outdated template sends two signals, not four. Google Ads treats the missing ones as a refusal.
  • Wrong categories. An unknown tracker lands in “unclassified” and nobody checks it. It then loads without control.
  • A banner that makes refusing hard. Regulators look for exactly this.

What Belgian and Dutch regulators say

The Belgian Data Protection Authority states that pre-ticked boxes don’t give valid consent.

Withdrawing consent must be as easy as giving it.

In the Netherlands, the Dutch Data Protection Authority sent warning letters to websites in April 2025.

On those sites, “no” didn’t work as intended, or boxes were pre-ticked.

A banner that appears proves nothing. Test like this:

TestHowWhat you want to see
OrderGTM Preview, first eventCookiebot and the consent default before any other tag
DefaultTag Assistant, Consent tabAll four signals on denied before you click
RefuseClick “Refuse”No marketing tags fired, Google tags with denied state
AcceptClick “Allow all”Update to granted, tags fire afterwards
Google AdsDiagnostics of your conversion actionsNo warning about missing consent signals

In Tag Assistant, open the Consent tab on the very first event:

Check the conversion side in Google Ads

Then check the conversion actions your bidding relies on. Look at which actions are marked Primary:

All conversions list in the Customer Impact Google Ads account: one GA4 contact form conversion action under the Contacts goal, with Primary in the Action optimization column, the conversion data consent mode protects The All conversions list in our own Google Ads account, October 2026. Only actions marked Primary steer the bidding, so those are the ones a consent error hurts most.

Repeat the full test after every theme update, new plugin or new tag.

Watch out: if Google Ads suddenly shows half as many conversions after a banner change, compare with your CRM first.

It’s often a measurement loss, not a lead loss.

Our conversion tracking audit checklist covers the rest of the chain.

When should you have this set up?

You can install Cookiebot yourself with these steps.

The mistakes usually sit in how everything fits together.

Consent, GTM, Google Ads, Meta and server-side tagging all have to connect:

  • Kaizo: we set up the full chain, from consent to GA4, Google Ads and Meta. Read the setup in the Kaizo case.
  • Tryve: consent was the foundation of conversion measurement too, as the Tryve case shows.

Want to know whether your setup is right? Start with a tracking audit.

If you want it built, our tracking specialist handles the installation, the Consent Mode v2 connection and the tests. Pricing on request.

For more on privacy-friendly measurement, read our guides on third-party cookies, Matomo and the clean event structure of a data layer.

Frequently asked questions

Is Cookiebot free?

There’s a free plan for one domain up to 50 subpages, with the basic banner and Google Consent Mode. For custom branding, multiple languages and larger sites you pay per domain per month. Check the current terms on Cookiebot’s pricing page.

Is Cookiebot the same as Usercentrics?

Cookiebot is a Usercentrics product. Usercentrics also offers its own, more extensive platform for larger organisations. Which of the two fits is covered in our CMP comparison.

Does Cookiebot work with Google Consent Mode v2?

Yes. Cookiebot passes the visitor’s choice on to Google through Consent Mode, including the ad_user_data and ad_personalization signals, provided you use a current template or script and the defaults are set correctly.

Do I have to install Cookiebot through Google Tag Manager?

You don’t have to, but it’s recommended if you use GTM. That way GTM controls the order through the Consent Initialization trigger and you manage consent and tags in one place.

Do I need Cookiebot if I only use Google Analytics?

You need some form of consent, because analytics cookies aren’t strictly necessary in Belgium. That can be Cookiebot or another CMP. If you want to depend less on cookies, also take a look at cookieless marketing.

So which Cookiebot plan should you pick?

Count your subpages across all languages, then pick the plan just above that number.

The setup decides whether your data holds up.

Want a second pair of eyes? Get in touch and we’ll check your consent chain in Tag Assistant with you.

Free website scan

Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.

Where should we send your report?

We only use your details for your scan. No spam, unsubscribe anytime.