What is the single most important field in a consent record?

The notice version is the one most often missing and most often decisive. Without it, you can show a choice was recorded but not what wording, purposes, or vendors the choice referred to, which weakens the record badly in a dispute.

How long should consent records be retained?

Tie the period to the relationship length plus the applicable limitation period for claims in your markets, write it into a retention schedule, and apply deletion across every copy, including warehouse exports and backups, when the period ends.

Does a consent banner log prove tags behaved?

No. The log proves the choice as recorded. Proving behaviour needs a production check that tags fired or stayed silent according to that state. Keep evidence of both, and repeat the behaviour check after tag manager changes.

Should rejected consent be stored with the same care as accepted?

Yes. A recorded refusal, with timestamp and version, is what stops a team from re prompting aggressively or accidentally enabling a purpose later. It also demonstrates that refusal was honoured, which regulators treat as part of valid consent design.

The Best Cookiebot Alternatives for Growing Sites

November 2, 2026

Sites outgrow their first consent tool on price per pageview, banner control, or scan quality. What to compare when switching, and how to migrate consent records without a gap.

The switch usually starts with an invoice or an annoyance. Pageview based pricing that made sense at launch now charges like enterprise software, the banner cannot be styled past a template, or the scanner keeps missing the third party scripts everyone actually worries about. Shopping for an alternative is easy. Comparing them honestly is harder, because every consent platform demos the same banner and claims the same regulation list, while the differences that matter live in scanning depth, record keeping, and what happens to your existing consent history on migration day.

Consent records are the part nobody should improvise. A shopper who declined marketing cookies last spring should not be silently reset to a fresh choice because the store changed vendors, and in several jurisdictions the record of that choice is something you may need to produce. Treat the migration as a data move with a banner redesign attached, not the other way round.

Compare the scanner and the blocker, not the banner

Ask each candidate the same three questions and make them show, not tell. How does the scanner find scripts and iframes that load only after interaction, like a chat widget or a payment frame? Does the blocker hold tags until consent, including tags fired through a tag manager by another team? How are new, unclassified services handled on a live site: blocked, allowed, or flagged for review within a day? The answers separate a consent tool from a banner generator quickly.

Run the candidates against your own heaviest page, not their demo page. A product page with video, reviews, payment icons, and a personalisation widget is your real test surface. Note what each scanner found that the others missed, and what each one classified wrong. Misclassification matters because the banner's category promises are only as good as the list behind them, and shoppers and regulators both eventually read the list.

Price the whole thing, including your traffic shape

Pageview pricing punishes seasonal spikes and successful campaigns, which is a strange way to charge for a compliance tool. Model each candidate at your peak month, not your average, and at the traffic you are planning for next year. Flat or domain based pricing can look expensive in a quiet month and cheap in December. Also price the tiers honestly: the feature in the sales deck, like Google Consent Mode support, a consent API, or multi language banners, often sits one tier above the price that got your attention.

Count implementation cost too. A tool your team can deploy and restyle without a developer ticket every quarter is worth money that never appears in the licence comparison. Include the hour cost of the migration itself, the re-test of every category against your tag manager, and the support contract you will actually use when a new tracker appears at 9pm before a sale.

Migrate consent like it matters, because it does

Export the existing consent records before you switch anything off, and confirm the new platform can import or honour prior choices, or at minimum that your plan for re-asking is deliberate and documented. A banner that re-asks everyone once, clearly, because the tool changed, is a defensible choice. A banner that quietly forgets declines and defaults people back into marketing categories is not a migration. It is a breach with a redesign on top.

After launch, re-run the full acceptance test: banner behaviour per region, categories respected in the tag manager, records written with timestamps, preference link in the footer reopening the tool with saved choices showing. Switch day is when consent debt gets created, because everyone is watching the banner appear and nobody is watching whether a decline actually stops the tags. Watch the tags.

Frequently asked questions

Why do sites switch consent platforms?

The common triggers are pageview based pricing outgrowing the site, limited banner design or language control, a scanner that misses interaction loaded scripts, and weak consent record exports. The banner itself is rarely the real reason, even when it is the visible one.

Can consent records move to a new platform?

Often yes, through export and import, but the format and fields differ by vendor. Confirm before the switch what history can be carried, and document any group of users who will be asked again. Never let a migration silently reset a decline into a fresh default.

What is the most important feature to compare?

Blocking behaviour in practice: whether tags and third party scripts are actually held until consent, including those loaded through a tag manager or after interaction. Scanning depth comes second, banner design third. A beautiful banner over tags that fire anyway is decoration, not consent.

How should pricing be compared?

At peak traffic and at next year's expected traffic, including the tier that holds the features you need, like consent mode support or an API. Pageview pricing looks cheap in an average month and expensive exactly when the business is doing well.