Google Consent Mode v2 Validation

Last updated: April 26, 2026

Use this page to verify Google Consent Mode v2 implementation quality before release.

1. Required Consent Signals

Verify all four keys are set and updated:

• ad_storage
• analytics_storage
• ad_user_data
• ad_personalization

2. Required Ordering

Baseline expectation:

1. Consent default is set before Google tags evaluate.
2. In banner regions, user choice triggers consent update.
3. In no-banner regions, defaults still resolve correctly (granted where banner is intentionally suppressed).
4. No conflicting consent commands are pushed by other scripts.

For GTM, use Consent Initialization - All Pages trigger.

For full GTM implementation steps, see Google Tag Manager (GTM) Template Guide.

3. Browser Console Checks

(window.dataLayer || []).filter(e => Array.isArray(e) && e[0] === 'consent')

Expected result: you can see both default and update commands in order.

4. Tag Assistant Checklist

1. Open Tag Assistant preview.
2. Test an EEA/UK session and reload with a fresh session.
3. Confirm consent defaults are present before Ads/Analytics tag execution.
4. Interact with banner and confirm consent update values change according to choice.
5. Test a non-banner region session and confirm defaults are granted when banner is intentionally not shown.

5. GTM Best Practices

• Keep CMP tag in Consent Initialization, not regular Page View.
• Avoid duplicate consent default commands from multiple templates.
• Keep region overrides documented in container notes.
• Do not hardcode one global denied default for every region.

6. Common Failures

• Consent defaults pushed too late.
• Tags fire before consent defaults.
• Missing one or more v2 keys in default or update calls.
• Another plugin overwrites consent state.
• No-banner sessions incorrectly receive denied defaults.

7. Evidence to Store for Audits

• Tag Assistant screenshots with event timeline (EEA banner flow + non-banner regional flow).
• Browser console export of consent events.
• CMP debug report from production domain.

See Cybexo Debug Tool and Audit Checklist (Pre-Launch).