Home › Guides › consent mode v2
Consent Mode v2 Explained for Small Businesses
What Google's Consent Mode v2 is, why it matters for UK and EU visitors, basic versus advanced mode, and how small businesses can set it up and test it.
Quick answer
Consent mode v2 is Google's system for adjusting Google tags to each visitor's cookie choice. It uses four signals, including ad_user_data and ad_personalization, and is needed to keep using Google Ads audiences and measurement for visitors in the UK and EEA. Set it up through a certified cookie banner and test it.
Key takeaways
- Consent mode v2 lets Google tags respect each visitor's cookie choice.
- It adds two signals: ad_user_data and ad_personalization.
- It is needed for Google Ads audiences and measurement for UK and EEA visitors.
- Advanced mode sends cookieless pings before consent; basic mode sends nothing until consent.
- Your cookie banner must set the signals correctly, so always test it.
If you run Google Ads or use Google Analytics 4 with visitors from the UK or Europe, you have probably heard of consent mode v2. It sounds technical, but the idea is simple: your Google tags should respect each visitor's cookie choice, and Google needs to know what that choice was.
This guide explains what consent mode v2 is, why it matters and how to set it up and test it.
What is consent mode?
Consent mode is a Google feature that adjusts how Google tags behave based on a visitor's cookie consent. If a visitor accepts, tags work normally. If they decline, tags limit what they do.

It does not decide whether you need consent. It passes your visitor's choice from your cookie banner to Google's tags.
What changed in version 2?
Version 2 added two new signals to the original two:
- ad_storage: can advertising cookies be stored?
- analytics_storage: can analytics cookies be stored?
- ad_user_data: can user data be sent to Google for advertising? (new)
- ad_personalization: can data be used for personalised advertising, such as remarketing? (new)
Google requires these signals for advertisers who want to keep using audience and measurement features for users in the UK and the European Economic Area.
Why does it matter?
Without it, you risk:
- Losing remarketing audiences for UK and EEA visitors
- Weaker conversion measurement, so campaigns optimise on less data
- Compliance problems, if tags fire before consent
With it, you stay compliant and still get modelled conversions for visitors who decline cookies, which helps your campaigns perform.
Basic vs advanced mode
There are two ways to implement consent mode:
Basic mode: Google tags do not load at all until the visitor makes a choice. If they decline, Google receives nothing. Simple and privacy-focused, but Google has less data for modelling.
Advanced mode: Google tags load straight away with consent set to "denied". They send cookieless pings without identifiers. If the visitor accepts, tags switch to full tracking. Google uses the cookieless pings to model conversions from people who declined.
Advanced mode usually gives better data for ads. Basic mode is simpler and more conservative. Choose based on your privacy approach and your advisers' view.
How to set it up
1. Choose a consent management platform (CMP). Pick a cookie banner that supports the latest version. Many website platforms include one, and Google lists certified CMPs.

2. Set the default consent state. Before the banner appears, set all four signals to "denied" for UK and EEA visitors. This must happen before any Google tags load.
3. Update consent on choice. When the visitor accepts or rejects, your CMP sends a consent update with the new values.
4. Configure your tags. In Google Tag Manager, check each tag's consent settings so it only fires with the right consent. Google tags handle consent mode automatically; other tags, such as the Meta Pixel, need consent triggers.
5. Turn on the consent overview in GTM to see which tags need which consent.
Our GTM container generator builds a container with consent settings already in place.
How to test it
Testing is essential. A banner that looks fine can still let tags fire too early.
- Open your site in a private window and use Google Tag Assistant
- Check the default state is "denied" before you click anything
- Reject cookies and confirm tags do not set cookies
- Accept cookies and confirm the update changes all four signals to "granted"
- Check GA4 and Google Ads diagnostics for consent status
Our Tracking Inspector shows which tags fire on a page before and after consent.
What about other platforms?
Consent mode is Google's system, but the same principle applies to Meta, Microsoft and others. Tags for these platforms should only fire, or fire in a limited way, after consent. Configure their triggers in GTM to respect your banner's choices. Microsoft has its own consent mode for UET, which your CMP may support.
Consent mode and server-side tracking
Server-side tracking does not remove the need for consent. Your server tags should read the same consent signals and behave accordingly. Our guide to server side tracking explains how the two fit together.
Common mistakes
- Tags firing before the default consent is set, often because of hard-coded tags outside GTM
- Missing the two new signals, ad_user_data and ad_personalization
- A banner that does not update consent when the visitor clicks accept
- Non-Google tags ignoring consent entirely
- Never testing after website changes
Regions and defaults
You can set different default consent states by region. Many businesses set everything to "denied" for visitors in the UK and EEA, where consent is required, and use the rules that apply elsewhere for other visitors. Ask your adviser what suits your business, set the defaults in your CMP or GTM and document the decision.

Keeping records
Regulators such as the ICO expect you to be able to show how you collect consent. Keep a note of your banner settings, your consent mode setup and when you last tested it. Many CMPs keep consent logs for you.
Will your numbers change?
Often, yes. When consent mode is set up correctly, GA4 may show fewer users and events from visitors who declined, while Google Ads shows modelled conversions alongside observed ones. This is normal. Explain it to anyone who reads your reports so a drop in numbers is not mistaken for a drop in business.
What to do next
Check your current cookie banner supports consent mode v2, confirm all four signals are set by default and updated on choice, and test the result with Tag Assistant. A correct consent mode v2 setup keeps you compliant and protects the data your ads depend on.
Want Claude to do more of this for you? Lead Focus has 30 Claude Skills that install in a minute and draft the work for you to check.
Questions and answers
Is consent mode v2 required?
For advertisers targeting users in the UK and the European Economic Area, Google requires consent signals to keep using features such as remarketing audiences and some measurement. If you only have visitors elsewhere, it is still good practice.
What is the difference between basic and advanced consent mode?
In basic mode, Google tags do not load until the visitor consents. In advanced mode, tags load with consent denied and send cookieless pings, which Google uses for conversion modelling.
Does consent mode replace a cookie banner?
No. Consent mode works with your cookie banner. The banner collects the visitor's choice, and consent mode passes that choice to Google tags.
Which cookie banner should I use?
Use a consent management platform that supports consent mode v2, ideally one certified by Google. Many website platforms offer one built in.
How do I check consent mode is working?
Use Google Tag Assistant or GTM preview to check the default consent state before a visitor chooses and the update after they accept or reject. Check that tags behave as expected in each case.