Post-Deployment Maintenance for Cookiebot

Now that Cookiebot has been set up on your site, it’s essential to understand what it does and how to maintain compliance as your website evolves.

How does Cookiebot work?

Cookiebot is a comprehensive, user-friendly solution that helps your website comply with global privacy regulations, including GDPR and CCPA. It automatically scans your site to detect and categorize cookies, then displays a customizable cookie consent banner that informs your visitors and allows them to control which categories they consent to.

When adding new content from third parties—such as YouTube videos, scripts in Google Tag Manager, or embedded iframes and javascript snippets—these third-party scripts may require extra steps for compliance.

Blue background with Usercentrics and Cookiebot logos. Illustration of a person interacting with a computer displaying a menu, on the right side.

Adding tags in Google Tag Manager

https://support.cookiebot.com/hc/en-us/articles/360003793854-Google-Tag-Manager-deployment#h_01JPPQA436K8H735KZMZ8SP2PG

Specific tags have built-in consent checks and no other configuration is needed for those. Other tags require a custom event and additional consent to be configured. See 2. Controlling cookies. In Google Tag Manager

  • Tags that would have been setup with the All Pages trigger will use the Custom Event: cookie_consent_update
  • Tags with any other trigger needs a Trigger Group created including Custom Event: cookie_consent_update

Adding content on the website that includes a script or iframe

https://support.cookiebot.com/hc/en-us/articles/4405978132242-Manual-cookie-blocking

  • Embedded JavaScript on the website requires updating the type attribute and adding a data-cookieconsent attribute based with the appropriate categories: “preferences”, “statistics”, and “marketing”.
  • External elements like iframes on the website require changing the src attribute to data-cookieblock-src and adding the data-cookieconsent attribute.
Illustration of a clipboard with a checklist showing three checked items in front of a blurred computer monitor displaying a spreadsheet or form.

Checking Compliance

Review the Monthly Cookiebot Report

Cookiebot runs a monthly scan and creates a report that will highlight potential compliance issues. The items can be addressed by reaching out to Orbit Support. Please note this is billable work. Alternatively you can address these items yourselves by following the steps listed below.

Login to your Cookiebot Account → Reports to see the results from the latest monthly scan.

Uncategorized or Unknown Cookies

Issue: Cookies or scripts that Cookiebot could not automatically categorize

  1. Cookies → Click on the cookie name (or script) labeled “Unknown”.
  2. Assign it to the correct category (e.g., Preferences, Statistics, Marketing) based on the cookie’s purpose. The best way to do this is to contact the platform providing the script.
  3. Save your changes.

Cookiebot documentation: https://support.cookiebot.com/hc/en-us/articles/360004177554-Check-your-unclassified-cookies

Select the Manager interface option on the right

Cookiebot interfaces with Manager selected

Scripts Detected That Are Not Blocked

Issue: A script is flagged as being loaded before consent is given. Blocked until accepted by user: No

  1. Ensure the script is not being triggered by a default “All Pages” trigger in GTM.
  2. Update the GTM tag to rely on Cookiebot’s consent triggers or variables.
  3. Verify the script is categorized under the correct Cookiebot category.

Need help navigating compliance?

We’ll walk you through the tools, setup, and best practices to meet your legal obligations with confidence.

Request Support from Orbit Media Studios