Migration guide

How to switch from Usercentrics to GetCookies

Switching is one script swap plus one edit for every script you tagged with data-usercentrics. For a site with a handful of tagged scripts, budget about an hour to scan, configure and test. Visitors are asked for consent again, because GetCookies does not read the consent Usercentrics stored.

Before you start

  • Keep your Usercentrics consent records

    Export what you need as proof of past consent before you cancel. GetCookies does not import them.

  • Find your tagged scripts

    Search your templates for data-usercentrics. Usercentrics' manual blocking uses type="text/plain" plus the name of a data processing service, such as data-usercentrics="Facebook Pixel".

  • Apps and connected TV

    GetCookies covers websites only. If you use the Usercentrics App or CTV CMP, keep it for those.

  • Check your plan needs

    Consent Mode v2 default and update signals work on every GetCookies plan. IAB TCF consent strings, geo-targeting and visitor-region detection for Consent Mode need Pro; more than one banner language needs Business. See pricing.

Migration steps

1. Create a GetCookies account, add your domain and run a scan. Review the category it assigns to each cookie.

2. Configure the banner: layout, text, languages and, on Pro, geo-targeting and the advanced Consent Mode settings.

3. Remove the Usercentrics loader script, and its auto-blocker script if you use one, or the Usercentrics tag in Google Tag Manager. Add the GetCookies loader as the first script in your page head. See direct script install and GTM installation.

4. Re-tag your scripts. Keep type="text/plain", replace data-usercentrics="<service name>" with data-cookieconsent and the category that service belongs to (below). See data-attribute blocking.

5. Test in a private window: decline, and confirm nothing non-essential fires. The consent testing guide shows how.

6. When everything works, cancel Usercentrics.

From service names to categories

Usercentrics ties each script to a named service; GetCookies ties it to a category. Usercentrics documents its markup in its implementation guide.

  • Analytics services

    Google Analytics, Hotjar, Matomo and similar: data-cookieconsent="analytics".

  • Advertising services

    Facebook Pixel, Google Ads, LinkedIn Insight and similar: data-cookieconsent="marketing".

  • Functional services

    Chat widgets and other features that remember choices: data-cookieconsent="preferences".

  • Essential services

    Scripts the site needs to work should not be blocked. Remove type="text/plain" so they run normally.

What changes for you

  • Consent is collected again

    Returning visitors see the GetCookies banner once, because their Usercentrics choice is not carried over.

  • Registered CMP status

    Usercentrics is a registered IAB Europe CMP and on Google's certified CMP list; GetCookies is neither yet.

  • Scripts, not iframes

    GetCookies holds back script tags. Iframes that Usercentrics blocked with data-src need to be loaded after consent with your own code, for example through the JavaScript API.

  • Pricing

    GetCookies plans are priced by number of domains, with no session limits. Compare on the pricing page and GetCookies vs Usercentrics.

Try GetCookies on your own site

Start on the Free plan: one domain, a cookie scan and a consent banner, no credit card required. Upgrade only when you need more.

Start free