On one side, you need reporting you can actually use. You need to understand which channels are driving traffic, which landing pages are turning interest into leads, and where your spend is working hardest. On the other side, you need to respect consent choices properly and keep your setup aligned with UK privacy rules.
That tension is exactly why Consent Mode has become such a big talking point. Google describes Consent Mode as a way to communicate users’ consent choices to Google so tags can adjust their behaviour accordingly, but it is very clear that Consent Mode does not provide the banner or widget itself.
That distinction matters more than many teams realise. Consent Mode is not a shortcut around compliance, and it is not a replacement for a proper measurement strategy. It is one part of a broader setup that includes your banner, your tag governance, your reporting logic, and the way your organisation defines success.
That broader, joined-up approach fits naturally with services like Data & Analytics, Insight & Strategy, and SEO Performance because the real challenge is not just collecting data. It is collecting data in a way that stays commercially useful.
What Consent Mode actually does
At a simple level, Consent Mode passes consent signals from your banner or consent management platform into Google’s tags. Google says those tags can then adjust their behaviour based on whether consent has been granted or denied for specific purposes such as analytics or advertising storage.
In other words, Consent Mode is a control layer between the user’s choice and the way your Google measurement tools behave.
That means it is important not to overstate what it solves.
It does not write your consent copy. It does not decide whether your consent banner is fair, balanced, or clear enough. It does not automatically make an old tagging setup compliant. If your implementation is messy, Consent Mode can only work with the signals it receives and the tags you already have in place. That is why technical discipline still matters.
Why the UK legal context matters
In the UK, the rules around cookies and similar technologies are not just a background issue for legal teams. They directly affect how your analytics and advertising setup should behave.
The ICO says PECR contains the specific rules on storage and access technologies, and those rules apply whether or not personal data is involved. It also says PECR sits alongside the UK GDPR and uses the UK GDPR standard of consent where consent is required.
The ICO’s guidance further states that valid consent must be freely given, specific and informed, and it must involve an unambiguous positive action. It also says you cannot set non-essential cookies before the user has consented to them.
That is why “we have anonymised reporting” is not a full answer. If your setup stores or accesses information on a device for non-essential purposes, you still need to think carefully about the PECR side of the picture.
The ICO’s newer storage and access technologies guidance also makes clear that this area is wider than just traditional cookies. It covers things like tracking pixels, link decoration and navigational tracking, device fingerprinting, web storage, and scripts or tags.
For marketing teams, the practical point is straightforward: useful measurement is not just about recovering more data. It is about making sure your setup respects the user’s choice before that data is collected in the first place.
Basic and advanced Consent Mode are not the same thing
A lot of people talk about Consent Mode as though it is one standard implementation. Google’s documentation says otherwise.
With basic Consent Mode, Google tags are blocked until the user interacts with the consent banner. Google says that in this version, no data is sent to Google before interaction, and if the user does not consent, no data is transferred to Google at all.
With advanced Consent Mode, Google tags load with default consent states and, while consent is denied, Google says the tags can send cookieless pings. If consent is later granted, full measurement data can then be sent. Google also says advanced Consent Mode supports more detailed advertiser-specific modelling compared with the more general modelling associated with the basic version.
That difference matters because your measurement outcomes will not be the same under both approaches. If you choose a basic implementation, you should expect bigger reporting gaps before consent is granted. If you choose an advanced implementation, you need to be even more confident that your consent defaults, tag behaviour, and governance are set up correctly.
Neither option is automatically right in every situation. What matters is whether the setup matches your banner logic, your organisation’s risk tolerance, and the type of reporting you actually need.
Why Consent Mode can help without being a magic fix
One of the biggest misunderstandings around Consent Mode is the idea that it “fixes” analytics.
It does not. If more users are given a meaningful choice, some of them will say no. That means some directly observed data will disappear.
Google is explicit that when users decline analytics cookies, Analytics will be missing data, and behavioural modelling for Consent Mode uses machine learning to model the behaviour of those users based on the behaviour of similar users who accepted analytics cookies. Google says this modelled data is there to help you gain useful insights while respecting privacy.
That is useful, but it changes how you should think about reporting.
You should stop expecting every report to look as complete as it did in older, less consent-aware setups. Instead, you should aim for reporting that is directionally reliable, commercially meaningful, and honest about where direct observation ends and modelling begins. That is why event design, conversion definitions, and business context matter so much.
Clean measurement matters more when consent reduces visibility
When visibility becomes partial, noise becomes even more expensive.
If your GA4 setup is full of duplicate events, vague click tracking, and conversions that do not really represent business value, Consent Mode will not rescue it. In fact, weaker visibility makes those problems more obvious because you have less room for sloppy measurement.
That is why your measurement model should be clear before you worry about dashboards. You need to know which actions genuinely matter, how they map to leads or revenue, and which events are just background activity.
If you work in lead generation, this becomes especially important. A form start is not the same as a qualified enquiry. A button click is not the same as a sales conversation. If your reporting treats these actions as interchangeable, your optimisation decisions will become weaker, not stronger.
What a compliant and useful setup looks like in practice
A good setup is not defined by whether the banner looks modern. It is defined by whether the whole system behaves properly.
In practice, that means you should be able to answer questions like these with confidence:
- What consent states are set by default?
- Which tags are blocked until consent is granted?
- Which tags still load, and why?
- How is the consent state updated after the user acts?
- Can users reject as easily as they accept?
- Can they change their mind later without unnecessary friction?
- Are your reports built around meaningful commercial events rather than vanity metrics?
The ICO’s guidance makes the user-choice side of this especially important. It says consent must be a clear positive action, that continuing to browse is not enough, and that users should have an easy means to enable or disable non-essential cookies.
Google, meanwhile, provides ways to set up, verify, and troubleshoot consent signals, including guidance on checking whether GA4 is receiving the necessary consent signals and verifying implementation using Tag Assistant.
This is why compliance and performance should not be treated as opposites. In many cases, the work that improves compliance also improves reporting quality. Better tagging discipline, better event design, and clearer governance usually lead to cleaner data.
Common mistakes that create false confidence
Most problems in this area are not caused by Consent Mode itself. They come from the way it is deployed.
One common mistake is assuming that enabling Consent Mode means the privacy side is “done”. Google explicitly says Consent Mode does not provide the banner or widget and works with your consent solution rather than replacing it.
Another mistake is assuming that any data labelled as “modelled” should be treated as exact truth. Google positions modelling as a way to fill gaps and improve insight, not as a guarantee of perfect reconstruction.
A third problem is relying on legacy setups. If your site has overlapping tags, forgotten pixels, inconsistent triggers, or unclear ownership, consent-aware reporting becomes far harder to interpret. That is where Development, Organic Marketing, and Paid Advertising all have a role. Measurement does not sit in one box. It touches the site build, the traffic sources, the conversion journey, and the reporting model.
How to keep analytics useful when some data is missing
The answer is not to chase perfect visibility. That is not realistic.
The better goal is to preserve strong signal quality. You want enough reliable information to answer the questions that actually matter to the business: which landing pages generate better leads, which campaigns influence the pipeline, where users drop out of the journey, and which improvements lead to better outcomes in £.
That often means shifting your focus away from surface-level totals and towards business-led interpretation. If you are linking your measurement to lead quality, sales progression, assisted conversion value, and channel contribution, you can still make good decisions even when not every session is directly observable.
That mindset also lines up with Measuring SEO ROI in £: a practical model for pipeline, assisted conversions, and revenue and the wider commercial focus across Totally Digital’s services.
The best way to think about Consent Mode
Consent Mode is best treated as a control layer, not a miracle tool.
Used properly, it helps your Google tags respond to user choices in a more structured way. It also helps reduce some of the blind spots that appear when users decline analytics or advertising storage, especially where modelling is available and your setup qualifies for it. But it only works well when the rest of your setup is sound: fair consent choices, clean tag governance, sensible event planning, and reporting built around real business questions.
If you want your analytics to stay useful while staying compliant in the UK, that is the balance to aim for. Not perfect visibility. Not legal box-ticking. Just a measurement framework that respects user choice, stands up to scrutiny, and still helps you make smarter decisions.
If you want help tightening up your measurement strategy, refining your tag governance, or making Consent Mode part of a more useful reporting setup, get in touch with Totally Digital and build something that works in the real world.