Migrating from Cookiebot to GetCookies: The Step-by-Step Guide
Date: June 25, 2026 Author: GetCookies Team Category: Migration Reading Time: 8 min
Tired of Cookiebot's rising prices or performance impact? Moving to GetCookies is simpler than you think.
We designed GetCookies to be a "drop-in" upgrade. This guide walks you through the migration process, ensuring zero downtime and no data loss.
Step 1: Remove the Cookiebot Script
Locate the script in your <head>. It looks like this:
<!-- DELETE THIS -->
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js" ...></script>
Step 2: Add the GetCookies Script
Replace it with our lightweight loader:
<!-- ADD THIS -->
<script src="https://js.getcookies.io/v1/loader.js" data-domain-id="YOUR_ID" async></script>
Step 3: Mapping Categories
Cookiebot and GetCookies use similar category names. You need to update any manual tagging you did on your scripts.
| Cookiebot Attribute | GetCookies Attribute |
|---|---|
data-cookieconsent="preferences" |
data-category="functional" |
data-cookieconsent="statistics" |
data-category="analytics" |
data-cookieconsent="marketing" |
data-category="marketing" |
Action: Search your codebase for data-cookieconsent and simple Find/Replace with data-category.
Step 4: Updating Event Listeners
If you have custom code listening for Cookiebot events, swap them.
- Cookiebot:
window.addEventListener('CookiebotOnAccept', function (e) { ... }) - GetCookies:
window.addEventListener('getcookies:consent_updated', function (e) { ... })
Step 5: Google Consent Mode
If you used Cookiebot's "Auto-Blocking" or GTM Template, GetCookies works identically.
- GTM: Swap the "Cookiebot CMP" tag for the "GetCookies CMP" tag in Google Tag Manager.
- Consent Mode: GetCookies supports Consent Mode v2 out of the box. No extra config needed.
Why You Upgraded
- Faster: a ~1.6 KB loader plus a ~20 KB banner loaded asynchronously.
- Cheaper: Flat pricing vs per-page pricing.
- Better UI: Modern, accessible, and customizable.
Welcome to the faster side of privacy!