Analytics and consent integration · Updated November 15, 2026

Cookiebot integration

Cookiebot by Usercentrics scans your site, shows a consent banner and can block cookies automatically until visitors choose. We set it up on WordPress, Webflow, Astro, Next.js or custom software for Quebec's Law 25 and Google Consent Mode v2, and pick automatic or manual blocking with page speed in mind.

Rated 5.0 out of 5,72 Google reviews

Cookiebot at a glance

Connects
Banner script, scanner, Cookie Declaration, Google Consent Mode v2, Microsoft UET and Clarity consent, IAB TCF on Premium.
WordPress
The official Cookiebot CMP plugin, connected with your Domain Group ID.
Webflow
Script first in site-wide head code, or through Google Tag Manager.
Astro or Next.js with Sanity
Script first in the shared head; in Next.js, beforeInteractive for Cookiebot only.
Custom software
Manual mode with data-cookieconsent attributes, for control and speed.
Complexity
Medium. Choosing a blocking mode and categorizing tags takes testing.
Typical setup
1 to 2 days for a small site, 3 to 6 days with French, geotargeting and Consent Mode checks.

How we connect Cookiebot

  • WordPress

    We install the Cookiebot CMP plugin from the WordPress directory and paste in the Domain Group ID from your Cookiebot account. Caching plugins must not defer, delay or combine consent.cookiebot.com, or blocking fails. Cookiebot names LiteSpeed Cache and Cloudflare Rocket Loader as ones to set up with care.

  • Webflow

    The script goes first in site-wide Head Code, before any tag that sets cookies, which needs a paid site plan. The Cookie Declaration goes in an Embed element on the privacy page only. When Cookiebot reports a choice, we pass it to Webflow's tracking consent API, which controls only Webflow Analyze and Optimize.

  • Astro or Next.js with Sanity

    Cookiebot documents a Next.js App Router setup where its script uses the beforeInteractive strategy. Other scripts using that strategy aren't blocked, so we keep them off it. In Astro the script sits at the top of the shared layout's head. Embeds editors add in Sanity get their consent category in the component code.

  • Custom software

    For apps and portals we usually choose manual mode. Each script that sets cookies gets a data-cookieconsent attribute naming its category, and Cookiebot loads asynchronously with no rendering delay. It takes more setup, and every new tag needs a category before it ships.

What organizations use Cookiebot for

  • Automatic blocking for sites with many tags

    In auto-blocking mode Cookiebot loads first and checks every other script before it runs. It suits a WordPress site where plugins add tags nobody tracks. Automatic blocking isn't on the Free plan, and Cookiebot's Google Tag Manager template doesn't support it.

  • Law 25 opt-in with a French banner

    Cookiebot says its banner supports the opt-in requirement Law 25 has set since September 22, 2023: non-essential technologies stay blocked until the visitor actively agrees, and each choice is logged with a timestamp. Premium plans add geotargeting and auto-translation for the French version.

  • Consent Mode v2 for Google Ads and GA4

    Google Consent Mode comes with every Cookiebot plan, Free included, and Google's CMP Partner Program lists Cookiebot at Gold tier as of November 15, 2026. Microsoft lists it as passing consent to Clarity. We run each banner choice through Tag Assistant to check that Google tags wait for it.

What to watch out for

  • Auto-blocking's cost to speed

    Cookiebot's help centre says auto-blocking loads the script synchronously, and checking other scripts first can add a small, sometimes noticeable rendering delay. It puts the script's typical load under 200 ms. Manual mode loads asynchronously instead. We measure LCP with each mode and add a preconnect to consent.cookiebot.com.

  • Priced by subpages, in euros

    As of November 15, 2026, Cookiebot lists Free for one domain up to 50 subpages, Premium Lite at €7 a month, Small at €15 per domain under 350 subpages, Medium at €30 under 3,500 and Large at €50 under 7,000, before tax. Daily scans cost €99 a month extra; otherwise scans run monthly. Watch the subpage count as your CMS grows, because it sets the tier.

  • The Free plan's limits

    Free has one language, consent that expires within a month, manual blocking only, and no geotargeting, auto-translation or email support. A bilingual Canadian site outgrows it quickly.

Questions about Cookiebot

Does Cookiebot have a Law 25 template?

Cookiebot's Law 25 page says its banner supports opt-in consent, but as of November 15, 2026 its pricing page lists GDPR, CCPA/CPRA, VCDPA, LGPD and POPIA frameworks, not Law 25 by name. We configure an opt-in banner for Quebec visitors and confirm the French text with you.

Is a cookie banner a CASL requirement?

No. The CRTC reads CASL as covering commercial electronic messages and software installs, and treats cookies as accepted while a visitor's conduct shows it. What your Cookiebot setup has to satisfy is PIPEDA's meaningful consent guidelines, Alberta and BC's private-sector privacy acts, and Law 25 in Quebec.

Can Cookiebot run through Google Tag Manager?

Yes, through Cookiebot's Tag Manager template, which sends Consent Mode signals before tags load. Automatic blocking isn't supported that way, so each tag in the container needs its own consent settings. On Webflow it keeps the head down to one Tag Manager snippet.

Related integrations

Choosing between automatic and manual blocking?

Send us your URL and a rough page count. We'll test both blocking modes against your page speed and size the Cookiebot plan to your subpages.

Book a call