What Is a Consent Management Platform (CMP)
What a CMP does, the four jobs it has to get right, and how it differs from a plain cookie banner.
6 min read
A consent management platform (CMP) is the software that asks your visitors for permission to use cookies and trackers, records their choice, and signals that choice to every tool that needs it. It is the control layer between someone landing on your site and the analytics, advertising, and personalization scripts that want to run.
The Four Jobs a CMP Has to Do
A banner is the visible part, but a real CMP does four things:
- Collect consent through a banner or preference center, in the language and layout each region requires.
- Store a durable, timestamped record of what each visitor agreed to, so you can prove it later.
- Enforce the choice by blocking or allowing scripts and cookies before they run, not after.
- Signal the choice downstream, to Google Consent Mode, the IAB TCF, and opt-out signals like the Global Privacy Control.
The fourth job is where most homegrown banners fall short: they show a banner but never actually stop the trackers, which is the part regulators fine you for.
CMP vs a Cookie Banner
A cookie banner is a UI element. A CMP is the system behind it. Anyone can drop a banner on a page; the compliance question is whether non-essential tags are genuinely blocked until consent, whether the record would survive an audit, and whether the same setup adapts when a visitor is in Berlin versus California. A banner that "accepts" on load, or that logs nothing, is theater.
Why It Has to Be Real-Time
Cookies and pixels fire the instant a page loads. If your consent tool checks permission after the tracker has already run, the data is already gone and the violation already happened. This is why blocking has to happen before scripts execute, and why bolting a banner onto a tag manager after the fact so often leaves trackers firing underneath it.
How Concord Fits
Consent Management is one of Concord's four pillars. Concord scans your site for trackers, blocks non-essential ones until the visitor agrees, stores the consent record, and signals the choice to Google Consent Mode and the IAB TCF, from one banner you configure without code. Because it shares a platform with privacy requests, data mapping, and policy management, the consent you collect lines up with the rest of your privacy program instead of sitting in a separate tool.