Migration guide
How to switch from iubenda to GetCookies
Switching the cookie banner is one script swap plus one edit for every script you tagged for iubenda's prior blocking. 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 iubenda stored.
Before you start
Keep your iubenda 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
_iub_cs_activate. iubenda's manual tagging usestype="text/plain", that class, adata-iub-purposesnumber and oftendata-suppressedsrcinstead ofsrc.Decide about your policies
If iubenda also generates your privacy policy or terms, decide separately whether to keep them. GetCookies has free privacy policy and cookie policy generators.
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 iubenda cookie solution scripts (the configuration snippet and iubenda_cs.js), or the iubenda tag in Google Tag Manager, and add the GetCookies loader as the first script in your page head. See direct script install.
4. Re-tag your scripts. Keep type="text/plain", remove the _iub_cs_activate class and data-iub-purposes, add data-cookieconsent with a GetCookies category (below), and rename data-suppressedsrc back to src. 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 the iubenda cookie solution.
Map iubenda purposes to GetCookies
iubenda lists its purpose IDs in its manual tagging guide.
2 Functionality and 3 Experience
Use
data-cookieconsent="preferences".4 Measurement
Use
data-cookieconsent="analytics".5 Marketing
Use
data-cookieconsent="marketing".Several purposes on one script
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 iubenda choice is not carried over.
Registered CMP status
iubenda is a registered IAB Europe CMP and on Google's certified CMP list; GetCookies is neither yet.
Pricing
GetCookies plans are priced by domains, without pageview limits. See pricing and GetCookies vs iubenda.
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