How to Check Google Consent Mode V2 Manually (Step-by-Step Guide)

This guide focuses on manual verification. You will confirm whether consent defaults are set correctly, whether consent updates are sent after user choice, and whether signals appear in network requests.

The goal is clarity: know whether your setup is technically correct before you troubleshoot reporting differences. If you want an automated Consent Mode v2 checker, use this checker page.

When Should You Check Consent Mode Manually?

When debugging GTM implementation details
When validating CMP integration behavior
When investigating tracking discrepancies
When testing before production release

1. What “working” actually means

A working setup has three characteristics:

A default consent call exists before Google tags load.
Core states like ad_storage and analytics_storage are denied by default.
An update call switches states when users accept or reject.

2. Manual method (DevTools)

The fastest way to check if Consent Mode v2 is initialized is to look at the browser console and check the dataLayer.

Step 1: Open DevTools

Open your website in a new incognito/private window (important - this simulates a new user). Press F12 (Windows/Linux) or Cmd+Option+I (Mac) to open DevTools.

Step 2: Check the Console Tab

Go to the Console tab. Look for any errors related to consent or gtag. You should see Consent Mode initialization messages if it's working. However, many sites don't log anything, so this alone isn't definitive.

Step 3: Check the dataLayer

In the Console, type dataLayer and press Enter. You should see an array. Look for objects that contain event: 'gtm.init' or consent-related data.

What to look for:

An object with gtagConsent or gtm.consentMode
Default states showing ad_storage: 'denied' and analytics_storage: 'denied'

If you don't see consent data in the dataLayer, Consent Mode v2 likely isn't initialized.

If you are testing conversion tracking after consent, continue with this manual Google Ads conversion testing guide.

3. GTM method

If you use Google Tag Manager, use Preview mode to confirm consent initialization and update behavior in sequence.

Step 1: Open GTM Preview

Start a preview session and load a fresh page view where no prior consent has been stored.

Step 2: Confirm consent initialization timing

Confirm your consent configuration runs on Consent Initialization before conversion and analytics tags.

If this runs too late, later steps may look correct while attribution still fails.

Step 3: Verify consent state transition

Trigger Accept/Reject and confirm state transitions are reflected in tag firing and consent state data.

4. Common mistakes

Fires before consent

Tags run on page load before a user choice is registered.

No update call

Default denied exists, but no consent update is sent when users interact with the banner.

This is one of the common implementation mistakes.

Manual Check vs Automated Scan

Method	Pros	Cons
Manual (this guide)	Deep debugging	Slower and easier to miss edge cases
Automated checker	Fast and broad coverage	Less granular than manual inspection

Related guides:

Part of the Google Ads conversion tracking series:

← Back to: Why Google Ads Conversions Break