CMP Pricing: Cookie Consent Costs and Hidden Limits

A cookie banner can be free, while a production-ready consent management platform (CMP) may cost from a small monthly subscription to a negotiated enterprise contract. The difference is rarely the banner design alone. CMP pricing can depend on domains, subpages, pageviews, scans, languages, users, consent records, support and the work required to keep tags correctly controlled.

That is why the useful question is not simply “How much does a cookie banner cost?” It is: what will this consent setup cost to buy, implement and operate for the next 12 months?

This guide explains the main consent management platform pricing models, compares current public models from several vendors, and gives you a practical total cost of ownership (TCO) method. Prices and plan details were checked against official vendor pages on 9 August 2026. They can change by currency, billing term, tax, region or product update, so verify the linked pricing page before buying.

A CMP can help collect, communicate and document visitors’ choices. It does not guarantee GDPR, UK GDPR or ePrivacy compliance on its own. Your notices, legal basis, vendor choices, tag configuration and internal processes still matter.

CMP pricing at a glance

Most cookie consent pricing falls into one or more of five models:

Pricing model	Billing unit	What can increase the bill	Best fit when
Per domain	Each website or registered domain	New brands, country sites, client sites or staging environments	The number of sites is stable and clearly defined
Per pageview	Visits to pages carrying the CMP script	Seasonal peaks, paid campaigns, bots or growth	Traffic is measurable and overage rules are predictable
Per subpage or scanned page	URLs found or included in a scan	E-commerce catalogues, filters, archives and landing-page growth	The site structure is small and controlled
Per feature tier	Capabilities included in each plan	Exports, white-label, geotargeting, APIs, support or more frequent scans	Requirements map neatly to a published tier
Custom usage or enterprise quote	Visitors, properties, profiles, users or another negotiated meter	Expansion across channels, brands, apps and regions	Procurement needs a tailored contract and SLA

A vendor may combine these models. For example, a plan can be sold per domain, include a pageview allowance and restrict the number of pages per scan. Compare all three limits, not just the headline monthly price.

For a baseline, review CookiePilot’s current pricing and plan limits together with its CMP features. The pricing page currently presents per-domain plans, while traffic, domain allowances and feature access vary by tier.

What does a CMP actually cost?

The annual subscription is only the visible part of the cost. A useful first-year estimate is:

First-year CMP TCO = subscription + usage charges + implementation + remediation + training + maintenance + migration risk

For later years, migration and initial implementation usually fall away, but maintenance, traffic growth and contract changes remain.

Use the same worksheet for every vendor:

• Subscription: note monthly versus annual billing, currency, tax, minimum term, cancellation and renewal price.
• Properties: list production domains, subdomains, country sites, apps, staging and campaign environments; ask what counts as billable.
• Usage: model normal and peak pageviews, sessions or visitors using the vendor’s exact counting definition and overage rule.
• Scanning: estimate crawlable URLs, including filters, variants, translations and archives, then compare pages per scan and scan frequency.
• Features: mark must-haves such as geotargeting, consent records, exports, branding controls, additional users, IAB TCF, APIs, mobile support, onboarding and SLAs.

If Google advertising or analytics is in scope, include Google Consent Mode v2 deployment and testing in the budget. The practical Google Consent Mode v2 guide explains the implementation context. A named integration does not prove that every tag is configured correctly.

Current vendor pricing models: official-page snapshot

The table below is a pricing-model comparison, not a feature-equivalence verdict. Products package scanning, records, regional controls, integrations and support differently. Public prices are shown only where an official page displayed them during our 9 August 2026 check.

Vendor	Public pricing model observed	Important limits or cost drivers	Planning caveat
CookiePilot	Free Starter; Pro listed at €7/month; Business at €25/month. The page also advertises 20% savings with annual billing.	Starter lists one domain and 10,000 pageviews/month; Pro lists one domain with unlimited pageviews; Business lists five domains with unlimited pageviews. Feature access differs by tier.	Prices exclude VAT. Verify the live page, annual-billing basis and required features before purchase.
Cookiebot Core	Free plan and paid tiers based primarily on subpages per domain. The official page showed Premium Lite from €7/month for up to 50 subpages and one domain.	The page states that plans automatically upgrade depending on the website’s number of subpages. Premium Lite showed no traffic limit; domain and subpage counts remain central.	The pricing interface is dynamic and currency/billing selections affect the display. We do not reproduce every slider tier; use the official calculator for the current site size.
consentmanager	Starter displayed at €23/month including 100,000 views; Essential at €59/month including 1 million views; Enterprise was custom.	The official page listed additional-view charges and different scan frequencies by tier. Starter displayed €0.11 per additional 1,000 views and Essential €0.05 per additional 1,000.	The page’s FAQ summarized overages as €0.02-€0.10 per 1,000 depending on plan, while the Starter card displayed €0.11. Because the official page contains this discrepancy, confirm the applicable rate in checkout or writing.
CookieYes	Free and paid plans priced per month per domain. The USD monthly view showed Basic $10, Pro $25 and Ultimate $55.	Free showed 5,000 pageviews and 100 pages per scan; Basic 100,000 pageviews and 600 pages per scan; Pro 300,000 pageviews and 4,000 pages per scan. Basic and Pro displayed $0.30 per extra 1,000 pageviews.	Annual pricing, currency and tax can change the payable amount. Ultimate showed unlimited pageviews but still an 8,000-pages-per-scan limit.
OneTrust	Custom “Get Pricing” model rather than a public CMP list price.	The official page said CMP pricing is based on average daily visitors aggregated across channels and properties. Other solution packages use value-based meters such as profiles, admin users or inventory.	Request a scoped quote and document the meter, tier thresholds, included properties, services and renewal rules. Do not infer a price from third-party estimate sites.

Understanding the Cookiebot pricing model

Cookiebot pricing intent is often “How many subpages will I be charged for?” rather than “How many visitors do I have?” On the official Cookiebot pricing page, the free and Premium Lite cards each showed up to 50 subpages and one domain, while the paid card stated no traffic limitation. The page also warned that plans automatically upgrade according to the website’s number of subpages.

That model can be predictable for a compact corporate website. It requires more care for a store, publisher or multilingual site where crawlable URLs can grow. Before selecting a tier, run the vendor’s size check, investigate parameter and duplicate URLs, and ask how frequently account size is reassessed. If you are comparing migration paths, use CookiePilot’s Cookiebot alternative overview and Cookiebot migration checklist, then validate the final plan directly with both vendors.

Understanding consentmanager pricing

Searches for “consentmanager pricing” and “consentmanager.net pricing” usually need a direct answer about the usage meter. On the official consentmanager pricing page, paid CMP plans included monthly view allowances, with additional views charged beyond the allowance. The plan cards also varied crawl frequency, support and advanced capabilities.

The practical calculation is therefore not only the base fee. Use expected monthly views, peak-month views, likely overage, required crawl frequency and support tier. Because the same official page showed a small inconsistency between the Starter card and FAQ overage figures during our check, obtain confirmation before using an overage rate in a procurement model.

CookieYes and pageview-plus-scan limits

The official CookieYes pricing page illustrates a combined model: per-domain pricing, monthly pageview allowances and pages-per-scan limits. A plan may fit traffic but not site size, or fit the scan size but create overage charges during a campaign. The page also states that additional domains need premium subscriptions, apart from the account’s single free plan.

This is why “cookie consent pricing” cannot be compared on one number. Put domains, pageviews and scanned pages in separate spreadsheet columns.

Why enterprise CMP pricing is often custom

Enterprise deployments may cover websites, mobile apps, connected TV, logged-in profiles, preference centres, multiple brands and formal support requirements. The official OneTrust pricing page uses value-based usage meters and asks buyers to request pricing. For its CMP package, it identifies average daily visitors aggregated across channels and properties as the meter.

A custom quote is not automatically expensive or poor value. It is simply less comparable without a written scope. Ask for the unit definition, measurement window, tier thresholds, implementation services, support, annual uplift and treatment of acquisitions or new properties.

Hidden CMP limits that change total cost

Automatic upgrades and overages

Two plans with similar entry prices can behave very differently when a limit is crossed. One may invoice a small overage; another may move the account to a higher tier. Ask for examples using your own peak figures, and request an alert before the threshold where possible.

One domain does not always mean one web property

A business may have a marketing site, shop, customer app, help centre and country domains. Inventory them before procurement. Include sites scheduled to launch during the contract, not only today’s production list.

“Unlimited traffic” can coexist with another limit

Unlimited pageviews do not necessarily mean unlimited domains, scanned pages, users, languages, records or support. Conversely, a traffic-based plan may include generous scanning and features. Read every column in the comparison table.

Consent records and retention

Determine whether the CMP provides evidence of consent, what data is stored, how long it is retained and whether exports are included. Check how access and deletion requests are handled. A low-cost plan that cannot support your evidence process may create manual work elsewhere.

Implementation, tag remediation and testing

The CMP script is only one component. Teams may need to inventory tags, classify purposes, rewrite banner text, configure default consent states, connect a tag manager, block embeds and test Accept, Reject and granular choices. A Google Tag Manager integration guide can reduce guesswork, but time for QA still belongs in TCO.

Maintenance after launch

New marketing tools, plugins and embeds can introduce trackers. Budget for periodic scans, review of unknown services, regression tests and updates to notices. Assign an owner. “Nobody owns it” is a hidden cost because problems are discovered late and handled urgently.

Support and migration

Confirm the included channel and response target. Migration may require mapping categories, preserving banner wording, replacing scripts, reconfiguring tags and deciding whether old consent evidence must remain accessible. Avoid assuming a vendor will perform this work because migration is mentioned on a sales page.

Cost scenarios without false precision

The following scenarios are planning ranges, not vendor quotes. Internal labour varies by site quality, team experience and local rates. Substitute your own hourly cost and obtain legal advice where needed.

Scenario	Likely subscription pattern	Initial work to budget	Main TCO risk
Small brochure site: one domain, fewer than 50-100 pages, modest traffic, analytics only	Free or entry tier may be sufficient if required records, branding and integrations are included	Several hours for inventory, copy, setup and choice testing; more if legacy tags fire early	Choosing free solely on price and discovering a missing feature later
Growing e-commerce store: one domain, thousands of URLs, paid media and seasonal peaks	A paid tier with adequate scan size or traffic allowance	Roughly one to several working days for tag mapping, Consent Mode, checkout testing and remediation	Product URLs exceed scan limits or peak campaigns generate overages
Multilingual SaaS: marketing site, app and help centre across regions	Multi-domain or higher feature tier; possibly a custom scope	Several working days across marketing, development and privacy stakeholders	Treating subdomains, languages or authenticated consent as automatically included
Agency portfolio: 20 client domains	Agency, volume or multi-domain arrangement	A repeatable template plus per-client discovery, QA and handover	Buying 20 retail subscriptions without comparing partner terms, ownership and offboarding
High-traffic publisher or enterprise group	Usage-based or negotiated enterprise contract	Discovery, security review, procurement, integration and staged testing	Undefined usage meter, TCF needs, SLA, annual uplift or new-brand treatment

For a simple numerical model, calculate three cases:

• Expected case: normal traffic and the current site/domain inventory.
• Peak case: highest plausible campaign month plus planned launches.
• Growth case: expected domains, pages and traffic 12 months from now.

If a vendor charges overages, calculate a range using the expected and peak excess rather than assuming every month equals the annual average. If the official rate is unclear, mark the cell “vendor confirmation required” instead of inserting a guessed number.

A practical CMP pricing checklist

Use this list before requesting or approving a quote:

• List every production domain, subdomain, app and staging environment.
• Record current monthly pageviews and the highest month in the last year.
• Estimate crawlable pages, including products, filters, archives and locales.
• Confirm how the vendor defines a pageview, visitor, domain and subpage.
• Separate must-have features from optional features.
• Check Google Consent Mode v2, GTM and advertising-tag requirements.
• Verify consent records, retention, exports and access controls.
• Compare monthly and annual commitments, taxes and renewal terms.
• Ask what happens at a limit: alert, overage, throttling or automatic upgrade.
• Check scan frequency and how unknown cookies or services are reviewed.
• Price implementation, remediation, QA, training and ongoing ownership.
• Test Accept all, Reject all, granular choices and consent withdrawal.
• Confirm support channels, response targets and paid onboarding.
• Document migration, cancellation, data export and offboarding procedures.
• Recheck the official pricing page immediately before approval.

If you are still deciding whether a no-cost tool is enough, compare the limitations in the free cookie banner guide rather than assuming free and paid CMPs differ only in appearance.

Common CMP pricing mistakes

Avoid comparing only starting prices, modelling only average traffic, ignoring URL growth or treating every named feature as equivalent. A low licence fee does not classify tags, test the site or guarantee compliance. Assign a maintenance owner and save the official source URL and verification date with every comparison.

For a broader shortlist, see Cookiebot vs CookieYes vs CookiePilot, then verify the purchasing details on each vendor’s official page.

CMP pricing FAQ

How much does a CMP cost?

There is no universal price. A simple site may fit a free or low-cost plan, while multi-domain, high-traffic or enterprise deployments can require higher tiers or custom pricing. Calculate subscription, usage, implementation and maintenance together.

How much does a cookie banner cost?

A basic banner can cost nothing, but a banner is not the whole consent operation. Scanning, tag controls, regional rules, records, integrations, support and ongoing review can add software and labour costs.

What is consent management platform pricing based on?

Common meters are domains, pageviews, visitors, subpages, scanned pages and feature tiers. Enterprise platforms may combine usage across websites, apps and other properties. Always ask for the vendor’s exact definitions.

What is the Cookiebot pricing model?

Cookiebot Core uses domain and subpage-based tiers. On 9 August 2026, its official pricing page showed a free plan and Premium Lite at €7/month for up to 50 subpages and one domain, with no traffic limitation on Premium Lite. The page says plans can automatically upgrade based on subpage count. Check the live calculator because billing period, currency and higher tiers are dynamic.

What is consentmanager pricing based on?

The official consentmanager page showed paid monthly plans with included view allowances and additional-view charges. It also varied crawl frequency and features by tier. Confirm the overage rate before purchase because the plan card and FAQ figures were not fully consistent during our check.

Is pageview-based or per-domain pricing better?

Neither is inherently better. Per-domain pricing can be predictable for a high-traffic single site. Pageview pricing may work well for several low-traffic properties if the domain terms allow them. Model your actual domains, traffic peaks and growth under each offer.

Does unlimited pageviews mean there are no limits?

No. The plan may still limit domains, subpages, pages per scan, scan frequency, users, records, languages, branding or support. “Unlimited” should always be tied to a named billing unit.

Does a paid CMP guarantee GDPR compliance?

No. A paid CMP can provide useful controls and evidence, but the organisation remains responsible for its legal basis, notices, vendor choices, technical deployment and processes. Seek qualified legal advice for your circumstances.

How often should CMP costs be reviewed?

Review at renewal and after major changes such as a redesign, new market, acquisition, traffic campaign, app launch or tag-stack change. A quarterly usage and configuration check is a practical cadence for fast-moving sites.

Choose on 12-month TCO, not the cheapest card

A sound CMP comparison uses one inventory and one set of assumptions across every vendor. Count domains, peak traffic and crawlable pages. Define required integrations, records and support. Add implementation and maintenance. Then test expected, peak and growth cases.

CookiePilot is designed to keep this comparison straightforward with published domain, traffic and feature limits. Review the current CookiePilot pricing, match a plan to your inventory, and start with a real website test before committing to a wider rollout.

Ready to compare your setup? List your domains, monthly and peak pageviews, approximate page count, required languages and tag stack. Then start free or contact CookiePilot for help mapping those requirements to the right plan.