Journal · CMP guides
What is a consent management platform (and when do you need one)
A consent management platform, or CMP, is the software that asks your visitors what data collection they allow and records each answer as proof. It then passes that choice to your analytics and advertising tags, so they collect only what was permitted. The cookie banner is the part visitors see; the CMP is the whole engine behind it.
What does a consent management platform do?
A consent management platform does two jobs at the same time, and most definitions only mention the first.
The first job is compliance. The platform shows the banner and captures whether a visitor accepts or rejects. It blocks non essential tags until there is a lawful basis to fire them, and it writes every decision to an audit ready log you can produce if a regulator asks. This is the part every vendor glossary describes.
The second job is measurement. The same consent decision has to reach your analytics and advertising tags in a language they understand, or those tags either over collect and break the law or under collect and quietly lose data. A CMP wired to Consent Mode v2 translates each choice into the signals Google expects, so Google's tags know what each visitor chose. Under Advanced Consent Mode, a rejected visit can still send a cookieless ping instead of leaving no trace at all. Capture the choice, then carry it: a platform that only does the first half is a banner, not a CMP.
Is a cookie banner the same as a CMP?
It is worth being precise, because the two words get used as if they mean the same thing. The banner is the front end: the box a visitor sees, with an accept and a reject. The consent management platform is everything behind it. It categorises the cookies and tags on your site and stores each consent decision with a timestamp. It asks again when consent has expired, and it keeps the signal flowing to your measurement tools in the state the visitor chose.
Same click. Only the CMP changes what tags do.
Banner only
Collects a click
- Tags never told the choice
- No proof kept
- Google gets no signal
Consent management platform
Acts on the choice
- Applies the choice to tags
- Logs each decision
- Sends Consent Mode signals
When do you actually need one?
The honest answer is that it depends on where your visitors are and what you collect, not on a scare number. A few clear signals tell you whether a CMP is genuinely required rather than nice to have.
You have EU or UK visitors and you run any tags
If people in the EU or UK reach your site and you load analytics or advertising tags, you need a way to ask first and to prove what was chosen. Article 5(3) of the ePrivacy Directive requires consent before storing or reading anything on a visitor's device that is not strictly necessary. This is the most common trigger, and it applies even to a small site that only runs GA4.
You serve California or other US privacy states
Several US states now give people the right to opt out of sale and sharing, and some require sites to honour a Global Privacy Control signal sent by the browser. You need something that can receive that signal and act on it, which a bare banner cannot do.
You depend on Google Ads or GA4 for decisions
The moment your marketing spend is steered by conversion numbers, the measurement job stops being optional. Without consent wired to your tags the way Google expects, the sessions behind the banner drop out of your reports and you optimise against a distorted picture.
If none of these apply, a purely local site with nothing beyond strictly necessary cookies may not need a CMP at all. The point is to decide from your regions and your tags, not from a vendor's fear copy; the same test tells you whether you need a cookie banner in the first place.
Do you need a Google certified CMP?
Only if you sell ad space through Google. Google requires a certified CMP integrated with the IAB’s Transparency and Consent Framework from partners serving personalised ads through AdSense, Ad Manager or AdMob to visitors in the EEA, the UK or Switzerland.
Buying Google Ads or running GA4 is a different position. That makes you an advertiser, and this requirement is written for publishers. Your job is to get the consent signal to Google’s tags, so check whether your site needs the TCF before you filter vendors on that badge.
Velo is not a registered TCF CMP yet, and our TCF status page keeps the current position. A publisher with this requirement should choose a certified platform for now.
How can you tell whether your CMP is working?
Test what your tags do after a choice, because a banner can look right while changing nothing. Use a private window with the browser’s developer tools open.
Reject, then look at the cookies
Reject everything and reload. Analytics and advertising cookies such as
_gashould not appear in the Application tab. If they do, find out which tag really set them.Read the signal Google received
Filter the Network tab for
collectand find thegcsparameter.G100means both storage types were denied, andG1--means the tag fired with no consent state attached. Under Basic Consent Mode you should see no request at all.Accept, then look for the change
In a new private window, accept everything. The next Google request should carry
gcs=G111. If it still saysG100, the choice never reached your tags.Find your test in the consent log
Open the platform’s log and look for both test visits with their timestamps. A choice that was never recorded cannot be proved later.
The gcs value covers only two of the four signals. For ad_user_data and ad_personalization, run the full Consent Mode v2 check.
What does a CMP change in your analytics?
Vendor glossaries describe a CMP as a compliance tool and stop there. That framing hides the expensive half. When the consent update never reaches your tags, Google keeps every visitor at the denied default, and your GA4 and conversion numbers undercount without a single error showing up. With no consent state at all, the opposite happens: tags fire as if everyone accepted. How much traffic sits behind the banner varies with region, audience and banner design. Measure your own: read the accept rate in your CMP, or compare GA4 sessions with the requests your server or CDN logged over the same days. Whatever the share, a CMP that only does compliance leaves that slice of your measured traffic uncounted.
Under Advanced Consent Mode, the measurement job gives Google a signal on every visit, including the rejected ones. That is what makes modelling possible, and it has limits. Modelling only fills part of the gap, and only when a property runs Advanced Consent Mode and meets Google’s published eligibility thresholds. Below them nothing is modelled at all, and modelled data never reaches the BigQuery export or your audiences. An honest CMP definition names both what the signal makes possible and where it stops.
Your next step in website privacy.
Velo sets your consent defaults, passes the four signals to Google’s tags and keeps a record of every choice your visitors make.
Common questions
What is a consent management platform?
A consent management platform, or CMP, is the software that asks your visitors what data collection they allow and records each answer as proof. It then passes that choice to your analytics and advertising tags, so they collect only what was permitted. The cookie banner is the part visitors see; the CMP is the whole engine behind it, including the consent log and the signal it sends to tools like GA4 and Google Ads.
Is a cookie banner the same as a consent management platform?
No. The banner is the visible front end where a visitor accepts or rejects. The consent management platform is the engine behind it: it stores every decision in an audit ready log, blocks non essential tags until consent is given, and passes the consent state to your measurement tools. A banner with no engine behind it collects a click but changes nothing about what your tags actually do.
Do I need a consent management platform?
It depends on where your visitors are and what you collect. If you have EU or UK traffic and run any analytics or advertising tags, consent law requires you to ask first and keep a record, which is the job a CMP does. If you serve California or the other US states with privacy laws, you need a way to honour opt out and Global Privacy Control signals. A purely local site with no tracking beyond what is strictly necessary may not need one at all. The honest answer follows your regions and your tags, not a default.
Do I need a Google certified CMP?
Only if you serve personalised ads through AdSense, Ad Manager or AdMob to visitors in the EEA, the UK or Switzerland. Google requires those publishers to use a certified CMP integrated with the IAB's Transparency and Consent Framework. If you only buy Google Ads or run GA4, that requirement is not written for you, although Google's tags still need the visitor's choice.
Keep reading
Why does a tracking cookie come back after rejection?
You rejected, the cookie vanished, and then it was back. Four causes, which one you have, and how to make a rejection stick.
Does HubSpot need cookie consent?
HubSpot lists its tracking cookies and ad pixels as non essential. How to hold them until a visitor consents, and why gating your Meta and LinkedIn tags can miss them.
Start with a scan
See what your homepage already loads before you install anything. The free scanner reads the page and your public Tag Manager container.
A first pass, not a verdict. Four checks on your homepage, and we open your container.
Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.
Step by step installs for WordPress, Shopify, Webflow, Wix and more.
Free for one site
Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.