Google Consent Mode v2: How It Works, What It Actually Changes, and What It Cannot Fix

A common misconception is equating a Consent Management Platform (CMP) with Google's Consent Mode itself. A CMP (Consent Management Platform) handles the visual and compliance elements: it displays the banner, collects the visitor's choice, and stores it. By contrast, Google Consent Mode v2 functions as a communication API - reading that choice and adjusting the behaviour of Google Analytics 4 and Google Ads scripts accordingly.

It is quite straightforward: if a user clicks "Reject analytics cookies" on the banner, the website must immediately send the analytics_storage=denied signal to the tag. Merely displaying "Rejected" on the banner pop-up changes nothing unless the tracking tags receive the corresponding command.

To align with the European Union’s Digital Markets Act (DMA), Google made Consent Mode v2 mandatory. Whilst version 1 relied on two core parameters (analytics_storage and ad_storage), version 2 introduced two crucial new signals:

• ad_user_data - sets consent for sending personal data to Google for advertising and measurement purposes (essential for features like enhanced conversions).
• ad_personalization - controls consent for personalised advertising and building remarketing audiences.

Both parameters must receive a value of either granted or denied depending on the user's choice. Failing to transmit these signals correctly prevents audiences from building and restricts campaign optimisation in Google Ads.

Implementing Consent Mode v2 can be done in one of two ways:

• Basic Mode: Google tags are completely blocked until the user interacts with the banner. If consent is denied, no data whatsoever is sent to Google. This is the simplest approach and offers maximum privacy, but it severely limits Google’s ability to model unobserved data.
• Advanced Mode: Google tags load immediately upon page open in a default denied state. If consent is declined, tags do not set cookies, but they send anonymous, cookieless pings. Google uses these signals for behavioural modelling in GA4 and conversion modelling in Google Ads.

Crucially, Advanced Mode does not mean tracking users against their wishes - data is estimated statistically on an aggregated level. Choosing between these modes should always be agreed with your organisation’s data protection or legal team.

Consent Mode v2 is a communication tool, not a quick fix for underlying analytics errors. Here is what Consent Mode cannot do for you:

• It will not generate a legally compliant banner or determine which consents are required.
• It will not fix misconfigured Google Tag Manager setups, broken GA4 events, or a lead form that fails to trigger a conversion tag.
• It will not automatically display modelled data on low-traffic websites.

For Google Analytics 4 to enable behavioural modelling, your property must meet strict volume thresholds: collect at least 1,000 daily events with analytics_storage='denied' for at least 7 days, and at least 1,000 daily users with analytics_storage='granted' for at least 7 out of the previous 28 days. If your site volume is below these thresholds, the model simply will not train.

To ensure your consent flow is working correctly, test it thoroughly using Google Tag Assistant or the Network tab in your browser’s Developer Tools:

• Test 1 (Before choice): Open the site in an Incognito window. In Advanced Mode, the default signal state should indicate unstated consent (look for gcs=G100 or gcs=G1-- in collect request parameters, along with default indicators in the gcd string).
• Test 2 (After accepting): Click "Accept All". The parameters in subsequent requests should update to granted (e.g. gcs=G111 and letters like r or v in gcd).
• Test 3 (After declining): Restart your session and click "Reject All". Signals should maintain denied values.

Make sure the consent update command executes before the main analytics events fire. Test this setup across key campaign landing pages as well as your homepage, as script loading sequences often differ across subpages.

A thorough audit report goes beyond simply stating "Consent Mode is working". It should document:

• A list of all four active signals (analytics_storage, ad_storage, ad_user_data, ad_personalization).
• Their default states and the exact timing of consent updates.
• Tag behaviour following user refusal (complete blocking vs cookieless pings).
• Screenshots from Google Tag Assistant or a verified inspect of window.dataLayer.

Only with this level of detail can you isolate true consent issues from tagging, GTM, or site configuration errors.

Properly implementing Google Consent Mode v2 is far more than a legal compliance exercise under the EU’s Digital Markets Act (DMA) - it is essential for maintaining digital marketing performance. Missing or incorrectly mapped signals like ad_user_data and ad_personalization will block remarketing audience expansion, disable enhanced conversion measurement, and degrade automated Smart Bidding strategies in Google Ads. Conversely, a well-configured Advanced Mode transmits cookieless pings that empower Google’s machine learning models to fill data gaps through GA4 behavioural modelling and conversion recovery. Ultimately, this provides a clearer view of user journeys, safeguards ad spend efficiency, and supplies the reliable data required for sound business decisions.