Migration guide

How to switch from CookieYes to GetCookies

Switching is one script swap plus one edit for every script you tagged with data-cookieyes. 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 CookieYes stored.

Before you start

  • Keep your CookieYes 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-cookieyes. CookieYes marks scripts with values such as cookieyes-analytics, and blocks other scripts by URL patterns set in its Cookie Manager.

  • Note your URL patterns

    Scripts that CookieYes blocked by URL pattern need markup in GetCookies, or a matching blocking rule for your domain.

  • 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 CookieYes script (script.js from cdn-cookieyes.com) or the CookieYes WordPress plugin, and add the GetCookies loader as the first script in your page head, or the GetCookies WordPress plugin. See direct script install and the WordPress setup guide.

4. Re-tag your scripts. Replace data-cookieyes="…" with data-cookieconsent and a GetCookies category, and add type="text/plain": unlike CookieYes, GetCookies only holds back scripts that carry that type. 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 CookieYes.

Map CookieYes values to GetCookies

CookieYes documents its attribute values in its prior consent guide.

  • cookieyes-analytics

    Use data-cookieconsent="analytics".

  • cookieyes-performance

    Use data-cookieconsent="analytics".

  • cookieyes-functional

    Use data-cookieconsent="preferences".

  • Advertisement scripts

    Use data-cookieconsent="marketing".

What changes for you

  • Consent is collected again

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

  • Registered CMP status

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

  • No pageview limits

    GetCookies plans are priced by domains, without pageview caps or overage. See pricing and GetCookies vs CookieYes.

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