Google Consent Mode v2 Explained: A Practical Guide for UK and EU Businesses

If your website serves visitors in the UK or the EU and you advertise on Google, Consent Mode v2 is no longer optional plumbing. It is the mechanism that tells Google’s tags what each visitor agreed to — and it directly affects your conversion data, your remarketing audiences and how well Google Ads can bid. Yet it is also one of the most frequently misconfigured parts of a tracking setup.

What is Google Consent Mode v2?

Consent Mode is a way for your cookie banner (your consent management platform, or CMP) to pass the visitor’s choices to Google tags — GA4, Google Ads, Floodlight. The tags then adjust their behaviour: with consent they work normally; without it they do not set advertising or analytics cookies.

Version 2 added two signals to the original two. The four Google consent types are:

Parameter	What it controls
ad_storage	Storage (e.g. cookies) for advertising
analytics_storage	Storage for analytics, such as GA4 visit cookies
ad_user_data	Consent to send user data to Google for advertising purposes (new in v2)
ad_personalization	Consent for personalised advertising, such as remarketing (new in v2)

Each has two states: granted or denied. Your setup sends a default state when the page loads and an update when the visitor makes a choice.

Why Google Ads needs Consent Mode v2

Since March 2024, Google has required advertisers to pass ad_user_data and ad_personalization signals for users in the European Economic Area, in line with its EU user consent policy, which also covers the UK. Without valid consent signals:

• Remarketing and audience lists stop growing for EEA and UK users.
• Conversion measurement loses visibility, because tags cannot observe users who declined or never answered.
• Smart Bidding gets fewer signals, so bidding becomes less accurate for exactly the leads you pay most for.

For a B2B or high-ticket business, where each conversion carries a lot of weight, losing part of that signal can make campaigns look worse than they are and push bidding in the wrong direction. If you run paid search, it belongs in the same conversation as your Google Ads and Meta Ads management.

Basic vs advanced Consent Mode

This is the decision that matters most.

Basic Consent Mode

• Google tags are blocked completely until the visitor interacts with the banner.
• If they accept, tags load and fire normally. If they decline or ignore the banner, nothing is sent to Google.
• Google Ads can still apply a general conversion model, but it is less tailored to your site.

Advanced Consent Mode

• Google tags load immediately with consent defaulted to denied.
• While consent is denied, tags send cookieless pings — basic, non-identifying signals that an event happened, without reading or writing cookies.
• When the visitor accepts, tags switch to full measurement.
• Google can use those pings for conversion modelling specific to your account, and GA4 can apply behavioural modelling to estimate the missing data, once your property meets Google’s eligibility thresholds.

Which one should you choose?

	Basic	Advanced
Data sent before consent	None	Cookieless pings
Modelling quality	General model	Site-specific modelling
GA4 behavioural modelling	Not available	Available if eligible
Legal caution	Lower	Requires a considered decision

Advanced mode gives better data. Some regulators and lawyers, however, take the view that even cookieless pings involve accessing the device or processing personal data such as IP addresses, so they need a legal basis of their own. Make this decision with whoever is responsible for data protection in your organisation, document it, and configure accordingly.

How Consent Mode relates to GDPR, UK GDPR and cookie banners

A common misunderstanding: Consent Mode does not make you compliant. It is a technical signal, not a legal basis.

• In the UK, UK GDPR and PECR govern personal data and cookies, with ICO guidance setting expectations for banners. The Data (Use and Access) Act 2025 relaxes consent for certain low-risk analytics cookies under conditions, but advertising cookies still require consent.
• In the EU, GDPR plus each country’s ePrivacy rules apply, with national regulators issuing their own cookie guidance.

You still need a cookie banner that:

• asks before non-essential cookies are set,
• makes rejecting as easy as accepting,
• explains purposes in plain language,
• records and respects the choice, and lets visitors change it later.

Consent Mode then carries that choice to Google’s tags. It does nothing for non-Google tags such as the Meta Pixel or LinkedIn Insight Tag — those must be blocked by your CMP or Tag Manager until consent is given.

How to implement Consent Mode v2

1. Choose a CMP that supports Consent Mode v2 natively. Google recommends a Google-certified CMP; check that it sends all four parameters.
2. Set defaults before any tag fires. In Google Tag Manager, use the Consent Initialization – All Pages trigger. Default to denied for UK and EEA visitors (you can set regional defaults).
3. Send an update on choice. The CMP sends granted or denied for each type when the visitor chooses, and on later page loads.
4. Configure non-Google tags with GTM’s consent checks (“additional consent required”) so they only fire after the relevant consent.
5. Consider ads_data_redaction and url_passthrough for better measurement in a denied state.
6. Test in Tag Assistant’s Consent view: page load (default), accept, reject, and a return visit.

Done properly, this sits inside a wider Google Analytics and Tag Manager setup.

Common Consent Mode v2 mistakes

In audits we often see:

• Tags firing before the default is set, because the CMP loads late or the default uses a normal page view trigger.
• Defaults set to granted for everyone, which defeats the purpose and creates legal risk.
• Only the two original parameters being sent, because an old CMP version was never updated.
• GA4 hard-coded in the theme alongside GTM, so one copy ignores consent entirely.
• A banner without a clear “Reject” button, or with pre-ticked boxes.
• Meta and LinkedIn pixels firing regardless of choice, on the assumption that Consent Mode covers them.
• Nobody re-testing after a website or CMP update.

Consent Mode v2 checklist

• CMP supports Consent Mode v2 and sends all four parameters
• Default consent set on Consent Initialization, before any tag
• Defaults are denied for UK and EEA visitors
• Updates fire on accept, reject and return visits
• Basic vs advanced mode chosen deliberately and documented
• Non-Google tags blocked until consent
• “Reject” as easy as “Accept”; preferences can be changed later
• Consent status checked in Google Ads diagnostics and GA4 Admin
• Retested after every site or CMP change

Key takeaways

• Consent Mode v2 passes four consent signals to Google tags; ad_user_data and ad_personalization are required for EEA and UK ad personalisation and measurement.
• Basic mode sends nothing before consent; advanced mode sends cookieless pings and enables better modelling.
• It is a technical layer, not compliance — you still need a lawful, well-designed cookie banner.
• Most problems come from timing, outdated CMPs and non-Google tags left unmanaged.

If you are not sure your consent setup is doing what you think, get in touch.