Introduction
Fix missing Google Consent Mode v2 configuration. Set denied defaults before GTM loads and wire consent updates to banner choices.
What it means
Google Consent Mode v2 parameters (analytics_storage, ad_storage, ad_user_data, ad_personalization) are not being set before Google tags load. This means Google tags run with default (potentially granted) consent state.
For sites using Google Analytics or Google Ads with EU traffic, missing Consent Mode v2 signals can impact both compliance posture and ad campaign measurement.
Why it matters
Regulators and compliance scanners treat this issue as a technical indicator that consent processes may not match stated policies. It is one of the most common findings in automated GDPR audits across all website categories.
Fixing this issue typically produces the largest single improvement in compliance scores, because it addresses the most heavily weighted scanning criteria.
Common mistakes
- Assuming the banner UI alone is sufficient — scanner findings are based on network and script behavior, not visual inspection.
- Testing only with an already-consented browser session, which hides the pre-consent behavior.
- Fixing the homepage but not campaign landing pages, subdomains, or localized variants.
Practical checklist
- Add Consent Mode v2 default commands (all four parameters set to denied) before any Google script loads.
- Wire the CMP to fire consent updates with the correct parameter states on Accept, Reject, and preference changes.
- Map analytics consent to analytics_storage and marketing consent to ad_storage, ad_user_data, and ad_personalization.
- Verify with Google Tag Assistant and a GDPRChecker scan in a private window.
- Run a compliance scan after fixes to confirm the issue is resolved.
- Document the fix date and rescan result for audit evidence.
How GDPRChecker helps
GDPRChecker flags Google Consent Mode v2 not configured as a medium-severity finding in scan reports. While less urgent than pre-consent tracking, this issue should be addressed to improve transparency and reduce compliance surface.
After implementing the fix, rescan your site with GDPRChecker to confirm the finding is cleared and your compliance score improves.