Troubleshooting

Consent Mode Troubleshooting

Last updated March 5, 2026

Consent Mode Troubleshooting

Google Consent Mode Not Working

Symptom: Google Analytics is tracking without consent, or consent signals are not being sent. Checks: 1. Script order: LegalBanner must load BEFORE gtag.js. Check the order of script tags in your . 2. DevTools verification: Open Chrome DevTools > Console and look for gtag('consent', 'default', ...) and gtag('consent', 'update', ...) calls. 3. Tag Assistant: Use Google Tag Assistant to verify consent signals are received. 4. GTM Container: If using Google Tag Manager, ensure your GTM container is configured for Consent Mode. In GTM, go to Admin > Container Settings and enable "Enable consent overview." Common fixes:
  • Move the LegalBanner script tag above Google tags in your HTML
  • If using GTM, add a "Consent Initialization" trigger for LegalBanner
  • Clear browser cache and test in an incognito window

Meta Consent Mode Not Working

Symptom: Meta Pixel fires before consent is given. Checks: 1. The LegalBanner script must load before the Meta Pixel (fbq()) 2. Check DevTools Console for fbq('consent', 'revoke') on page load 3. After accepting marketing cookies, verify fbq('consent', 'grant') is called Common fixes:
  • Ensure the Meta Pixel script is placed after the LegalBanner script tag
  • If the Pixel is injected via GTM, ensure GTM respects consent signals

Analytics Data Missing

If you notice a drop in analytics data after implementing LegalBanner, this is expected behavior. Users who decline cookies will not be tracked. Google's Advanced mode provides behavioral modeling to estimate missing conversions.