Consent & Tag Firing Debugger

Simulate user banner choices and verify how GTM tags fire across Google Ads, GA4, Meta, and third-party trackers. Test EEA/UK DMA compliance and compare Advanced Consent Mode vs Basic Consent Mode.

User Consent Signals
GCM v2 Consent States
ad_storage
analytics_storage
ad_user_data
ad_personalization

Tag Execution & Signal Diagnosis

INTERACTIVE DEMO Want to test how this tool works?
Save these results as a PDF report A clean, branded copy to share with your team or client.
Free PDF report

Where should we put your name on the report?

Your PDF downloads straight away. Your tool data never leaves your browser.

Jobair Mahmud, Web Analytics & Tracking Architect
Tool Creator

Jobair Mahmud

Founder & Tracking Architect

100% Top Rated
★★★★★
5.0 / 5.0

Need your Consent Mode v2 setup audited?

I audit and implement Consent Mode v2 with OneTrust, Cookiebot, CookieYes, and custom CMPs to ensure complete regulatory compliance.

Audit my Consent Mode setup →

How to use the Consent Mode v2 Tag & Trigger Debugger

Under Google Consent Mode v2, Google tags must adjust behavior based on four core consent states (ad_storage, analytics_storage, ad_user_data, and ad_personalization). This debugger simulates user consent decisions and checks whether your GTM triggers fire properly or leak tracking data.

Step by step

  1. Select user consent states for Analytics, Ads, User Data, and Personalization.
  2. Inspect the generated gtag("consent", "default") and gtag("consent", "update") commands.
  3. Check which tags are allowed to write cookies versus which must send cookieless modeled pings.
  4. Verify that tag firing triggers in GTM match your Consent Management Platform (CMP) events.

How to read your result

Full Consent Granted

Tags execute with full cookie access; GA4 records complete session paths and ad conversion tags send rich attribution signals.

Consent Denied (Cookieless Mode)

Tags must not set or read storage cookies. Google tags transmit cookieless pings to support behavioral modeling in GA4.

Common mistakes

  • Blocking GTM container scripts completely when consent is denied, which prevents Google Consent Mode from sending modeled pings.
  • Firing tag updates after GA4 config tag has already executed, causing the initial page view to be recorded with denied consent.
  • Forgetting the two new v2 signals (ad_user_data and ad_personalization), resulting in Google Ads audiences remaining empty.

Questions

What is the difference between Basic and Advanced Consent Mode?

Basic blocks tags completely until consent is granted (0 data collected). Advanced allows Google tags to load with denied consent, sending cookieless pings that train GA4 behavioral modeling.

Is Google Consent Mode v2 mandatory?

Yes. Since March 2024, Google requires Consent Mode v2 for all advertisers measuring traffic or running remarketing campaigns targeting users in the EEA and UK.

Need your Consent Mode v2 setup audited?

I audit and implement Consent Mode v2 with OneTrust, Cookiebot, CookieYes, and custom CMPs to ensure complete regulatory compliance.