Launch
Consent Mode v2 checklist before launch
Use a launch checklist for signal order, banner mapping, network behavior, GA4 and Ads, withdrawal, regional rules and evidence.

In brief
Release only after the first-visit trace, mixed-choice trace and withdrawal trace match your chosen mode.
Before implementation freeze
Inventory every Google tag, CMP script, third-party pixel and first-party proxy. Decide Basic or Advanced mode and record who approved the pre-consent behavior. Review regional rules and banner wording with the appropriate owner.
If the four signals are unfamiliar, start with the Consent Mode v2 overview before recording release evidence.
Check signal timing and mapping
On a clean first visit, confirm ad_storage, analytics_storage, ad_user_data and ad_personalization have a default before tags. Test analytics-only and advertising-only choices if your banner offers them. Confirm a choice updates consent without a reload.
Check actual requests
Use Tag Assistant and DevTools together. For Basic mode, no Google tag data should leave before permission. For Advanced mode, document the limited pings you expect while denied. Check storage and network activity for non-Google tags too.
Check change and persistence
Test reject, accept, granular choice and withdrawal. Reload and navigate to a second page after each choice. Confirm the saved state returns early and no stale grant briefly fires a tag.
Ship with evidence
Record the live URL, container version, test browser, choice states, screenshots of the consent timeline and a network trace. Re-run the same checklist after a CMP, theme, tag or analytics change. Use the interactive list below as a working sign-off, not as automated certification.
Try it
Launch readiness checklist
0 of 11 checked
This checklist stays on this page only. Save your evidence in your own release record.
Continue with a related guide
Primary sources
- Google: Set up consent mode(opens in a new tab)
- Google: Troubleshoot consent mode(opens in a new tab)
- Google Analytics: Verify consent settings(opens in a new tab)
Reviewed 15 October 2026. Validate product interfaces and requirements for your own implementation.
Check the implementation on your site
Consentory helps teams inspect trackers, configure prior blocking and document consent choices. The guides above give you a test plan before rollout.