Manually implementing Cookiebot CMP (Cookiebot Admin) – Cookiebot Support

To correctly implement Cookiebot CMP on your website, follow the 3 steps below.

Step 1 – Create a Cookiebot CMP account and add your domain

Sign up and log into your account, select “Domains & Aliases”, and add your website domain name(s). A scan of the website(s) will start automatically. * ^{please allow up to 24 hours for the scan to complete.}

Step 2 – Choose the cookie consent banner and Privacy Trigger you want to display on your website

Select “Configuration” from the main menu and configure your cookie consent banner.
On the “Privacy” tab you can configure the Privacy Trigger.

The default banner and Privacy Trigger are configured with the strictest settings available (suitable for cookie consent under GDPR and ePR).

On the “Content” tab you can edit the default banner and Privacy Trigger text to fit your website and legal requirements.

Step 3 – Insert the scripts on your website to make the cookie consent banner and the Privacy Trigger (and the cookie declaration) appear

Select “Script embeds” from the main menu.

1. Cookie consent banner and Privacy Trigger: Copy the top script and insert it as the very first script within the HEAD-tag of your website. Inserting it as the very first script ensures that no cookies or trackers escape our automatic cookie blocking. This script will guarantee that the banner is shown for consent collection and the Privacy Trigger is shown for consent changes and withdrawal. The Cookiebot CMP Privacy Trigger allows the user to withdraw (or change) their consent at any time – as required under e.g. GDPR.

Example:

<html>
  <head>
    <script 
      id="Cookiebot"
      src="https://consent.cookiebot.com/uc.js"
      data-cbid="00000000-0000-0000-0000-000000000000"
      type="text/javascript"
      data-blockingmode="auto"
    ></script>
  </head>
  <body>
    ...
  </body>
</html>

2. OPTIONAL – Cookie Declaration: Copy the second script and insert it in the HTML on the specific page and at the exact position where you would like the Cookie Declaration to appear. This could be as a separate page on your website or embedded into an existing privacy policy. The standard Cookie Declaration lists all cookies and trackers discovered on your website and allows the user also to withdraw (or change) a consent at any time – as required under e.g. GDPR.

Example:

<html>
  ...
  <body>
    <h1>Cookie Declaration</h1>
    <script
      id="CookieDeclaration"
      src="https://consent.cookiebot.com/00000000-0000-0000-0000-000000000000/cd.js"
      type="text/javascript"
      async
    ></script>
  </body>
</html>

To round off, when the website scan is complete, check your scan report. If there are any unclassified cookies, log in to your account and under “Cookies” make sure to classify them and add a short purpose description. This classification helps ensure that all cookies and trackers on your website (except for ‘strictly necessary’ cookies) will automatically be blocked until a user has given consent. Only those categories of cookies the user has consented to will be activated upon consent – all other cookies will be held back automatically.

Additional resources

You can disable the automatic cookie blocking feature and make a manual implementation of Cookiebot CMP instead by following our manual implementation guide.
You can also use our JavaScript SDK to customize Cookiebot CMP, for example to create alternative ways for the user to withdraw or change a consent.
Frequently asked questions about how Analytics data is impacted by the requirement to obtain user consent and our help center (in English).