How to Check if Google Consent Mode v2 is Enabled

Is your cookie banner working? Learn how to check if Google Consent Mode v2 is enabled on your site using automated scanners, GTM Preview, and Tag Assistant.

Having a visual cookie banner on your website does not mean your tracking is compliant. Google Consent Mode v2 is mandatory for any site running Google Ads or Google Analytics 4 (GA4) in the European Economic Area (EEA) and the United Kingdom.

Why Checking Matters

If your consent banner is not correctly communicating with your tracking stack, your website will fail to transmit critical privacy parameters to Google’s servers. Checking your configuration ensures that your legal privacy requirements match your actual network payloads.

What Happens If It Is Not Enabled

If Consent Mode v2 is missing or broken, the consequences are immediate:

Emptied Remarketing Lists: Google Ads will block you from populating retargeting audiences. Lost Conversion Modeling: GA4 and Google Ads will stop receiving cookieless pings, blinding your Smart Bidding algorithms. Regulatory & DMA Liability: You risk violating the Digital Markets Act (DMA) and regional data protection laws.

Two Ways to Check

You can test your setup using automated tools (which scan network payloads in seconds) or manual inspection methods (using Google Tag Manager Preview mode and browser diagnostic tools).

Here is how to run both checks step-by-step.

Method 1: Free Automated Check (60 seconds)

The fastest and most reliable way to verify your tracking setup is to run your domain through an automated network scanner.

Manual checks show what is happening in your specific browser session, but an automated scanner evaluates the exact raw data packets being transmitted to Google's endpoints.

Check Your Site Free: Tag Integrity Consent Mode Scanner

What the Results Mean

PASS: Your site actively detects a Consent Management Platform (CMP), sets default consent states before tags fire, and transmits all four Consent Mode v2 parameters (adstorage, analyticsstorage, aduserdata, and adpersonalization). FAIL: Your setup is missing critical V2 signals, suffers from a race condition (tags firing too early), or has a visual banner that is entirely disconnected from Google Tag Manager.

Method 2: Check Manually with GTM Preview

If you manage your site’s tags via Google Tag Manager (GTM), you can inspect the data layer timeline directly inside GTM's Preview mode.

1. Open your GTM workspace and click Preview in the top right corner. 2. Enter your website URL and click Connect to open Google Tag Assistant. 3. Check the Default State: In the Tag Assistant timeline on the left, click on the Consent Initialization event (the very first event). Click the Consent tab in the main window. 4. Check the Update State: Go back to your website debug window, click "Accept All" on your cookie banner, and return to Tag Assistant. Click on the custom consent update event in the timeline (e.g., cookieconsentupdate).

What to Look For

Under Consent Initialization, all four V2 signals should show as Denied (for strict compliance regions) under the "On-page Default" column. Under the update event, all four signals should transition to Granted under the "On-page Update" column.

Method 3: Check with Google Tag Assistant

You can also inspect network payloads live using Google Tag Assistant or your browser's Developer Tools.

1. Open your website in Chrome and press F12 to open Developer Tools. 2. Navigate to the Network tab and type collect? in the filter bar. 3. Refresh the page and click on one of the network pings sent to Google Analytics or Google Ads. 4. Scroll to the payload parameters and locate gcs and gcd.

Interpret Your Results

gcs Parameter: Must show G100 before accepting consent (storage denied) and G111 after accepting consent (storage granted). gcd Parameter: Inspect this alongside the named states in Tag Assistant. Its presence or individual encoded letters alone do not verify that consent was granted; compare the default and update states against the visitor's choice.

Why a Visible Banner Is Not Enough

A banner disappearing after a click only confirms a visible interaction. It does not confirm that default consent was established before Google tags loaded, that the CMP sent an update, or that the resulting requests reflect the visitor's choice. Use the Consent tab in Tag Assistant and the Network tab together rather than treating the CMP dashboard as proof.

Verify the Full Visitor Journey

1. Start with a fresh browser session and record all four default states before interacting with the banner. Confirm the default is established before the first Google tag. 2. Accept the relevant categories and confirm the On-page Update states match that choice, especially aduserdata and adpersonalization. A CMP may apply the update through its consent API rather than a custom event with a particular name. 3. Start another fresh session, reject consent, and verify the denied states remain in place. In basic mode, Google tags are blocked until consent; in advanced mode, eligible tags can send cookieless pings while denied. 4. Reload and navigate to another page to confirm the stored choice is reapplied before tracking starts. Repeat on checkout or other domains in the visitor journey. 5. Record the tested URL, region, default and update states, and request evidence so a developer can reproduce any mismatch. Regional defaults must follow the requirements that apply to your visitors; geography alone is not a reason to assume consent is granted.

The gcd parameter encodes default and update consent information. Its presence alone, or particular letters in the string, does not prove that all four signals are correctly configured or granted. Confirm the named consent states in Tag Assistant and compare requests before and after a choice. See Google's consent debugging guide.

What the Consent Signals Mean

To be fully compliant with Consent Mode v2, your setup must explicitly manage four parameters:

adstorage: Controls cookie-based ad tracking and storage on the user's device. analyticsstorage: Controls cookies related to website analytics, such as visit duration and pageviews. aduserdata: Sets explicit consent for sending user-related advertising data to Google. adpersonalization: Sets explicit consent for personalized advertising, which is required to build remarketing lists.

What to Do if Consent Mode is Missing

If your audit reveals that Consent Mode v2 is missing or incomplete, follow these remediation steps:

1. Install a Certified CMP: Ensure you are using a Google-certified Consent Management Platform (such as Cookiebot, CookieYes, or OneTrust) that natively supports V2 signal mapping. 2. Configure GTM: Ensure your CMP tag inside GTM uses the Consent Initialization - All Pages trigger so default states lock in before tracking tags load. 3. Follow a Verified Blueprint: Read our complete Consent Mode v2 GTM Setup Guide to walk step-by-step through configuring your tags, triggers, and update events.

Common Issues Found

During technical audits, three structural errors account for almost all failing setups:

No CMP Detected (Visual Only): A cookie banner displays on the site, but it is not linked to GTM. The banner opens and closes, but zero consent signals are pushed to the data layer. Signals Not Configured (Legacy V1): The site passes adstorage and analyticsstorage, but completely lacks the newer aduserdata and adpersonalization parameters. Wrong Trigger Order (Race Conditions): GA4 or Google Ads tags load on standard "Page View" triggers before the CMP has a chance to set default consent states, causing tags to fire illegally.

Verify Your Implementation Today

Never assume your cookie banner is working based on visual appearance alone. A misconfigured setup will silently degrade your ad performance, corrupt your GA4 data, and expose your business to legal compliance risks.

Check Your Site Free →

Published by TagIntegrity Professional Tag Auditing Platform tagintegrity.com

Run a free Consent Mode v2 scan