Skip to main content

Migrate from Cookiebot

Time: ~1.5 hours

What you need​

  • Cookiebot account with admin access
  • ConsentForge account (create one at consentforge.com/register)
  • Access to your website's HTML or CMS

Step 1: Export your Cookiebot data​

  1. Log in to manager.cookiebot.com
  2. Go to your domain → Cookies tab
  3. Click Export → CSV
  4. Save the file — you'll use this in Step 3

Step 2: Create your ConsentForge property​

  1. Log in to app.consentforge.com
  2. Click Add Property
  3. Enter your domain URL
  4. ConsentForge will run an initial scan

Step 3: Import your vendor/cookie list​

  1. Go to Property → Vendors → Import
  2. Select Cookiebot CSV
  3. Upload your exported CSV
  4. Review the import preview — ConsentForge will match known vendors automatically
  5. For unmatched cookies, assign them to the appropriate category manually
  6. Click Import

Step 4: Configure your banner​

In Banner Builder:

  • Set your brand colors (match your previous banner)
  • Upload your logo
  • Review and edit the banner texts in DE and EN

Step 5: Run Shadow Mode​

Add the ConsentForge script alongside your existing Cookiebot script. Both run in parallel — Cookiebot still controls consent, but ConsentForge collects data.

<!-- Existing Cookiebot script — keep this for now -->
<script id="Cookiebot" src="https://consent.cookiebot.com/uc.js"
  data-cbid="YOUR_COOKIEBOT_ID" type="text/javascript"></script>

<!-- ConsentForge in shadow mode — add this -->
<script
  src="https://cdn.consentforge.com/consentforge.min.js"
  data-token="YOUR_CF_TOKEN"
  data-shadow-mode="true"
  defer
></script>

In shadow mode, ConsentForge shows no banner — it just collects scan data and prepares your setup.

Step 6: Test​

After 1–2 weeks of shadow mode:

  1. Check Property → Scanner → Findings — all vendors should be mapped
  2. Preview your ConsentForge banner in the Banner Builder
  3. Test the full flow in an incognito window using the staging embed URL

Step 7: Live switch​

When you're ready to go live:

  1. Remove the Cookiebot <script> tag
  2. Remove data-shadow-mode="true" from the ConsentForge tag
  3. If you used Cookiebot for Google Consent Mode, update your GTM setup to use the ConsentForge template
<!-- Final ConsentForge tag (no shadow mode) -->
<script
  src="https://cdn.consentforge.com/consentforge.min.js"
  data-token="YOUR_CF_TOKEN"
  defer
></script>

Step 8: Post-migration check​

  • Cookiebot script removed from all pages
  • ConsentForge banner appearing in incognito window
  • Scripts blocked before consent (DevTools → Network)
  • Google Consent Mode v2 firing (check dataLayer)
  • Consent receipts appearing in Dashboard → Evidence
  • Cancel your Cookiebot subscription
tip

If you used Cookiebot's WordPress plugin, install the ConsentForge WordPress plugin and remove the Cookiebot plugin. See WordPress setup.