Is Google Consent Mode V2 legally required, or just recommended by Google?

Consent Mode V2 itself is Google's technical requirement for continued access to full GA4 and Google Ads functionality for EEA/UK traffic, so it isn't a law in itself. The underlying obligation to obtain valid consent before setting non-essential cookies comes from GDPR and the ePrivacy Directive, which are legally binding across the EEA and UK.

What happens if I don't implement Consent Mode V2?

Google has stated that without valid consent signals, GA4 and Google Ads may stop processing data for EEA users, and conversion modelling won't be available to fill the gap. In practice, this means blind spots in reporting and reduced ad optimization performance for that traffic.

Do I need Advanced Consent Mode, or is Basic enough?

Basic mode is compliant on its own, but it means zero data for anyone who hasn't consented yet or declines. If ad performance and modelled conversions matter to your business, Advanced mode is generally worth the extra setup.

Can I use Google Consent Mode without Google Tag Manager?

Yes, you can implement it by editing your site's tagging snippet directly, but GTM makes ongoing changes and testing dramatically easier, especially once you have more than a couple of Google tags on the site.

How to Implement Cookie Consent V2 Effectively

Illustration of Cookie Consent V2 implementation

If you run an online rental store or any other website that relies on Google Analytics and Google Ads to grow, you’ve almost certainly bumped into a deadline you can’t ignore: Google Consent Mode V2. Sites that don’t pass valid consent signals to Google now risk losing measurement and ad personalization for EEA visitors entirely, with no fallback data to soften the blow.

This guide walks through what Consent Mode V2 actually does, how to choose a Consent Management Platform (CMP), how to wire it up through Google Tag Manager, and how to test that it’s working, so that GDPR compliance and user trust are built in from the start rather than bolted on afterward.

“Consent shouldn’t be treated as a legal checkbox you tick once and forget. Every rental business we work with collects payment details, ID checks, and booking history. Cookie consent is the same trust relationship, just applied to tracking. Get it right and customers actually notice the difference.” — Asgeir Helland, Product Expert at Sharefox

What is Google Consent Mode?

Google Consent Mode is a framework that lets your website adjust how Google tags behave based on the consent choices a visitor makes. It sits between your cookie consent banner (or CMP) and Google services like Google Analytics 4 (GA4) and Google Ads. When someone accepts or declines cookies, Consent Mode passes that decision to Google’s tags in real time, so those tags only fire, or fire in a limited “cookieless” form, according to what the visitor actually agreed to.

Key features of Consent Mode V2

Version 2 introduced two new consent parameters covering ad personalization and user data for advertising, building on the original signals that governed ad storage and analytics storage. This split gives Google, and you, more precise control over what kind of data can be used and how, which matters most for advertisers operating under GDPR and the ePrivacy Directive.

Consent Mode V2 comes in two flavours. Basic Consent Mode simply holds Google tags back from loading at all until consent is granted, which is simple to set up but means you lose all measurement for users who haven’t yet responded or who decline. Advanced Consent Mode instead lets tags load in a consent-aware, cookieless state that sends anonymous “pings” even without consent, and Google then uses conversion modelling to estimate the gap, recovering a meaningful share of otherwise-lost conversion data.

Benefits of using Consent Mode

For a subscription or e-commerce business, the practical upside is straightforward: you stay compliant with GDPR-style consent requirements while keeping your GA4 and Google Ads reporting usable. Advanced mode in particular means a declined-cookie visitor doesn’t just vanish from your funnel. Modelled conversions keep your ROAS and CAC numbers grounded in something closer to reality.

Choosing the right CMP for your website

What is a CMP?

A Consent Management Platform, or CMP, is the software that displays your cookie banner, records each visitor’s choices, and communicates those choices as machine-readable signals to the rest of your stack, including Google Consent Mode. It’s also your audit trail if a regulator ever asks how you obtained consent.

Comparing CMP options

There’s no single “best” CMP. It depends on your CMS, your budget, and how granular your consent categories need to be. Here’s how three widely used, independent options stack up on the criteria that matter most for a Consent Mode V2 implementation:

Criteria	OneTrust	Cookiebot	Complianz
Built-in Consent Mode V2 support	Yes, native	Yes, native	Yes, native (WordPress-focused)
Automatic cookie scanning	Yes	Yes	Yes
Google Tag Manager integration	Native template	Native template	Via GTM template or direct plugin hook
Pricing model	Custom / enterprise tiers	Tiered by monthly page views	One-time or annual licence (freemium tier available)
Ease of self-service setup	Moderate, more configuration involved	High	High
Best fit	Enterprise, multi-brand, multi-region sites	Mid-market sites wanting fast setup	WordPress / WooCommerce sites

Table compiled from each vendor’s publicly documented Consent Mode integration guides. Confirm current tiers directly with each vendor before purchasing, as pricing changes frequently.

How to select a CMP for your needs

When comparing options, it helps to weigh a few practical questions. Does the CMP ship a ready-made GTM template, or will your developer need to hand-code the integration? Can visitors accept analytics cookies but decline ad personalization separately? Does the vendor push updates automatically when Google or regulators change requirements, or is that left to you? And can you export consent-rate data to see what percentage of visitors are actually opting in?

Step-by-step: integrate the consent banner

Start by picking a CMP from the comparison above and installing its WordPress plugin, or adding its script to your site header manually. Next, configure your cookie categories, typically split into necessary, analytics, and advertising or personalization. Publish the banner and confirm it fires before any Google tag loads, since this “default deny” state is what Consent Mode V2 requires. Finally, confirm the CMP is correctly sending the initial default consent state before GTM’s container loads, and updating that state the moment a visitor makes a choice.

Using Google Tag Manager for implementation

GTM is the cleanest way to manage this once the banner is live. Add a Consent Initialization trigger so it fires before any other tag. Set your default consent state to denied across the board for ad storage, analytics storage, ad user data, and ad personalization. Configure your GA4 and Google Ads tags with additional consent checks, so they only fire, or only fire in cookieless “ping” mode, based on the visitor’s actual state. Then publish and use GTM’s Preview mode to confirm the consent signals update live as you accept or decline cookies on the front end.

If you’re managing a broader stack of integrations alongside GTM, including payment providers, booking widgets, and a CRM, it’s worth keeping a written map of which scripts depend on which consent categories. It saves hours the next time someone asks why a particular tag stopped firing.

Configuring the cookie consent banner

Beyond the legal minimum, a well-configured banner states clearly, in plain language, what each cookie category is for. It makes “reject all” exactly as easy to find as “accept all,” since regulators increasingly flag banners that don’t. And it loads fast, without blocking core page functionality while a visitor decides.

Person managing cookie consent settings on a laptop while holding a smartphone.

Understanding advanced mode settings

Advanced Consent Mode’s conversion modelling only works if Google has enough baseline signal to model against, generally a few hundred conversions per week per market. Below that threshold, don’t expect much recovery. It’s a statistical model, not magic.

Testing and troubleshooting your implementation

Before calling any consent implementation done, open your browser’s network tab and confirm the consent status attached to each request is correct for every scenario: accept all, reject all, and partial. Use GTM’s Preview and Debug mode to step through each consent state, and check GA4’s DebugView to confirm events still populate for consented users. It’s also worth re-testing after any CMP, GTM, or theme update, since these integrations tend to break silently more often than you’d think.

Review your banner quarterly rather than just at launch, since new categories, new ad platforms, and new regulatory guidance from bodies like the EDPB will all require adjustments over time. Monitor consent rates inside your CMP dashboard too; a sudden drop usually signals a banner bug rather than a genuine shift in visitor sentiment. And keep your documentation current: your privacy policy should always match what your banner actually collects, since mismatches here are one of the most common findings in regulatory audits.

Getting this right isn’t just a compliance exercise. It’s part of the same trust-building work that goes into a clear editorial policy or an honest about us page. Visitors notice when a business is straightforward about how it handles their data, and that trust compounds.

If you’d like to see how Sharefox’s own rental management software and booking software handle customer data end-to-end, you can start a free trial and explore the settings yourself. For more on getting your site discovered in the first place, see our Academy guide to SEO in Sharefox and our related post on running a hyper-efficient rental business.