Are you paying too much for your CMP?
Published CMP prices run from €0 to €90 per domain a month. If your cookie consent comes as a quoted annual contract, here is how to tell if you overpay.
Some companies pay nothing for cookie consent. Others pay for it inside an enterprise privacy contract whose price nobody outside procurement has seen. Both can have a banner that works. The difference is rarely the banner: it is how the vendor charges, and how much platform comes with the part you actually use.
This post gives you a yardstick: what consent management platforms (CMPs) charge when they publish their prices, and the signs that you are paying for more than consent. If you are new to the term, start with what a CMP is.
What CMPs charge when the price is public
Self-serve CMPs put their prices on their websites. These are the ranges from each vendor's own pricing page, as we read them in September 2026:
| CMP | Published price | What the price follows |
|---|---|---|
| Cookiebot | €7-€90 a month per domain | Number of subpages on the domain |
| CookieYes | $10-$55 a month per domain | Pageviews, with $0.30 per 1,000 above the plan on Basic and Pro |
| Usercentrics | €7-€50 a month, custom above that | Sessions and a domain cap; the plan upgrades automatically when a limit is passed |
| Cookie Information | From €19.50 a month per domain | Domains, consents per account and scanned URLs |
| Katla | €9-€59 a month per site | Pages per scan and consents per site, with no overage charge |
| OneTrust | Not published | Quoted by sales; cookie consent is one module of a wider privacy suite |
Most of them also have a free tier. So on a self-serve plan, cookie consent for one site costs from a few euros to around €90 a month at list price, with traffic-metered plans climbing from there. That is the range to hold any quote against.
Five signs you are paying too much
1. You pay for a suite and use the banner. Enterprise privacy platforms sell consent next to request handling, vendor risk and assessments. If your team only uses the banner and the cookie list, the rest is platform you carry without using. Ask what the consent part costs on its own; if the vendor cannot say, that is an answer too.
2. The price is a quote you cannot compare. When pricing is not published, you cannot benchmark it, and every renewal is a negotiation you start without data. Put your annual contract next to the table above, per domain and per month, and see what the difference buys.
3. Your bill follows your traffic. Pricing on pageviews or sessions means a good month arrives as a bigger invoice, or a bigger plan. CookieYes charges $0.30 for every 1,000 pageviews above the plan; Usercentrics moves you up a tier when you pass a limit. For a shop whose traffic peaks in November, that is a cost that grows exactly when the margin matters.
4. You pay a lot and it still sets cookies before consent. Price says nothing about whether the banner does its job. Open your site in a private window, open DevTools and look at the cookies before you click anything. If analytics or advertising cookies are already there, the expensive part is not working. Our cookie checker runs the same check on any URL, without an account.
5. It slows every page down. The consent script loads before anything else, on every page view. A heavy one costs you Core Web Vitals on the pages that earn the money. Check its size in the Network tab of DevTools, as served to a first-time visitor.
What not to cut
A cheaper CMP is only cheaper if it does the parts you need. Before you switch, check:
| If you need | Check that the new CMP has |
|---|---|
| Personalised ads through AdSense, Ad Manager or AdMob in the EEA, UK or Switzerland | IAB TCF support, which Google requires for those products |
| Proof of consent | Records of each visitor's choice and when it was made |
| A procurement process | A data processing agreement, an SLA and invoicing |
| Many brands or countries | One place to run every site, and a price for the whole estate |
And plan the move: you can run both while you switch site by site, but never two consent scripts on the same page, or they will fight over the same cookies.
Where Katla fits
Katla is a CMP that does consent and stops there, at a price you can see. Plans are €9, €29 and €59 per site a month, or €7, €23 and €47 billed annually, excluding VAT. There is no charge per 1,000 pageviews: plans have page and consent limits, and when you outgrow one you move plan deliberately rather than finding out from the invoice. The free plan scans your site and generates a cookie policy without a card. For many sites, a custom plan adds volume pricing across sites, a DPA, an SLA and invoicing.
It is not the lowest list price for every shape of site, and we would rather say so. What it gives you for the price:
- Blocking before consent. In GDPR mode, the cookie guard refuses cookies outside the categories a visitor accepted, and deletes any that were set before it started.
- Reject next to Accept on the first layer, with nothing pre-selected.
- AI cookie scanning, and a cookie policy generated from the scan in 13 languages, which updates itself after every scan.
- Google Consent Mode v2 and Global Privacy Control built in.
- A light script: about 18 KB with the banner and 4 KB headless, measured over the wire.
- Hosting in the EU, in Frankfurt.
- Any platform: one script in the head or one Google Tag Manager tag, on whatever your sites run on.
Katla does not support the IAB TCF. If you sell personalised ads through Google's publisher products in Europe, you need a TCF-certified CMP, and Katla is not one.
If you are weighing a move from an enterprise suite, our comparison with OneTrust covers how the two can run side by side while you switch site by site.
Tip
Before your next renewal, divide your consent contract by the number of domains it covers and by twelve. Then compare that monthly figure per domain with the published prices above.
Competitor prices are as listed on each vendor's own pricing page when we checked them in September 2026, and may have changed since. Katla's prices exclude VAT.