Guide

Consent Mode v2 implementation checklist

A practical checklist for validating Consent Mode defaults, updates, GTM sequencing, Google signals, region behavior, and evidence capture.

Consent Mode v2 should be validated as browser behavior, not as a tag installation.

This checklist focuses on the implementation controls that decide whether Google tags receive the right consent state at the right time.

What breaks

The failure pattern usually starts before the dashboard can see it.

Defaults are installed after tags

The tag manager may load Google libraries before denied defaults are available.

Consent updates are partial

Some user choices update analytics signals but not advertising or user data signals.

Regions are untested

Different consent defaults may be needed across EU, UK, US, and fallback traffic.

How ModeConsent fixes it

Repair the consent system where visitors and tags actually interact.

Implementation work is sequenced from observation to repair to proof, so legal requirements, platform behavior, and measurement needs are reconciled in the same technical record.

01

Check initialization order

Verify defaults exist before Google tags, conversion tags, and dependent templates execute.

02

Exercise every choice

Test reject, accept, category selections, preference changes, and revisit behavior.

03

Capture browser evidence

Record network requests, data layer events, storage changes, and visible consent state for each test.

Evidence we validate

Proof artifacts for the browser, not just the policy file.

Consent defaults visible before Google requests

Four v2 signals checked after each user action

GTM consent checks mapped to CMP categories

GA4 and Ads requests compared across states

Screenshots and request logs saved for signoff

Start with evidence

Find out what your site actually does before a regulator, browser, or platform does.

ModeConsent audits the live browser behavior of your consent stack and turns the results into a prioritized implementation roadmap.