Switching
Moving from another consent tool
Usually an afternoon for the first site and much less for the rest. Here is the order that keeps you covered the whole way through.
Five steps, per site
Note the order: the old banner comes off last, so your site is never uncovered.
1. Add the site and build your banner
Create a free account, add your first site, and build the banner. Pick a design, set your colours, and check the preview. Nothing is live on your site yet, so take as long as you like getting it right.
2. Run a check on the site as it is today
Before you change anything, let ConsentCook crawl your site the way a visitor arrives. You get a list of what actually loads and what fires before anyone agrees — which is worth having on its own, and often surprises people who thought their current banner was handling it.
3. Publish, then add our line
Publish your banner, then put the ConsentCook line on the site. On WordPress that is installing our plugin and connecting your account. Elsewhere it is one script tag, or one tag in Google Tag Manager.
4. Check both, then remove the old one
With both installed you may briefly see two banners — that is expected, and it is the safe way round. Confirm ours appears, choose an option, and check the receipt lands in Reports. Then remove the old tool's script.
5. Run the check again
One more crawl, to confirm nothing non-essential fires before consent now. That is the point at which you are done, and you have the evidence to say so.
What carries over, and what doesn’t
Your old consent records do not move
We will not import consent records from another tool. We could copy the rows, but we could not honestly sign them — a ConsentCook receipt says we recorded that choice, at that moment, against the exact banner the visitor saw. Stamping our signature on somebody else’s data would make the signature worthless. Keep an export from your old tool for your own records; ours starts clean, from your first visitor.
Visitors will be asked once more
Because the record starts fresh, returning visitors see the banner one more time. That is the honest outcome of a change of controller-side tooling, and every tool has it — anyone claiming otherwise is carrying over a consent they cannot evidence.
Your settings do not import, and that is quick anyway
There is no import from another vendor’s configuration format. Building a banner takes a few minutes, and the site check does the hard part — working out what is actually running — rather than you copying a list across.
Your tags keep working
Common trackers are recognised and held before consent without you tagging anything, and Google Consent Mode v2 is set from the start. If you already mark scripts for your old tool, you can leave those markers in place — they do no harm — and mark them for us as you go.
Start with one site
Do the first one on the Free plan while your current tool is still running. Move the rest once you are happy. If you get stuck, the live chat is on every page and a person answers.