Concord, a broad product with three meters
Concord is genuinely more than a cookie banner, and that's the honest case for it. Alongside consent it gives you a privacy centre, privacy-request handling and data mapping, so a small team can cover several privacy jobs with one subscription instead of three. Its documentation is also unusually good. It states IAB TCF v2.3 support explicitly, explains how Google Consent Mode v2 behaves alongside a TCF string, and doesn't leave you guessing about which signal does what. Plenty of vendors charging more are vaguer than this.
The trade-off is how it counts. The free plan is $0 for 5,000 monthly sessions, but it is also capped at one domain, one policy, one user and one regulation — so it stops being viable the moment you have a second site or a second colleague. Paid plans run from $29 a month for Essentials and $99 for Pro, with Enterprise quoted. And the third meter is the one people don't budget for: privacy requests are rationed by tier, at 50 a month on Essentials, 250 on Pro and 1,250 on Enterprise according to a Google-hosted product profile document. That is an allowance on something you don't control — the public decides how many requests you receive, not you. Worth adding that Concord's own pricing page and that profile document don't line up cleanly on plan names and session limits, so get your tier confirmed in writing.
Conzent vs Concord at a glance
| Conzent | Concord | |
|---|---|---|
| Pricing model | Per site, not per session — the price drops as you add sites, and traffic never changes it. See current tiers | Per monthly session. Free at 5,000 sessions, Essentials from $29/mo, Pro from $99/mo, Premium also listed from $99/mo, Enterprise custom. A Google-hosted product profile maps those to 20,000, 100,000 and 500,000 sessions |
| What happens when you grow | Nothing — no allowance to exceed, no domain cap, no quota on the requests you receive | Three things move at once — sessions, the number of domains your plan permits, and your monthly privacy-request allowance (50 / 250 / 1,250 by tier) |
| GDPR / IAB TCF / Consent Mode v2 | ✓ GDPR, CCPA & 25+ regional laws ✓ IAB TCF v2.4 ✓ Consent Mode v2 (Basic & Advanced) — all included, every plan | Consent Mode v2 supported and clearly documented · IAB TCF v2.3 documented · the free plan covers one regulation only |
| CMS & platform integrations | 6 native integrations: WordPress, Wix, Joomla, Drupal, TYPO3, Umbraco — plus a universal script tag for anything else | No published CMS-by-CMS list. Documented integrations are Google-side, with Zapier and wider API access appearing on the higher tiers |
| Self-hosted / open source | ✓ Yes — OCI, Apache 2.0, one-line installer, unlimited sites and pageviews | ✗ Not published — no self-hosted or open-source edition appears in Concord's public material |
| EU data residency | ✓ Yes — managed cloud data hosted in Germany; self-host it and it never leaves your own server | No residency statement or selectable region published; ask before you sign if this is on your checklist |
| Free tier | ✓ Free forever if self-hosted; free trial on managed cloud | Yes — 5,000 sessions/month, but limited to 1 domain, 1 policy, 1 user and 1 regulation. 14-day trial on the paid plans |
Concord figures are taken from its public pricing page and a Google-hosted product profile document, both current in 2026. The two do not agree on every plan name and limit, and pricing changes — confirm the numbers with Concord before you switch. See Conzent's current plans.
Switching from Concord? Here's what to expect
Moving CMPs follows the same shape whichever vendor you leave: install the new script alongside the old one for a short test window, run a fresh scan to rebuild your cookie categories, configure and preview the banner, then switch the live script and remove the old one. Historical consent records stay with the vendor that collected them and don't transfer — that's normal for any CMP migration rather than anything specific to Concord, so plan to start your consent log fresh. One extra step applies here: because Concord also handles privacy requests and data mapping, work out where those jobs will live before you move the banner, so nothing quietly falls between the two tools.
Why teams switch from Concord to Conzent
One meter instead of three
Sessions you can forecast. Domains you can plan. The number of privacy requests strangers send you in a given month, you cannot. Conzent prices on the one number you actually control — how many sites you run — and the price per site drops as you add more.
The second site isn't an upgrade
A one-domain limit turns your next campaign microsite or country domain into a plan change. Conzent is built around multiple sites from the start, with IAB TCF v2.4, Consent Mode v2 and coverage for GDPR, CCPA and 25+ regional laws on every plan rather than on the ones above a certain price.
An exit that doesn't cost anything
Conzent's core is open source under the Apache 2.0 licence. If the commercial relationship ever stops working for you, you can run the same platform on your own server for free instead of starting another vendor search.
Frequently asked questions
How much does Concord cost?
Its public pricing page lists a free plan at 5,000 monthly sessions, Essentials from $29 a month, Pro from $99, a Premium tier also shown from $99, and Enterprise on request. A Google-hosted product profile document maps those tiers to 20,000, 100,000 and 500,000 sessions. The two sources don't label the ladder identically, so ask for your tier and its limits in writing.
Does Concord limit how many privacy requests I can handle?
Yes. The Google-hosted product profile lists 50 privacy requests a month on Essentials, 250 on Pro and 1,250 on Enterprise. It's an allowance on something outside your control, since the volume depends on how many people write to you. Conzent has no such quota.
Which IAB TCF version does Concord support?
Concord documents IAB TCF v2.3, and its docs explain how Google Consent Mode reads the TCF signal. Conzent runs IAB TCF v2.4 on every plan, including self-hosted.
Can I run more than one website on Concord's free plan?
No — the free plan is capped at one domain, one policy, one user and one regulation. Conzent's pricing is per site and the per-site price falls as you add sites, and self-hosting covers unlimited sites and pageviews at no cost.
What's the best alternative to Concord?
If it's the session meter, the domain cap or the request quota that's bothering you rather than the product itself, look for pricing set by site count. Conzent works that way, includes TCF v2.4 and Consent Mode v2 on every plan, hosts managed cloud data in Germany, and can be self-hosted for free if you'd rather own the whole thing.