Google Consent Mode v2: What UK Small Businesses Need to Know (2026)
Short answer: If you run Google Ads or GA4 in the UK, you need it
Consent Mode v2 is how your website tells Google whether each visitor has agreed to cookies, so your tags behave lawfully. It's required for UK and EEA traffic if you use Google Ads, GA4 or Google's marketing tools. Without it, you lose remarketing, conversion data and a big slice of measurable results.
Cookie banners are nothing new, but how they connect to your analytics and advertising has changed. Google Consent Mode v2 is the bridge between a visitor's cookie choice and what your Google tags are allowed to do. For UK small businesses running any Google marketing, it's gone from "nice to have" to "must have". This guide explains it in plain English.
Note: this article is general guidance, not legal advice. For how UK GDPR and PECR apply to your specific business, check the ICO's guidance or speak to a data-protection professional.
What Is Google Consent Mode v2?
Consent Mode is a way for your website to communicate a visitor's consent choices to Google's tags (such as Google Analytics 4 and Google Ads) in real time. When someone interacts with your cookie banner, Consent Mode passes that decision along, and Google's tags adjust their behaviour accordingly — collecting data when consent is granted and holding back when it isn't.
The "v2" update, which became the required version for advertisers using Google's services in the UK and EEA in 2024, added two new signals specifically about advertising data and personalisation. It exists so that the data Google receives lines up with what each visitor has actually agreed to.
Why It Matters for UK Businesses
There are two reasons it matters, and they pull in the same direction:
1. Compliance with UK privacy law
Under UK GDPR and the Privacy and Electronic Communications Regulations (PECR), you generally need a visitor's consent before setting non-essential cookies for analytics and advertising. Consent Mode v2 is Google's mechanism for honouring those choices in your Google tags. It doesn't replace your legal obligations or your cookie banner — it's the plumbing that makes your tags respect them.
2. Keeping your measurement and advertising working
Google requires Consent Mode v2 to continue using features like remarketing audiences and conversion data from UK and EEA visitors. Without it, those features are switched off for that traffic — which quietly degrades everything from your audience sizes to your conversion reporting.
The Four Consent Signals
Consent Mode v2 works through four parameters, each set to "granted" or "denied" based on the visitor's choice. Two existed in v1; two are new in v2.
| Signal | What It Controls | Version |
|---|---|---|
| analytics_storage | Storage of analytics cookies (e.g. GA4 measurement) | v1 |
| ad_storage | Storage of advertising-related cookies | v1 |
| ad_user_data | Consent to send personal data to Google for advertising | New in v2 |
| ad_personalization | Consent for personalised advertising and remarketing | New in v2 |
Basic vs Advanced Consent Mode
There are two ways to implement Consent Mode, and the difference affects how much data you recover:
| Basic | Advanced | |
|---|---|---|
| When tags load | Only after consent is granted | Tags load but adjust behaviour by consent state |
| Data when consent denied | Nothing is sent | Anonymous, cookieless "pings" are sent |
| Conversion modelling | Limited | Google can model gaps from the pings, recovering more data |
| Best for | Simplicity and a stricter privacy stance | Maximising measurable conversions while respecting consent |
Advanced mode typically recovers more usable data because Google can statistically model the behaviour of users who declined cookies, without storing their personal data. Which is right for you depends on your priorities and your interpretation of your obligations — another reason to confirm the approach with a privacy professional.
What Happens If You Don't Set It Up?
Skipping Consent Mode v2 doesn't just risk a compliance headache — it quietly damages your marketing data:
- Your Google tags stop collecting data on UK and EEA visitors, which means no remarketing, no conversion modelling and shrinking advertising audiences.
- You lose measurable conversions. Properties that haven't implemented it can lose a significant share — commonly cited at anywhere from roughly 15% to 40% — of measurable conversions in affected regions.
- The lost data doesn't come back. It isn't retroactively backfilled, so every week without it is a week of decisions made on incomplete numbers.
- Smart Bidding gets worse signals. Automated bidding relies on conversion data; starve it and performance drifts.
How to Implement Consent Mode v2
The setup has a few moving parts, but the path is well-trodden:
- Choose a consent management platform (CMP). In 2026 Google expects consent signals to come from a recognised CMP. Many cookie-banner tools integrate with Google's consent framework out of the box.
- Install and configure your cookie banner so visitors can genuinely accept or reject analytics and advertising cookies (no pre-ticked boxes).
- Connect the CMP to Consent Mode so each choice sets the four signals correctly — ideally via Google Tag Manager for clean, central control.
- Set sensible defaults (typically "denied" until the visitor consents) and update them the moment a choice is made.
- Decide between Basic and Advanced implementation based on your priorities and obligations.
- Test thoroughly. Use Google Tag Manager's preview mode and GA4's consent settings checks to confirm the signals fire correctly for accept, reject and no-choice states.
If you've already set up GA4, this is a natural next step — see our GA4 setup guide for the foundations.
Common Mistakes to Avoid
- Assuming your old cookie banner is enough. A banner that doesn't pass the four v2 signals to Google leaves you non-compliant and losing data.
- Pre-ticking consent or using "implied" consent. Consent must be a genuine, active choice — this is a common compliance failure.
- Setting it and never testing. Misconfigured signals can silently block all data or, worse, send data without consent.
- Forgetting the reject path. Test what happens when a visitor declines, not just when they accept.
- Treating it as purely technical. The legal side matters too — align your setup with your privacy policy and obligations.
Frequently Asked Questions
Is Consent Mode v2 a legal requirement?
It's Google's technical requirement for using its advertising and measurement features with UK and EEA traffic. Your underlying legal duty comes from UK GDPR and PECR, which require consent for non-essential cookies. Consent Mode v2 is how your Google tags honour that — but always check your specific obligations with the ICO or a professional.
Do I need it if I only use Google Analytics, not Google Ads?
If you serve UK or EEA visitors and use GA4, you should still implement Consent Mode so analytics cookies are only used with consent and your data collection is lawful. It becomes especially important the moment you add any advertising or remarketing.
Will I lose all my data if visitors reject cookies?
Not necessarily. With Advanced implementation, Google can send anonymous, cookieless pings and statistically model some of the missing behaviour — recovering data you'd otherwise lose entirely, without storing personal data of users who declined.
Do I need a paid cookie banner tool?
You need a consent management platform that integrates properly with Google's consent framework. Some are free for small sites; others are paid. The key is that it reliably passes all four v2 signals — not the price tag.
How do I know it's working?
Use Google Tag Manager's preview mode and GA4's consent diagnostics to confirm the four signals fire correctly for accept, reject and no-choice scenarios. If you're unsure, a developer can verify it in well under an hour.
Want Consent Mode v2 set up correctly?
We'll configure your cookie banner, CMP and Google tags so you stay compliant and stop losing conversion data. Explore analytics & tracking services → or get in touch.
