How Cookiebot Works
Cookiebot (a product of Usercentrics) is one of the most widely deployed hosted cookie consent tools. It solves the same problem Consenti does — showing a banner and gating scripts on consent — but with a different architecture: cloud-hosted scanning and a CDN-served banner script, instead of code you run yourself.
The scanning step
Cookiebot's defining feature is its automated crawler, which periodically visits your site to detect cookies and tracking scripts and auto-generates a cookie declaration — a categorised list of what your site sets, without a developer manually cataloguing every script. This declaration typically renders on a hosted subdomain and can be embedded on your own privacy policy page.
The banner script
The consent banner itself loads as a script tag pointed at Cookiebot's CDN (consent.cookiebot.com), configured with a domain group ID. It shows the notice, records the visitor's category choices, and exposes a JS API other scripts can query before deciding whether to run.
How script blocking works
Rather than requiring you to rewrite every third-party script, Cookiebot's documented approach uses a data-cookieconsent attribute plus a script type override (e.g. text/plain) so the browser doesn't execute the tag until Cookiebot rewrites its type after consent is granted for the matching category. It's a markup-level convention rather than a bundler or build step.
IAB TCF and Consent Mode
Cookiebot supports the IAB Transparency & Consent Framework (TCF) for programmatic ad vendors and documents Google Consent Mode integration for Ads/Analytics signal passthrough — both standard expectations for a CMP aimed at ad-funded publisher sites.
Where the architecture differs from a self-hosted widget
| Cookiebot (hosted) | Self-hosted widget (e.g. Consenti) | |
|---|---|---|
| Script origin | Loaded from Cookiebot's CDN at runtime | Bundled with your own build — no third-party script origin |
| Cookie discovery | Automated crawler + declaration page | Declared in your own config; no crawler included |
| Consent record storage | Stored on Cookiebot's infrastructure | Stored on your own database |
| Pricing model | Free tier with domain/pageview limits; paid tiers beyond that, per Cookiebot's published pricing | Open-source license, no per-pageview meter |
| Backend / audit log | Managed by Cookiebot | Depends on the widget — some are frontend-only, some ship a full backend |
If what you actually want is a self-hosted, open-source CMP with a similar banner-plus-blocking model but code you own outright, see the open-source alternatives to Cookiebot comparison — Consenti is one such option.
Based on Cookiebot's publicly documented behaviour as of July 2026. Cookiebot is a trademark of its respective owner; Consenti is not affiliated with, endorsed by, or sponsored by Cookiebot or Usercentrics. See the Terms of Use for our comparisons policy.