Getting Started With Cookiebot: Account and Domain Setup

Sign up with your email and a password, then verify the account using the registration key sent to your inbox. Existing users log in with the same credentials. The verification step is required before you can add a domain, so use an address you can access immediately rather than a shared alias.

Adding your website address under domains. That triggers the scanner, which crawls the site and lists every cookie it finds in the admin interface. Everything else in the setup depends on that inventory, so it is worth letting the first scan complete before configuring the banner in detail.

In the head area of your website's code, near the top. Placement matters more than it appears, because scripts loading before the consent script cannot be blocked by it. Anything positioned lower in the page leaves a window where trackers run before consent has been captured.

Yes. Google Tag Manager and the free WordPress plugin both handle installation without direct code changes. The tag manager route is the usual choice where a container already exists, since it keeps the consent tag alongside the tags it governs and makes the firing order easier to control.

Automatic blocking recognizes known trackers and holds them until consent is given, without you tagging anything manually. You can switch to manual mode and mark scripts yourself where you need finer control. Automatic suits most sites, since it keeps working as new trackers appear rather than requiring maintenance.

Consent rates appear in your account once the banner is live. Beyond the reporting, verify the mechanism directly: open the site in a private window and confirm trackers are not firing before you interact with the banner. Recorded consent rates confirm collection, not that blocking is working.

Yes. The design, the widget position and the content shown are all configurable before you generate the script. Worth setting deliberately, since banner presentation affects opt-in rates and a banner that looks unrelated to the site tends to perform worse than one matching its design.

The help center covers the common implementation paths in step-by-step guides, organized by category. If nothing there matches, a support request goes to the technical team. Most failures at this stage trace back to script placement or a mismatched domain, both of which the guides address directly.