Set up Cookiebot to obtain user consent

To capture valuable insights while protecting user privacy, you need to collect consent from your website users. We recommend you use a Consent Management Platform (CMP) or work with your Content Management System (CMS) to collect consent and send it to Google. 

Step 1: Set up a consent banner

  1. Sign up for a Cookiebot account. You can use your existing Google account for easy signup.
  2. To configure your banner and cookie categories, go through the configuration flow. Add your domain and select the regulations for your banner configuration. Then, customize the design and content of your consent banner.
    A screenshot showing consent banner settings in Cookiebot.
  3. Cookiebot’s scanner will identify and automatically categorize all of the third-party cookies and trackers in use on your website. After the scan is complete, embed the consent banner into your website.
  4. If you use Google Tag Manager and want to deploy Cookiebot CMP through it, continue with the installation of the Tag Manager template.

If you want to continue with manual installation, review the instructions to copy the CMP script tag in the last step of the onboarding flow and embed it in the head of your website. Learn more about how to Get started using the Admin Interface.

Step 2: Set up consent mode

Cookiebot offers basic and advanced consent mode. The instructions below configure tags to be consent aware. If you’d like to use Advanced consent mode, follow the additional instructions about Google Tag Manager deployment.

  • Basic consent mode: Basic consent mode is only available for third-party tags.
  • Advanced consent mode: Google's own tags have "built-in consent" so to enable Advanced consent mode, assign the trigger you would normally use.
  1. From your Cookiebot account, add the consent mode script before your Google tag.

  2. Select the tag that you want to configure consent requirements for and switch to “Edit” mode.
  3. Expand the “Advanced Settings” section, then expand “Consent Settings”.
  4. Select Require additional consent for tag to fire, then choose the type of storage you want to require for your tag to fire.
  5. If you use any “page load” triggers, it’s recommended that you replace them with a custom “cookie_consent_update” event trigger.

Configure and test consent mode

If you’re using Cookiebot’s Google Tag Manager template, there’s no additional setup. However, If you implemented the Cookiebot CMP manually, make sure you’ve also implemented the default consent mode state as a script before your Google tag. You can also check if consent mode is properly implemented

Was this helpful?

How can we improve it?
true
Search
Clear search
Close search
Google apps
Main menu
3789707606030475127
true
Search Help Center
true
true
true
true
true
69256
true
false