Google Consent Mode v2: Four Signals, Basic vs Advanced Mode

Your cookie banner is being questioned and your tags are in the spotlight. Here's what Google Consent Mode v2 does, how basic and advanced mode differ and where Google's own pages contradict each other.

Ömer S. Ekinci
CEO, Oxford Impulse
Published
6 min read

If someone has asked whether your cookie banner actually controls your Google tags and you’re not sure what to say, Google Consent Mode v2 is the piece to understand. It’s a way of telling Google’s tags what your visitor agreed to, so the tags can adjust what they collect.

The short answer

Google Consent Mode v2 is a set of consent signals your site passes to Google tags. Each signal is either granted or denied, and the tags change their behaviour to match[1]. In basic mode, tags stay blocked until the visitor acts on your banner. In advanced mode, tags load straight away with default settings, send cookieless pings while consent is denied, and send full data only after consent is given[1]. This is an explainer built on Google’s own documentation, not legal advice. If you need to know what the law requires of your shop, ask a qualified adviser.

Consent mode works through consent types. Four are the main signals[1]:

  • ad_storage: whether advertising cookies and identifiers can be used.
  • analytics_storage: whether analytics data can be stored and used.
  • ad_user_data: whether user data can be sent to Google for advertising purposes.
  • ad_personalization: whether personalised advertising is allowed.

Every type has two states: granted or denied[1]. There are also three further types: functionality_storage, personalization_storage and security_storage[1]. Check Google’s developer page for what each of those covers.

The last two of the main four, ad_user_data and ad_personalization, are the “v2” part. Google added them in November 2023 and ties them to traffic from the European Economic Area (EEA) and its EU user consent policy[2]. If your setup only ever passed ad_storage and analytics_storage, it doesn’t include the two newer signals.

Consent mode is not a banner

This catches people out. Consent mode doesn’t show anything to your visitors. It works alongside your own banner or a consent management platform (CMP, the tool that displays the banner and records the choice), which passes the visitor’s decision to your Google tags[3]. No banner means no choice to pass on. A banner that doesn’t talk to your tags means no signal is sent.

Tip

Test the connection, not just the banner. Accept and refuse on your own site, then check that your tags receive the matching granted or denied values.

Basic and advanced mode

Both modes use the same signals. The difference is when your Google tags load and what they’re allowed to send beforehand.

Basic mode

In basic mode, Google tags are blocked until the visitor interacts with the banner. If they refuse consent, nothing is sent to Google[1]. If they accept, the tags load and run with the granted settings. It’s the simpler model to explain: no choice, no tag, no data.

The catch is what you lose. Google’s help page says that if a self-maintained banner blocks Google tags until the visitor interacts, you may lose data[4]. That’s the trade you’re making with basic mode. For visitors who refuse, nothing is sent[1].

Advanced mode

In advanced mode, the tags load when the page opens, with default consent values already set. While consent is denied, they send cookieless pings. These are small signals that don’t rely on cookies. Full data is sent only after the visitor consents[1].

Think of it as the tag being present but restrained. What it’s allowed to send depends on the state of the signals.

Watch out

Advanced mode doesn’t make a banner optional. The defaults you set, and the way your banner updates them, still decide what the tags do. A badly configured default is a configuration problem, whichever mode you pick.

Neither of the Google pages we’re drawing on says basic mode is non-compliant or that advanced mode is mandatory, and we won’t claim either. They describe two behaviours with different consequences for your data.

Who the policy covers

Consent mode is a tool. The rules sit in Google’s EU user consent policy. It names the EEA, the UK and Switzerland[5]. Under it, you’re asked to make sure of four things[5]:

  • You obtain valid consent from end users.
  • You disclose the parties involved in collecting and using data.
  • You keep records of consent.
  • You give users steps to revoke their consent.

That list is worth reading against your banner. Does it name the parties? Is there a way for visitors to revoke consent? Can you show a record of what each person chose? Those are questions about your banner and CMP, not about Google tags, and consent mode won’t answer them for you.

Google’s Ads Help page on the v2 update frames the new signals around EEA traffic[2]. The policy itself names a wider list of places[5]. Whether the policy applies to your particular shop is a question for your adviser.

What Merchant Center says

If you run Shopping ads, there’s a separate line in the Google Merchant Center Help page on data collection and use. Using Shopping ads (not free listings), remarketing or conversion tracking without consent from users in the EEA or the UK breaks policy[6]. That page names the EEA and the UK, so don’t read Switzerland into it.

The practical point is that consent affects your advertising features, not just your analytics. For the Google side of conversion tracking, our walkthrough of enhanced conversions for web at https://oxfordimpulse.com/enhanced-conversions-for-web-setup/ covers the setup.

Where the pages contradict each other

Google’s own pages don’t agree on one detail of advanced mode: what happens by default. The Ads Help page[3] and the developer overview[1] describe the advanced-mode default differently. We’re not going to pick one and present it as settled, because we can’t tell from the pages which is current.

What to do about it:

  • Don’t assume a default. Set your defaults explicitly in your tag setup or CMP, for each consent type.
  • Check what your tags actually send before consent. Open your browser’s developer tools, load the page without touching the banner and look at the requests going to Google.
  • Check the same thing after refusing, and again after accepting.
  • Write down which page you relied on when you configured it, and the date, so you can revisit it when Google updates its documentation.

There’s a second point worth noting. Google’s Ads Help guidance says that if you run personalised ads, self-maintained banners should implement consent mode v2[4]. The same page warns that blocking tags until interaction may cause data loss[4]. So the choice between a stricter setup and a fuller set of data is one to make deliberately, with your adviser.

FAQs

What is Google Consent Mode v2?

It’s the current version of Google’s consent signalling system. Your site tells Google tags whether a visitor has granted or denied each consent type, and the tags adjust what they collect[1]. Version 2 added ad_user_data and ad_personalization in November 2023[2].

Does consent mode give me a cookie banner?

No. Consent mode doesn’t display anything to visitors. You need your own banner or a consent management platform, which passes the visitor’s choice to your Google tags[3].

What’s the difference between basic and advanced consent mode?

In basic mode, Google tags are blocked until the visitor acts on the banner, and nothing is sent if they refuse[1]. In advanced mode, tags load on page open with defaults set, send cookieless pings while consent is denied, and send full data only after consent[1].

Is basic mode against Google’s rules?

The pages we’ve relied on don’t say so. They do note that blocking Google tags until a visitor interacts may cause data loss[4]. That’s a data trade-off, not a policy verdict.

Do I have to use advanced mode?

Nothing in these Google pages says advanced mode is mandatory. They describe it as one of two ways consent mode can behave[1]. Choose based on how you want tags to behave before consent and on advice from someone qualified.

What do ad_user_data and ad_personalization do?

ad_user_data covers whether user data can be sent to Google for advertising. ad_personalization covers whether personalised ads are allowed[1]. Both were added in November 2023 and are tied to EEA traffic and the EU user consent policy[2].

Which countries does the EU user consent policy name?

It names the EEA, the UK and Switzerland[5]. The Merchant Center page on data use names the EEA and the UK for Shopping ads, remarketing and conversion tracking[6].

What are the other consent types besides the four main signals?

Google lists functionality_storage, personalization_storage and security_storage as further types[1]. Like the main four, each is either granted or denied.

Where to go from here

Start by listing your banner or CMP, your current defaults for all four signals and what your tags send before and after consent. Fix any gaps you find, then recheck after your next tag change. If you want a second pair of eyes on how consent fits with your campaigns, our Google Ads page at https://oxfordimpulse.com/google-ads/ explains how we work.

Sources

Share this article

Written by

Ömer S. Ekinci

CEO, Oxford Impulse Google Partner

Ömer S. Ekinci is the director of Oxford Impulse, a London-based Google Partner agency. He works hands-on in Google Ads, Meta Ads and Google Merchant Center accounts for e-commerce, healthcare and B2B brands across the UK, Europe and the US.

Free audit

Want a second pair of eyes?

Get a free audit and a clear list of what to fix first.

Get a free audit
0% read 6 min left

Google Consent Mode v2: Four Signals, Basic vs Advanced Mode

Get a free audit