For years, talking about consent in digital marketing meant talking about cookies, banners, and regulatory compliance. Today, the conversation is much broader.
The way a brand collects, interprets, and communicates user consent affects the data available to platforms such as Google Ads and Google Analytics 4 and, therefore, its ability to measure conversions, build audiences, and optimise campaigns.
This is where two elements that are often confused come into play: Consent Management Platforms (CMPs) and Google Consent Mode.
They are not the same thing, but they need to work together.
You can have a perfectly visible CMP on your website and still lose valuable measurement signals if the connection between consent, tags, and platforms is not implemented correctly.
What is a CMP and what is it used for?
A Consent Management Platform (CMP) is a platform designed to collect and manage users’ consent decisions regarding the processing of their data.
In practice, it is the technology usually behind the banner users see when they visit a website, allowing them to accept, reject, or configure different cookie categories and purposes.
But reducing a CMP to a cookie banner means looking only at the visible part.
Its role also involves recording user preferences and communicating those decisions to the rest of the brand’s technology ecosystem.
For example, a user may allow their data to be used for analytics but not for advertising personalisation. That decision needs to be correctly translated into signals that different technologies can interpret and respect.
In addition, in certain advertising scenarios, Google requires the use of a certified CMP integrated with the IAB Europe Transparency & Consent Framework (TCF), particularly for publishers using certain Google monetisation products in the European Economic Area, the United Kingdom, and Switzerland.
A CMP is not something you configure once and forget about: it needs to be regularly reviewed and updated to account for new cookies, tools, and changes in the measurement architecture.
Therefore, choosing and correctly configuring a CMP is not simply a UX or compliance decision. It is also part of a company’s data infrastructure.
What is Google Consent Mode?
This is where the second piece comes in.
Google Consent Mode does not replace a CMP.
While the CMP collects the user’s decision, Consent Mode communicates that consent status to Google tags so they can adapt their behaviour accordingly.
To simplify the process:
User → CMP → consent status → Consent Mode → Google tags → Google Ads / Google Analytics
This allows tags to behave differently depending on the preferences expressed by the user.
Consent Mode works with different consent signals, including:
ad_storage: controls storage related to advertising.analytics_storage: controls storage related to analytics.ad_user_data: communicates whether consent has been granted to send advertising-related user data to Google.ad_personalization: communicates whether consent has been granted to use data for personalised advertising.
This makes consent much more than just a legal layer on a website: it becomes part of the measurement architecture.
CMP and Consent Mode: two different parts of the same system
A simple way to understand it is to think that the CMP asks, while Consent Mode communicates.
The CMP collects what the user accepts or rejects. Consent Mode communicates those decisions to Google’s ecosystem.
Tools such as Google Ads and Google Analytics then adapt their behaviour based on those signals.
Problems arise when these components are not properly connected.
A brand may have implemented a CMP and assume its consent strategy is covered. But if preferences are not communicated correctly, tags fire when they should not, consent statuses fail to update after the user makes a choice, or discrepancies arise between tools, measurement quality can be affected.
This is where a seemingly technical issue starts to become a marketing problem.
How does consent affect campaign measurement?
Every interaction that cannot be observed in the same way changes the amount and type of information available to understand the customer journey.
This can have implications across several areas.
1. Conversion Measurement
When consent restrictions apply, some interactions cannot be measured using the same mechanisms as when a user has granted permission.
A proper Consent Mode implementation allows Google tags to adapt their behaviour according to the user’s consent status.
In certain configurations, Google can also use cookieless signals and modelling to help address measurement gaps created by users who have not granted consent.
The goal is not to bypass user preferences, but to build a measurement system that is prepared for an environment where different customer journeys can be measured differently depending on each user’s consent choices.
2. Data Quality
The problem is not always that a user rejects cookies.
Sometimes, it lies in how that acceptance or rejection has been technically implemented.
A CMP that is poorly connected to the tagging system can lead to situations such as:
- tags firing before the user’s consent status is known;
- signals not being updated after the user makes a decision;
- different configurations across pages or domains;
- discrepancies between the CMP, Google Tag Manager, and measurement platforms;
- unnecessary loss of signals that could otherwise be used while respecting user preferences.
The result is less consistent data on which investment decisions are subsequently based, as well as the risk of collecting data without the appropriate consent or legal basis.
3. Campaign Optimisation
One of the main benefits of Google Consent Mode is that it helps reduce the loss of measurement caused by users who do not accept cookies, while respecting their consent choices.
For example, if only 60% of a website’s visitors accept cookies, traditional measurement would provide direct visibility into only that 60%. Much of the behaviour of the remaining 40% would fall outside cookie-based measurement.
With Consent Mode, Google can use signals without personal identifiers and modelling techniques to estimate some of the behaviour and conversions of users who have not consented to cookie-based measurement.
This does not mean identifying those users or reconstructing their individual activity. Instead, aggregated patterns are used to model conversions and reduce measurement gaps.
The result is a more complete view of campaign performance and a stronger signal base for Google Ads optimisation algorithms.
In an ecosystem where a significant share of users may not accept cookies, Consent Mode helps brands move from completely losing that portion of measurement to estimating part of it through modelling, while respecting users’ privacy preferences.
4. Audience Building and Activation
Consent management also determines which data can be used for certain advertising and personalisation purposes.
Signals such as ad_personalization and ad_user_data communicate the corresponding user preferences to Google’s ecosystem.
This means that consent, first-party data, and audience activation can no longer be treated as entirely separate conversations.
They are part of the same architecture.
Having consent mode does not mean it is properly implemented
This is one of the most common mistakes.
Activating a CMP, installing Google Tag Manager, and configuring Consent Mode does not automatically guarantee that everything is working correctly.
The implementation should be validated end to end.
For example:
- What happens when a user accepts all purposes?
- What happens when they reject them?
- Are consent states correctly established before the user interacts with the banner?
- Are they updated afterwards?
- Do tags respect those states?
- Is behaviour consistent across all pages and domains?
- Are Google Analytics and Google Ads receiving the expected signals?
This is why configuration is not the same as validation.
And that distinction matters when a brand is making investment decisions based on data that may be arriving incomplete or inconsistently.
A measurement architecture is built in layers
The entire process can be understood as a chain:
Consent → signal quality → first-party data → measurement → optimisation → growth
CMP and Consent Mode sit near the beginning of that chain.
If signal collection and transmission fail, the problem can spread to GA4, Google Ads, audiences, attribution models, and the algorithms responsible for optimising investment.
That is why reviewing consent does not simply mean reviewing a banner.
It means reviewing one of the first points of entry for data across the entire growth system.
What should brands review?
A good audit should start by understanding how consent travels from the moment a user enters the website until the relevant platforms receive the corresponding signals.
Some particularly important areas to review include:
- which CMP is being used and how it is configured;
- how different preferences are collected;
- how the CMP connects with Google Consent Mode;
- which consent states are set by default;
- how those states change after user interaction;
- which tags fire in each scenario;
- how Google Tag Manager is configured;
- what information Google Analytics 4 and Google Ads receive;
- whether there are discrepancies between domains, markets, or properties;
- how first-party signals are being incorporated;
- and how all of this fits into the overall measurement strategy.
The goal is not to collect more data by ignoring user preferences.
It is about achieving the best possible measurement within the consent choices expressed by each user.
Consent is also part of your growth strategy
Modern marketing increasingly depends on systems capable of connecting data, technology, platforms, and decisions.
But any growth system is only as good as the signals it receives.
That is why an advanced measurement strategy does not necessarily start with a dashboard. It starts much earlier: with how data is collected, under what conditions it can be used, and how that signal travels correctly throughout the technology architecture.
CMP and Google Consent Mode are part of that infrastructure.
And reviewing their implementation should not only be a compliance conversation.
It should also involve marketing, data, technology, and business teams.
Because moving from fragmented measurement to a connected system is not simply about adding more tools. It is about making consent, data, technology, and activation work together.
And when the signal is stronger, so are the decisions built on top of it.
