Google Consent Mode V2

Google Consent Mode V2 tells Google tags whether a website visitor has accepted or rejected different types of tracking. For UK tracking, it matters because Google Analytics 4, Google Ads, remarketing, and conversion measurement all rely on how consent choices are collected, passed to Google, and respected by the website.

If your cookie banner, GA4 reports, or Google Ads conversions have started to feel harder to trust, you are not alone. Many UK businesses are trying to work out whether their tracking is still set up properly, especially when visitors reject cookies or paid media data looks thinner than expected.

Consent Mode V2 is not a cookie banner, and it is not a legal compliance switch. A consent banner or consent management platform collects the visitor's choice, while Consent Mode V2 passes that choice to Google tags so they can adjust their behaviour.

For UK businesses, the challenge is balancing useful marketing data with PECR, UK GDPR, clear cookie notices, and changing rules under the Data (Use and Access) Act 2025. C2 Marketing helps you understand what is working, what is not, and what needs fixing across tracking, Google Analytics, Google Ads, and wider digital marketing performance.

Google Consent Mode V2 And UK Tracking In Plain English

Google Consent Mode V2 connects your consent banner with Google measurement and advertising tools. When a visitor accepts analytics or advertising cookies, Google tags can run in the way you have configured them, and when a visitor rejects consent, the tags should adjust and avoid setting certain cookies or using data for restricted purposes.

The key point is that Consent Mode V2 does not collect consent by itself. Your website still needs a clear banner, proper consent categories, an accessible reject option, and a way for visitors to change their choice later.

So, does this mean your site is compliant once Consent Mode V2 is installed? Not automatically, because legal compliance depends on your cookie banner, privacy information, data purposes, tag behaviour, records, and whether each technology is genuinely necessary or consent based.

What Changed In Consent Mode V2?

The original version of Consent Mode focused mainly on two consent signals. One related to analytics storage, which controls whether analytics cookies can be used, while the other related to advertising storage, which controls whether advertising cookies can be used.

Consent Mode V2 added two more advertising related signals. One covers whether user data can be sent to Google for advertising purposes, and the other covers whether data can be used for personalised advertising, including remarketing and audience features.

In simple terms, the four areas are:

• Analytics storage controls whether analytics cookies can be used for tools such as GA4.
• Advertising storage controls whether advertising cookies can be used for Google Ads and related measurement.
• Advertising user data controls whether user data can be sent to Google for advertising measurement or matching.
• Advertising personalisation controls whether data can be used for personalised adverts, remarketing, and audience features.

These extra signals matter because modern paid advertising relies on more than a simple cookie being present. Conversion tracking, enhanced conversions, audience lists, and remarketing all rely on clear rules about what data can be used and for what purpose.

Is Google Consent Mode V2 Required In The UK?

If you use Google advertising or measurement products for UK visitors, Consent Mode V2 is highly relevant because Google treats the UK as a region where consent signals affect advertising and analytics functionality. Without the correct signals, some Google Ads and measurement features may be limited, especially around remarketing, personalised advertising, and conversion modelling.

That can feel worrying if paid media is a key part of your lead generation or sales. Nobody wants to lose useful data, waste budget, or make decisions from reports that do not show the full picture.

That does not mean Consent Mode V2 is the same thing as UK law. Google has platform requirements, while UK tracking rules come from PECR, UK GDPR, ICO guidance, and your own legal assessment.

A website can be technically configured for Google but still have problems if its banner is unclear, if tags fire too early, or if visitors cannot reject or withdraw consent properly. For businesses running paid campaigns, this is also a performance issue because poor consent setup can reduce the quality of conversion data, weaken remarketing lists, and make reporting harder to trust.

If Google Ads is a major growth channel, reviewing consent setup alongside PPC campaign management is usually a sensible step. It helps you protect both your measurement quality and the decisions you make from that data.

UK Tracking Rules And Consent

UK tracking is not just about cookies. PECR applies to storage and access technologies, which can include cookies, pixels, scripts, tags, local storage, tracking links, and similar tools.

In plain English, if a tool stores information on someone's device or reads information from it, you need to think carefully about consent. The ICO explains that organisations generally need to provide clear information and obtain consent before using these technologies unless a valid exception applies, and its official guidance is the best place to check the current position.

UK GDPR may also apply where tracking involves personal data. That can include online identifiers, user IDs, advertising IDs, IP addresses in context, or data that can be linked back to a person.

In practice, this means you need to think about transparency, purpose limitation, lawful basis, data minimisation, and keeping records of decisions. The Data (Use and Access) Act 2025 introduced additional exceptions for some low risk statistical purposes, but this should not be treated as a blanket analytics exemption.

Advertising, profiling, remarketing, cross site tracking, individual monitoring, and secondary use of data may still fall outside any exception. It is worth being cautious before relying on an exception without checking whether it genuinely fits your setup.

How Consent Mode V2 Works

When a visitor grants consent, Google tags can operate according to the categories that have been accepted. For example, if analytics consent is granted, GA4 can use analytics cookies as configured, and if advertising consent is granted, Google Ads conversion tracking and advertising cookies may also run depending on your tag setup.

When a visitor denies consent, Google tags should respect the denied signals. In some setups, Google may receive restricted cookieless signals, often called cookieless pings, but these do not work like normal cookie based tracking and should not be described as tracking every rejected user anonymously.

What does that mean for your reports? Cookieless pings can support aggregate reporting and modelling, but they do not recreate every individual visit or conversion.

This is why reporting after a consent update can look different from historical data. Sessions, users, journeys, conversions, and audience sizes may all change, so the data needs to be reviewed in context rather than treated as a like for like comparison.

Basic Versus Advanced Consent Mode

There are two common ways to think about Consent Mode implementation. Basic Consent Mode blocks Google tags until the visitor grants consent, which is often easier to understand because no Google measurement tag should run before the relevant choice is made.

Advanced Consent Mode loads Google tags with denied defaults before the visitor has made a choice. If consent is denied, the tags may send restricted cookieless signals rather than setting normal cookies, which can improve modelling potential but needs careful technical and privacy assessment.

• Basic mode means Google tags are blocked before consent, which is simpler and more conservative.
• Advanced mode means Google tags load with denied defaults and may send limited signals, which needs stronger governance.
• Measurement impact means advanced mode may support more modelling, but it is not automatically suitable for every UK website.
• Risk assessment means the right choice depends on your purposes, banner wording, legal advice, tag setup, and visitor regions.

Neither approach removes the need to control other tags. You might also have pixels, insight tags, heatmaps, chat tools, call tracking, and other third party scripts on your site, and these may need their own consent controls because Consent Mode V2 mainly communicates consent choices to Google tags.

What Happens To GA4 And Google Ads Data?

For GA4, denied analytics consent can reduce visible users, sessions, journeys, and event data. Some reports may become less complete, especially if a large share of visitors reject analytics cookies.

This can affect landing page analysis, channel comparisons, conversion rates, and content decisions. For Google Ads, denied advertising consent can affect conversion tracking, remarketing audiences, personalised advertising, enhanced conversions, and attribution.

Conversion modelling may estimate some lost measurement, but it should be treated as a model rather than a perfect replacement for observed user behaviour. This is where many business owners understandably get frustrated, because you may still be getting leads or sales even when your platforms do not show them as clearly as before.

Good reporting means looking beyond one platform and comparing GA4 with Search Console, CRM records, ecommerce revenue, form submissions, call data, and consent acceptance rates. C2 Marketing often connects tracking improvements with wider marketing analytics so businesses can make better decisions from imperfect but useful data.

How To Implement Consent Mode V2 In The UK

Start with a tracking audit. List GA4, Google Ads, Google Tag Manager, remarketing tags, enhanced conversions, pixels, scripts, consent tools, and any other platform that stores or accesses information on a visitor's device.

For each tool, record the purpose, provider, consent category, storage duration, and whether personal data may be involved. This gives marketing, development, and privacy teams a shared view of what is actually running on the site.

Next, configure the cookie banner or consent management platform. It should explain purposes clearly, offer genuine accept and reject choices, record the visitor's choice, and allow withdrawal.

The wording on the banner and cookie notice should match what the website actually does. If the banner says advertising cookies are optional, advertising tags should not run as though consent has already been granted.

Then set denied consent defaults before Google tags fire. The four Consent Mode V2 signals should be mapped to the right banner categories, and updates should be sent immediately when a visitor makes a choice.

If your website serves both UK and international visitors, regional rules may also need to be configured. This helps avoid applying one consent approach to every visitor when different regions may need different settings.

Finally, check every tag and trigger. Google tags need to respect consent signals, but non Google tags must also be controlled.

If you are using Google Tag Manager, it is worth reviewing your wider setup alongside practical resources such as GA4 tracking guidance. This helps ensure conversion events are accurate as well as consent aware.

How To Test Consent Mode V2

Testing should be done in a clean browser session, ideally using private browsing and cleared cookies. Before clicking the banner, check whether analytics or advertising cookies are being set, and inspect tag requests using browser developer tools or Google Tag Assistant.

Reject analytics and advertising consent separately if your banner allows it. Confirm that the consent state changes correctly and that cookies, events, and advertising tags behave as expected.

Then accept consent and check that the correct tags activate only after the relevant choice has been made. This should include GA4 events, Google Ads conversion tags, remarketing tags, and any other tool that depends on a consent category.

Do not forget withdrawal testing. A visitor should be able to change their mind, and the site should then update future tag behaviour.

Testing should be repeated after website releases, banner changes, new campaign tags, checkout changes, or updates to Google Analytics and Google Ads configuration. A small technical change can affect tracking, so regular checks are worth building into your process.

Common Consent Mode V2 Mistakes

One of the most common mistakes is setting consent defaults too late. If Google tags fire before denied defaults are applied, the first page view may already have been tracked in a way that does not reflect the visitor's choice.

The consent state should be available before measurement tags execute. This is especially important on fast loading pages where tags can fire before the banner has fully loaded.

Another common issue is assuming the banner is enough. A banner might record a choice, but if that choice is not passed correctly to Google tags, Consent Mode is not doing its job.

The same applies when only analytics and advertising storage are configured, while the two newer advertising signals are ignored. All four Consent Mode V2 signals need to be mapped correctly if you rely on Google advertising and measurement tools.

You might also forget about other tools on your site, such as pixels, chat widgets, heatmaps, or call tracking scripts. Consent Mode does not automatically stop every marketing script on the page.

A complete setup needs a tag inventory, clear ownership between marketing and development teams, and regular checks after new tools are added. Without that process, tracking can drift out of shape over time.

A Practical UK Consent Mode Checklist

A useful UK checklist should cover legal, technical, and reporting points. It should not sit only with the marketing team or only with developers, because privacy, analytics, web development, and paid media responsibilities often overlap.

• Assess whether PECR applies to your cookies, tags, scripts, pixels, and local storage.
• Check whether UK GDPR applies because personal data or online identifiers are involved.
• Do not overgeneralise the Data (Use and Access) Act 2025 statistical purpose exception.
• Make sure the banner has clear purposes, accessible reject options, and withdrawal controls.
• Set denied defaults before Google tags fire.
• Map all four Consent Mode V2 signals properly.
• Control non Google tags as well as Google tags.
• Keep records of testing, consent categories, tag purposes, and configuration changes.
• Compare GA4 data with CRM, sales, Search Console, and campaign data.

If you need support connecting consent, tracking, paid media, and reporting, C2 Marketing can help you see what is working, what is missing, and what needs fixing. That makes your marketing decisions easier to trust and your reporting easier to explain.

Final Thoughts

Google Consent Mode V2 is important for UK businesses because it affects how Google Analytics 4, Google Ads, conversion tracking, remarketing, and reporting work when visitors accept or reject consent. It helps Google tags respond to consent choices, but it does not replace a proper cookie banner, legal assessment, privacy notice, or careful tag control.

The best approach is practical and documented. Review your banner, check when tags fire, test what happens when consent is rejected, and compare GA4 with real leads, calls, enquiries, or sales.

For UK tracking, that combination of transparency, technical accuracy, and sensible measurement is what makes the difference. It helps you protect visitor choice while keeping enough reliable data to improve marketing performance.

Frequently Asked Questions

Does Consent Mode V2 Make A Website GDPR Compliant?

No. It helps Google tags respond to consent choices, but compliance also depends on your banner, privacy information, data purposes, records, and wider tracking controls.

Is Google Consent Mode V2 Only For Google Analytics?

No. It also affects Google Ads, conversion tracking, remarketing, personalised advertising, and other Google measurement features.

Can I Use Google Analytics In The UK Without Consent?

It depends on the exact setup, purpose, data processing, and whether a valid exception applies. The 2025 Act introduced some statistical purpose exceptions, but they are conditional and should be checked carefully.

What Happens If A Visitor Rejects Cookies?

Google tags should adjust according to the denied consent signals. Depending on the setup, cookies may not be set, and limited signals may be used for aggregate measurement or modelling.

Does Consent Mode Control Every Website Tag?

No. It mainly communicates consent choices to Google tags, so other scripts and marketing pixels need their own consent controls or compatible integrations.

Latest News