Switch to Clickio
in an afternoon
CMP migrations sound scary and mostly aren't: one tag out, one tag in, and a scanner that rebuilds your cookie inventory for you. Here's the whole process, plus what to double-check before you flip.
Trusted by 2,000+clients worldwide
The migration, step by step
Set up Clickio in parallel
Create your account, add your site, and configure design, languages and regulations. Nothing touches production yet.
Rebuild your inventory
Run the Cookie Scanner: it detects the cookies and vendors that actually fire on the pages it crawls, so your Clickio dialog matches reality rather than an old spreadsheet.
Swap the tags
Add the Clickio snippet, remove the old CMP's tag (and its cookie-table embed, replaced by Clickio's), and publish.
Verify after the swap
One dialog, not two
Confirm the old CMP's banner is fully removed: double dialogs are the classic migration bug.
Signals flowing
Check TC strings via __tcfapi and let Clickio's automated checks confirm correct Consent Mode defaults and updates.
Trackers gated
Re-scan and confirm non-consented categories stay silent until consent, empirically rather than by assumption.
Cookie Scanner →What you should expect to change
Check consent compatibility
Compatibility depends on your existing CMP and implementation. Check what your setup supports before switching, and plan for visitors to make a fresh choice where needed.
Reporting →Your cookie policy updates itself
Replace the old static cookie table with Clickio's embed and stop maintaining it by hand.
Cookie List Embed →Pricing you can predict
Clickio's prices are published and per site (a free plan for one small site, then from £2 a month on annual billing, £3 monthly, up to Pro+ at £30/£35, with pageview allowances from 5,000 to 500,000; Enterprise on quote), so you can compare your renewal quote before you move.
Pricing →Migrating a larger estate? Enterprise plans include a dedicated account manager, same-day e-mail support and implementation help for staged rollouts.
Talk to usFrequently asked questions
Do existing consents carry over from my old CMP?
Do not assume automatic transfer. Compatibility depends on your current CMP and setup. Check which settings and consent choices are supported, and plan for fresh consent where needed.
How long does the switch take?
For a typical site: an afternoon including verification. The parallel setup means production changes only at the tag swap.
Can I run both CMPs briefly?
Avoid two active dialogs. Set Clickio up fully in parallel (unpublished on production), then swap in one deploy.
What usually goes wrong?
Leftovers: the old CMP's tag still loading, its cookie-table embed still on the policy page, or hard-coded tags that bypassed the old CMP and bypass the new one too. The re-scan catches the last case.
How do I check consent signals after switching?
The swap itself is instant. Signal continuity (TC strings and Consent Mode) is the thing to verify, and Clickio's automated checks flag misconfigured Consent Mode signals.