Cookiebot vs Termly for Google Consent Mode v2 Compliance — what do I need to change?
Choose a consent manager using current pricing and feature gating now that Consent Mode v2 support and licensing thresholds determine whether the setup stays self-serve.
Blockers
- Lock-in via vendor/cookiebot
- Lock-in via vendor/termly
- Lock-in via vendor/termly
- requires_version: capability/google-consent-mode-v2-advanced → package/termly-embed-script
Who this is for
- cost-sensitive
- small-team
- compliance
Candidates
Cookiebot CMP
Cookiebot is a Google-certified CMP with Google Consent Mode support, and its official pricing page says Consent Mode v2 is enabled by default. As of 2026-03-27, its self-serve pricing is driven by domain count and subpage count, not traffic: free is limited to 1 domain with up to 50 subpages, Premium Lite is EUR 7/month for 1 domain up to 350 subpages, Premium Medium is EUR 30/month per domain up to 3,500 subpages, Premium Large is EUR 50/month per domain up to 7,000 subpages, and Premium Extra Large is EUR 90/month per domain above 7,000 subpages. The monthly subscription price is calculated from the highest page count recorded in scan history. Cookiebot explicitly says it does not charge by page views or usage.
When to choose
Use Cookiebot when page count is the main sizing variable and you want Consent Mode v2 available without upgrading for traffic volume. It is the cleaner self-serve choice for sites with predictable URL scope, especially when traffic can spike but the page inventory stays small enough for Lite or Medium.
Tradeoffs
Pros: Consent Mode v2 enabled by default, no traffic-based billing, free tier available for very small sites, premium plans include broad customization and multi-language support. Cons: pricing can jump when scan history detects more subpages, and the free tier is only viable for very small sites.
Cautions
As of 2026-03-27, Cookiebot's pricing is scan-based on subpages, and the highest recorded page count in scan history controls billing. If your site generates many unique URLs, landing pages, or parameterized pages, you need to verify how that affects the counted subpage total before assuming the integration stays self-serve.
Termly CMP
Termly supports both basic and advanced Google Consent Mode v2, but the pricing gate is tied to banner-view volume and plan level rather than page count. As of 2026-03-27, Free includes 10,000 banner views per month, Starter is USD 10/month annually or USD 14/month monthly with 50,000 banner views, and Pro+ is USD 15/month annually or USD 20/month monthly with unlimited banner views. Termly's pricing page shows Google Consent Mode v2 as Basic on Free and Starter, and Advanced on Pro+ and Agency. The support docs also state that using Consent Mode advanced options requires the latest Termly embed script.
When to choose
Use Termly when your site has many pages or subdomains but relatively modest consent-banner traffic, or when you already want Termly's bundled legal-policy tooling. It becomes the better self-serve option when Cookiebot page-scan pricing would escalate first, but you should budget for Pro+ if you need advanced Consent Mode behavior.
Tradeoffs
Pros: cheaper entry pricing, page count is not the metered unit on the public pricing page, and Pro+ bundles unlimited banner views plus broader compliance features. Cons: Consent Mode v2 capability is feature-gated by plan, and free or Starter may not be enough if you specifically need advanced Consent Mode configuration.
Cautions
As of 2026-03-27, advanced Consent Mode is not shown on Free or Starter; those tiers show Basic only. Termly's support docs also warn that advanced options require the latest embed script, so older installations can silently miss the configuration path you expect.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Cookiebot vs Termly for Google Consent Mode v2 Compliance — what do I need to change?"