Testing and Verifying Consent Mode v2 Implementation | Adslytics | Adslytics

Consent Mode How-To Guide

Testing and Verifying Your Consent Mode v2 Implementation

By Muhammad Farooq · April 9, 2026 · 5 min read
Testing and Verifying Your Consent Mode v2 Implementation

Why Testing Is Critical

Many Consent Mode v2 implementations look correct but are functionally broken. The banner displays, the GTM tags appear to fire, but the consent signals never reach Google — meaning you are either tracking all users without consent (compliance violation) or treating all users as non-consenting (data quality problem). Systematic testing is the only way to verify correct operation.

Test 1: GTM Preview Consent Tab

  1. Open GTM Preview Mode and browse to your site in an incognito window
  2. In Tag Assistant, look for the "Consent" tab (appears when Consent Mode is configured)
  3. Initial state: all four consent types should show "Denied" (before banner interaction)
  4. Click "Accept All" in the cookie banner
  5. Consent tab should update immediately to show all types as "Granted"
  6. Reload the page (still in incognito) — consent tab should show "Granted" from the stored consent cookie (confirming the CMP persists consent correctly)

Test 2: Network Request Inspection

With consent denied, GA4 should send cookieless pings (in advanced mode) or nothing (in basic mode):

  1. Open DevTools → Network tab → filter for "collect" or search for your GA4 Measurement ID (G-XXXXXXXXXX)
  2. In an incognito window with consent denied, browse to a page
  3. You should see GA4 network requests (in advanced mode) with reduced parameters — no _ga, no client_id parameter
  4. Accept consent, then browse — GA4 requests should now include _ga cookie parameter and full data

Test 3: Consent on Return Visit

A critical failure mode: the CMP correctly calls gtag('consent', 'update') on the first visit but doesn't restore consent correctly on return visits.

  1. Visit the site in a regular (non-incognito) browser, accept all consent
  2. Reload the page
  3. GTM Preview Consent tab should show "Granted" immediately on page load (before the banner appears)
  4. If it shows "Denied" then updates to "Granted" a moment later: this indicates a timing issue where tags fire before the CMP restores consent

Test 4: Category-Specific Consent

Verify that partial consent (accepting analytics but not marketing) is correctly reflected:

  1. In incognito, accept only "Analytics/Statistics" cookies, decline "Marketing/Advertising"
  2. Consent tab: analytics_storage = Granted, ad_storage = Denied, ad_user_data = Denied, ad_personalization = Denied
  3. If all four are Granted after accepting only analytics: your CMP category mapping is incorrect

Test 5: Google Ads Consent Diagnostics

In Google Ads → Admin → Privacy and messaging → Consent settings → Check the consent signal diagnostic. This shows whether Google Ads is receiving valid consent signals from your website.

Summary

Consent Mode v2 verification requires five tests: (1) GTM Preview Consent tab showing correct default/update states, (2) Network request inspection confirming cookieless vs full hits, (3) Return visit consent restoration timing, (4) Category-specific partial consent mapping, (5) Google Ads consent signal diagnostic. Only passing all five tests confirms a correctly functioning implementation.

See our Consent Mode v2 Implementation service for verification support.

Need your Consent Mode implementation verified? Contact Adslytics.

Need expert tracking setup?

Our Google Tag Manager experts have delivered 500+ tracking setups with a 98% success rate.

Get a Free Consultation →
← Back to Blog
Muhammad Farooq

Author

Muhammad Farooq GTM & Analytics Expert · Adslytics Founder

Tracking specialist with 10+ years of experience in Google Tag Manager, GA4, Server-Side Tracking, and Google Ads. Founder of Adslytics — a dedicated analytics agency with a 98% success rate across 232+ projects on Upwork.

Top Rated Plus LinkedIn Visit the author's profile →