Definition
A consent management platform, or CMP, is software that manages visitors' permissions for cookies, similar storage and the processing that tags carry out. It does three things.
- Presents the choice. It shows the banner and the more detailed settings, grouped into categories such as analytics and advertising, in the wording and languages the business configures.
- Records the choice. It stores what each visitor agreed to and when, both so the choice is remembered on later visits and so the business holds evidence of it. Where processing relies on consent, the GDPR expects the controller to be able to demonstrate that consent was given.
- Signals the choice. It exposes the result to the page, usually through a tag manager and through Google's Consent ModeA Google tag feature that adjusts what tags collect according to the visitor's consent choices., so that each tag knows whether it may set cookies or send data.
The platform does not decide what the law requires in a given market; the business and its advisers do, and the CMP is configured to match.
In practice: categories, defaults and tag behaviour
Configuration is where a CMP becomes part of measurement. Each tag is assigned to a category. A default state is set for each category before the visitor answers, typically denied where consent is required. And the platform updates that state the moment the visitor chooses. In a GTMTag management system. container, most CMPs supply a template that runs on the consent initialisation trigger, sets the defaults, loads the banner and issues the update; the consent mode guide explains how that wiring should look and how to verify it.
The order of events matters more than any single setting. If an analytics or advertising tag loads before the CMP has set its defaults, it fires as though consent were granted, whatever the visitor later says. The conversion tracking setup guide makes this one of its explicit checks: the consent state must be updated before the Google tag fires, and a denied state must actually stop cookies being set.
CMP versus consent mode
The two are often confused because they work together. The CMP collects the answer and remembers it. Consent mode is Google's signalling layer that carries the answer to Google's tags and changes how those tags behave. Without a CMP, consent mode has nothing to signal; without consent mode, or an equivalent tag-blocking rule, the CMP's answer never reaches the tags in a form they act on. Other vendors' tags, such as social pixels, take the answer through the tag manager's triggers instead.
Effects on data, speed and layout
A CMP changes the data by design. Visitors who decline are absent or only partly visible, so analytics describes consenting visitors rather than all of them, and the share varies by market and by banner design. The privacy, consent and measurement guide sets out what each consent state leaves in the reports, and why every banner change should be dated as a break in the series. Pressure on Third-Party CookiesCookies set by a domain other than the site visited, used to recognise a browser across sites. and the shift towards First-Party DataData a business collects directly from its own customers, visitors and users. make the consented, first-party signal more valuable, not less.
It also changes the page. A banner is another script, and one injected above existing content moves the page as it appears. The landing page speed and mobile guide names a banner that pushes the page down as a cause of mis-taps, and the Core Web Vitals guide lists consent banners among the injected elements that need space reserved for them. When tracking stops suddenly, a CMP release is one of the first changes the tracking outage response SOP asks the team to check.
A campsite whose tags ran before anyone chose
Skelbrook Campsite adds a consent banner through a plugin that loads at the bottom of the page, after the analytics and advertising tags in the page header. A routine check shows analytics cookies set on every visit, including visits where the banner was rejected, and analytics recording around 9,200 sessions a month. The developer moves the CMP into the tag manager on the consent initialisation trigger, with analytics and advertising denied by default. The tags now wait for the answer. The next month analytics records about 6,100 sessions while bookings hold at roughly 230. The fall is explained in the monthly report as the share of visitors who decline, dated to the day of the change, rather than read as lost demand.
Related terms
Consent ModeA Google tag feature that adjusts what tags collect according to the visitor's consent choices. carries the CMP's answer to Google's tags. A GTMTag management system. container is where most CMPs connect to the tags they govern. The decline of Third-Party CookiesCookies set by a domain other than the site visited, used to recognise a browser across sites. and the reliance on First-Party DataData a business collects directly from its own customers, visitors and users. raise the stakes of collecting consent properly, because consented first-party signals are what measurement increasingly rests on.
Common confusions
- A banner is not compliance. The configuration behind it decides whether tags actually respect the answer.
- A CMP is not consent mode. One collects and stores the choice; the other passes it to Google's tags.
- A drop in sessions after a CMP change is not a tracking fault. It may be the setup working as intended.
- The vendor's template defaults are not a decision. Default states and regions should be set deliberately and recorded.
- Consent counts and analytics counts are not meant to match. The CMP counts banner interactions, including people who leave before any tag could run.
