Migration guide

How to switch from OneTrust to GetCookies

Switching is one script swap plus one edit for every script you tagged by hand for OneTrust. For a site with a handful of hand-tagged scripts, budget about an hour to scan, configure and test; each extra tagged script adds a small edit. Visitors are asked for consent again, because GetCookies does not read the consent OneTrust stored.

Before you start

  • Keep your OneTrust consent records

    Export what you need as proof of past consent before your OneTrust contract ends. GetCookies does not import them.

  • Find your hand-tagged scripts

    Search your templates for optanon-category. OneTrust's manual blocking marks scripts with type="text/plain" and a class such as optanon-category-C0002.

  • Check what OneTrust does for you beyond cookies

    If you also use OneTrust for data mapping, assessments or preference management, GetCookies replaces only the website cookie banner, scanning and consent logs.

  • 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 OneTrust script (otSDKStub.js from cdn.cookielaw.org) or the OneTrust tag in Google Tag Manager, and add the GetCookies loader as the first script in your page head. See direct script install and GTM installation.

4. Re-tag your hand-tagged scripts. Keep type="text/plain", remove the optanon-category-… class and add data-cookieconsent with a GetCookies category (mapping 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 OneTrust.

Map OneTrust categories to GetCookies

OneTrust's default category IDs are listed in its own manual blocking article. Your account can use custom IDs, so check your OneTrust category list first.

  • C0002 Performance

    Use data-cookieconsent="analytics".

  • C0003 Functional

    Use data-cookieconsent="preferences".

  • C0004 Targeting

    Use data-cookieconsent="marketing".

  • Several categories on one script

    OneTrust allows classes such as optanon-category-C0002-C0004. GetCookies takes one category per script, so choose the strictest one, usually marketing.

What changes for you

  • Consent is collected again

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

  • Registered CMP status

    OneTrust is a registered IAB Europe CMP and on Google's certified CMP list; GetCookies is neither yet. If your ad partners require a registered CMP, keep that in mind before switching.

  • Scripts, not iframes

    GetCookies holds back script tags. Embedded iframes that set cookies, such as video or map embeds, need to be loaded only after consent with your own code, for example through the JavaScript API.

  • Pricing

    GetCookies prices are public and flat per plan. Compare plans on the pricing page and facts on GetCookies vs OneTrust.

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