Consent Management Platform (CMP)
Tracking & PrivacyDefinition
A Consent Management Platform (CMP) is the tool that asks visitors for permission to use cookies and tracking, records their choices and passes those choices to your analytics and advertising tags. It is the layer that keeps your tracking compliant with the GDPR and the ePrivacy rules while still allowing measurement where users agree.
A CMP sits between your website and every script that wants to set a cookie or send data to a third party. When a visitor lands on your site, the CMP shows the consent banner, lets the user accept, reject or customise categories such as marketing, statistics and preferences, and then stores that decision. Tools like Google Tag Manager, the Meta Pixel or GA4 read this stored decision and only fire when consent for the relevant category exists. Without a CMP you have no reliable, auditable record of who agreed to what, which is exactly what a regulator asks for first.
Most CMPs work either through the IAB Transparency and Consent Framework (TCF), which is built for programmatic advertising, or through a simpler category-based model that maps cleanly onto Google Consent Mode. For a typical lead-gen or e-commerce advertiser, the category-based approach paired with Consent Mode v2 is the practical choice: it signals consent state to Google in real time so that conversion modelling can fill the gap left by users who decline. The CMP is not just a banner, it is the source of truth that your entire tag setup obeys.
Technically the CMP loads first, before any marketing or statistics tag. It writes a consent string or a set of signals into the browser, and your tag manager listens for those signals. In Google Tag Manager you connect the CMP through built-in consent checks or a consent-aware template, so every tag has a required consent type before it is allowed to run. When the user updates or withdraws consent, the CMP re-broadcasts the new state and tags stop firing immediately. A correct setup also blocks tags by default until a choice is made, which is what the GDPR expects for non-essential cookies.
Getting the CMP right is the difference between tracking that holds up under audit and tracking that quietly breaks the law while also losing data. A misconfigured banner that fires tags before consent exposes you to fines and to the cleanup work of re-flagging everything later. On the other side, an overly aggressive banner that blocks Consent Mode signals starves Google's conversion modelling and makes your campaigns look worse than they are. The CMP is where privacy compliance and measurement quality meet, so it deserves the same attention you give bids and creative.
Related Terms
Related Services
Frequently Asked Questions
-
If your site uses non-essential cookies for marketing or analytics and you serve visitors in the EU, you need a way to collect and document valid consent before those cookies load. A CMP is the standard way to do that. Purely essential cookies do not require consent, but almost every advertiser uses tracking that does.
-
It changes what you can collect without permission, not your total ability to measure. Users who decline are not tracked with cookies, but Consent Mode lets Google model those conversions so you keep a usable picture. A well configured CMP often improves data quality because it removes the legal risk and the messy half-tracked sessions.
-
The CMP collects and stores the user's choice and shows the banner. Consent Mode is Google's mechanism that reads that choice and adjusts how Google tags behave, switching to modelled conversions when consent is missing. They work together: the CMP is the decision, Consent Mode is how Google reacts to it.
Make your consent setup audit-proof
We implement your CMP, wire it to Consent Mode and your tag manager, and verify that no tag fires before consent. The result: tracking that satisfies the GDPR and still feeds your campaigns clean data.