Consent & GDPR 8 min read September 04, 2026

Understanding Google Consent Mode v2: Basic vs Advanced

A practical guide outlining the differences between Basic and Advanced consent mode implementations and how it impacts your GA4 metrics.

PD
PowerData Engineering TeamTechnical Marketing Architects

The Problem Frame

With the roll-out of the Digital Markets Act (DMA) in the EU, Google Consent Mode v2 became mandatory for utilizing Google Ads remarketing and audience building. However, many businesses rush the implementation and end up either breaking their measurement entirely, or violating GDPR by misconfiguring tags.

Engineering The Solution

01

1. Grasp the Concept of Consent States

Consent mode utilizes parameters (like `ad_storage`, `analytics_storage`, `ad_user_data`, and `ad_personalization`). Depending on a user's choice in your Cookie Banner (CMP), these are set to 'granted' or 'denied'.

02

2. The 'Basic' Implementation

In Basic mode, tags are hard-blocked from firing until consent is explicitly granted. If a user rejects cookies, nothing fires. No data of any kind goes to Google. This is the strictest, safest legal approach, but results in massive data gaps in GA4.

03

3. The 'Advanced' Implementation

In Advanced mode, Google tags (GA4, Ads) load immediately but in a restricted 'denied' state. If consent is rejected, the tags fire 'cookieless pings' that do not read or write cookies, but pass basic contextual info (like timestamp, referral URL). Google uses these pings to use machine learning to 'model' conversion paths for the unconsented users, preserving reporting.

04

4. Configuring the CMP in GTM

Ensure you use a Google-certified CMP (Consent Management Platform). Use their official GTM template to initialize the default consent state before any other tags fire. Then, build Consent Checks natively into every single remaining tag in your container.

QA Checklist

Use GTM Preview mode and click on a 'Consent' or 'Initialization' event to verify the Default 'ad_storage' and 'analytics_storage' are denied.
Accept cookies on the banner and verify a 'Consent Update' event fires and changes the statuses to 'granted'.
Monitor network requests. For unconsented users, search the payload for the parameter `gcs` and verify it reads `G100` (meaning denied for both) and lacks cookie values.

Want us to build this for you?

Skip the trial and error. We implement these architectures perfectly on exactly your stack.

Common Questions About This Approach

It is debated. Some data authorities argue passing even 'cookieless pings' without consent is questionable under ePrivacy derivatives. Always consult your legal counsel. Basic Mode is universally safer, while Advanced is better for marketers.

Google claims Advanced Consent Mode can recover up to 70% of ad-click-to-conversion journeys lost due to user cookie rejection, but this requires substantial traffic volume to train the models.