Google Consent Mode V2 Explained: What You Actually Need to Do

What Consent Mode Actually Is

Consent Mode is Google's system for adjusting how their tags behave based on user consent choices.

When someone visits your site and declines tracking cookies, Consent Mode tells Google tags to:

• Not set or read cookies
• Not send identifiable data
• Optionally send anonymised pings for modelling

It's a bridge between your consent management platform (the cookie banner) and Google's advertising and analytics products.

Version 2, required since March 2024 for EU/UK advertisers, added two new consent signals that Google uses for more granular control over data collection.

Why This Matters Now

If you run Google Ads campaigns targeting the UK or EU and you still haven't implemented Consent Mode V2, you're likely:

• Losing audience data for remarketing
• Seeing incomplete conversion tracking
• Facing ad serving restrictions

Google requires Consent Mode for using audience features (remarketing, Customer Match) in the European Economic Area. Without it, your remarketing lists stop building.

This isn't a future concern. It's been the reality for two years now.

The Two Implementation Modes

Consent Mode has two levels:

Basic Mode

When users deny consent, Google tags simply don't fire. No data collection happens.

This is easier to implement because it's essentially what most consent banners already do. You're just adding the formal consent signals.

Pros: Simple, clear privacy stance, minimal implementation.

Cons: You lose all data from users who decline consent. No modelling to fill gaps.

Advanced Mode

When users deny consent, Google tags still fire but with adjusted behaviour:

• No cookies set or read
• No identifiable information collected
• Anonymous pings sent for conversion modelling

Google uses these anonymised signals to model conversions and audiences for the users who declined full tracking. If you want measurement that holds up even as cookies and consent tighten, pair this with server-side tracking.

Pros: Recovers some data through modelling, better measurement accuracy.

Cons: More complex implementation, some privacy advocates question sending any data without explicit consent.

What the New V2 Signals Mean

Version 2 added two new consent parameters:

ad_user_data: Controls whether data can be sent to Google for advertising purposes.

ad_personalization: Controls whether data can be used for remarketing and personalised ads.

Previously, you only had:

analytics_storage: Controls GA4 cookies

ad_storage: Controls advertising cookies

You now need to send all four signals based on user consent choices.

How to Implement It

Here's the practical path to implementation:

Step 1: Check Your Current Consent Banner

Most modern Consent Management Platforms (CMPs) now support Consent Mode V2 natively:

• Cookiebot
• OneTrust
• Usercentrics
• Termly
• CookieYes
• Complianz

If you're using one of these, check their documentation for enabling Consent Mode V2. It's usually a configuration option.

If you're using a custom solution, you'll need to implement the consent signals yourself through Google Tag Manager.

Step 2: Configure GTM for Consent Mode

In Google Tag Manager:

1. Go to Admin → Container Settings
2. Enable "Consent Overview" under Additional Settings
3. Configure default consent states

For EU/UK visitors, defaults should be:

• ad_storage: denied
• analytics_storage: denied
• ad_user_data: denied
• ad_personalization: denied

These defaults apply before the user makes a choice.

Step 3: Connect Your CMP

Your consent banner needs to update these consent states when users make choices.

Most CMPs handle this automatically once you enable their Consent Mode integration. They fire the necessary consent update commands when users accept or decline.

If implementing manually, you need to push consent updates to the dataLayer.

When consent is granted, your CMP pushes an update changing the relevant parameters from "denied" to "granted."

Step 4: Configure Tag Consent Settings

In GTM, each tag has consent settings. Configure them to:

• Require ad_storage and ad_user_data for advertising tags
• Require analytics_storage for GA4

This ensures tags only fire fully when appropriate consent is granted.

Step 5: Test Thoroughly

Testing consent implementations is tricky because you need to:

• Clear cookies between tests
• Test different consent choices
• Verify tags fire or don't fire appropriately
• Confirm consent signals are being received by Google

Use Google Tag Assistant and check your GA4 DebugView to verify correct behaviour.

Basic vs Advanced: Which Should You Choose?

Choose Basic if:

• You want the simplest implementation
• Your legal/compliance team prefers zero data collection without explicit consent
• You have enough consenting users for adequate measurement
• You're comfortable with some data loss

Choose Advanced if:

• You want Google's modelling to fill measurement gaps
• You need remarketing audiences from users who haven't explicitly opted in
• You have high rates of consent decline
• You're willing to accept the complexity

Advanced mode is where Google's marketing is pushing. But basic mode is perfectly compliant and may align better with your organisation's privacy philosophy.

What Happens If You Don't Implement It

Without Consent Mode V2:

Now: Your remarketing lists aren't being built for EU/UK users. Your conversion measurement is incomplete.

Soon: Google may restrict your access to audience features entirely in the EEA.

Eventually: Your ability to run effective advertising in these regions is significantly hampered.

This isn't theoretical. Google has explicitly stated Consent Mode is required for EEA audience features.

Common Implementation Mistakes

Default Consent Set to Granted

Some implementations accidentally default all consent to "granted" before the user interacts. This means you're tracking users before they've given consent, defeating the whole purpose.

Defaults for EU/UK users must be "denied" for all consent types.

CMP Not Actually Sending Signals

Having a consent banner isn't the same as having Consent Mode. The banner needs to actually communicate consent choices to Google tags.

Test by declining consent and checking if Google tags fire. If they do (and you're on basic mode), something's wrong.

Not Updating for V2

Many sites implemented Consent Mode V1 and never updated. The newer ad_user_data and ad_personalization signals are required for V2 compliance.

Check that your consent updates include all four parameters.

Testing Only Accept Scenarios

It's easy to test the happy path (user accepts, everything works). But you also need to test decline scenarios to verify tags aren't firing when they shouldn't be.

The Practical Timeline

If you haven't implemented Consent Mode V2 yet:

This week: Check if your CMP supports it and enable the integration.

Next week: Configure GTM and test consent behaviour.

Following week: Verify everything is working in production.

This isn't a complex multi-month project. For most sites, it's a few hours of focused work.

But every day you delay is a day of lost remarketing data and incomplete measurement.

Beyond Compliance

Consent Mode isn't just about ticking boxes. Implemented properly, it:

• Gives you accurate measurement despite privacy restrictions
• Maintains user trust through transparent consent
• Future-proofs your setup for evolving regulations
• Enables advanced features that require consent signals

The organisations that implement consent infrastructure well have measurement advantages over those who treat it as a grudging compliance exercise. It also sets you up for a stronger first-party data strategy as third-party signals keep fading.

What to Do Now

1. Check your current consent banner's Consent Mode status
2. Verify you're sending V2 signals (all four parameters)
3. Test both accept and decline scenarios
4. Monitor your audience lists to confirm they're building

This is table stakes for EU/UK advertising now. Get it done.