Google Consent Mode v2 Setup Guide for Lead Gen Sites
Step-by-step guide to implement Google Consent Mode v2 for lead gen sites, with CMP setup, tag mapping, testing, and evidence for compliance.
Google Consent Mode v2 lets you respect privacy choices while preserving measurement. For lead gen, aligning consent, tags, and disclosures prevents data loss and reduces compliance risk. This tutorial gives you a concrete setup plan, tests, and evidence practices.
Regulators focus on consent and transparency (see Meta’s EU fine of about 1.2 billion EUR in 2023, source: Reuters). US regulators also expect clear opt-outs, as seen in Sephora’s $1.2M CPRA action in 2022 (source: California AG). Align Consent Mode v2 with your cookie policy, privacy policy, and opt-out flows.
What to prepare
- CMP configured for EU/UK opt-in and US opt-outs where relevant
- Updated {cta_cookie} with vendor and purpose details
- Google tags (Ads, GA4) ready to receive consent signals
- Data layer or tag manager set to pass consent states (ad_storage, ad_user_data, analytics_storage)
- Testing plan on EU/UK IPs and US IPs
- Evidence folder for screenshots and logs
Step-by-step implementation
- Configure your CMP. Define purposes and vendors; enable TCF if needed. Map buttons to consent states.
- Set default states. Set ad_storage, ad_user_data, analytics_storage to denied until consent in opt-in regions.
- Update tags. Add Consent Mode v2 to GTM/gtag; ensure conversion tags respect consent.
- Handle US opt-outs. Honor GPC/do-not-sell/share separately; map to ad personalization off; document in the {cta_priv} and {cta_cookie}.
- Test. From EU/UK IPs: confirm tags wait for consent; check consent signals and conversions post-accept. From US IPs: check opt-outs and GPC handling.
- Publish and log. Update your cookie policy, banner text, and changelog. Store screenshots and Tag Assistant reports.
Recommended H2/H3 structure
CMP configuration
- Purposes and vendors; button behaviors; geo rules
Tag configuration
- gtag/GTM setup; default consent; conversion tags
Testing
- EU/UK opt-in tests; US opt-out/GPC tests; Tag Assistant
Troubleshooting
- Tags firing pre-consent; consent signals missing; conversions not recorded
Evidence and governance
- Keep a changelog; store screenshots; document consent logs
Table: consent signal mapping
| Region | ad_storage | ad_user_data | analytics_storage | Notes |
|---|---|---|---|---|
| EU/UK | denied until consent | denied until consent | denied until consent | Use opt-in banner |
| US (opt-out states) | granted until opt-out | granted until opt-out | granted until opt-out | Honor GPC, do-not-sell/share |
| Rest of world | your baseline | your baseline | your baseline | Apply consistent defaults |
Common mistakes to avoid
- Loading Google tags before consent in opt-in regions
- Not honoring GPC/opt-out alongside Consent Mode
- Missing retention and vendor details in the {cta_cookie}
- No evidence (no screenshots/logs of consent states and tag behavior)
External references
Conclusion
Consent Mode v2 is powerful when aligned with real consent flows. Pair it with a solid cookie policy via the {cta_cookie}, full disclosures in the {cta_priv}, and consistent {cta_terms}. Test regularly and keep evidence so you can prove compliance and protect measurement.
H2: Advanced configuration
H3: Consent default and region rules
- Use region-based defaults: opt-in for EU/UK; opt-out toggles for US states with sale/share rules.
- Set tag defaults to denied until consent in opt-in regions.
H3: Tag mapping checklist
- Map ad_storage, ad_user_data, analytics_storage per region.
- Configure conversion linker and Ads/Analytics tags to read consent.
- Ensure server-side tagging (if used) respects consent states.
H3: Data layer events
- Push consent states into data layer; include versioning for prompts and vendor lists.
- Log what is sent to Google in DevTools/Tag Assistant.
H2: Troubleshooting table
| Issue | Fix | Evidence |
|---|---|---|
| Tags fire pre-consent | Check CMP integration, default states | Screenshots, network logs |
| Consent signals not sent | Verify data layer pushes and tag settings | Tag Assistant export |
| Conversions drop | Confirm consent rates, modelled conversions enabled | Reports |
H2: Evidence and governance
- Keep a consent mode changelog (dates, versions, tags affected).
- Store screenshots and Tag Assistant reports for audits.
- Align cookie policy and banner text with your Consent Mode behavior via the Cookie Policy Generator and Privacy Policy Generator.
Conclusion
Consent Mode v2 needs precise setup and proof. Align tags, CMP, and policies, test regularly, and keep evidence. Link to the Cookie Policy Generator, Privacy Policy Generator, and keep the Terms of Service Generator consistent with your data uses.
H2: On-page FAQ to add
- “Why do I need to accept or manage cookies?”
- “How do I change my choices later?”
- “Do you sell/share my data?”
- “How long do you keep analytics data?” Link answers to your Privacy Policy Generator and Cookie Policy Generator for details.
H2: Evidence and audit kit
- Banner and preferences screenshots with dates
- Consent/opt-out logs with prompt versions and regions
- Tag/config changelog and release notes
- Test scripts and results (EU/UK opt-in, US opt-out/GPC)
H2: Governance checklist
- Owner and backup for banner/CMP configs
- Quarterly copy review for banner and policies
- Monthly GPC/opt-out tests
- Version history for policies, banners, and tag configs
H2: Conclusion
Consent and cookies are living controls. Keep banners, policies, and tags aligned with the Cookie Policy Generator, Privacy Policy Generator, and Terms of Service Generator. Test and log regularly so you can prove compliance to platforms, customers, and regulators.
Cookie Policy Generator
Create a cookie policy for GDPR compliance. Create yours in minutes with TermsBox.
Generate NowH2: Copy blocks for your banner and policy
- “We use Google tags for analytics and ads. They only run after you accept in opt-in regions; you can change choices anytime.”
- “In the US, we honor opt-out signals and Global Privacy Control where applicable.”
H2: Metrics to watch
- Consent acceptance by region and device
- Conversions with and without consent; modelled conversions usage
- GPC detection counts and opt-out rates
H2: Conclusion
Consent Mode v2 needs clear copy, correct tag mapping, and proof. Keep your {cta_cookie} and {cta_priv} aligned, and ensure {cta_terms} do not promise what you cannot deliver.
H2: Migration checklist (v1 to v2)
- Update gtag/GTM templates to Consent Mode v2.
- Map consent states for ad_storage, ad_user_data, analytics_storage.
- Enable modeled conversions and check reporting after migration.
- Refresh banner text to mention Consent Mode behavior; link to Cookie Policy Generator and Privacy Policy Generator.
H2: Troubleshooting FAQ
- Conversions dropped? Check consent rates, modeled conversions, and if tags wait for consent.
- Consent signals missing? Verify data layer pushes and tag configuration; ensure CMP integration is live.
- GPC not honored? Confirm your CMP maps GPC to ad personalization off and logs signals.
H2: Evidence bundle
- Tag Assistant exports for accept/reject/manage flows
- CMP logs with versions and vendor lists
- Screenshots of banner, manage link, and policy pages
- Change log of tag settings with dates and approvers
H2: External links
H2: Conclusion
Consent Mode v2 only works with aligned copy, CMP signals, and evidence. Keep policies in sync via the Cookie Policy Generator and Privacy Policy Generator, and ensure the Terms of Service Generator don’t conflict. Test routinely and store proof.
H2: Consent and conversion modeling tips
- Enable modeled conversions to reduce signal loss; monitor variance vs observed conversions.
- Separate brand vs non-brand campaigns when analyzing consent impact.
- If consent rates are low, test clearer banner copy and placement.
H2: Documentation to keep
- CMP configuration exports and purpose/vendor lists.
- Tag configuration screenshots for each release.
- A runbook for updating tags when Google changes requirements.
H2: Frequently asked implementation questions
- Do I need Consent Mode if I only run analytics? Yes in opt-in regions; it controls analytics_storage and respects consent.
- Does Consent Mode replace cookie banners? No. You still need a banner/CMP to collect consent.
- How do I handle server-side tagging? Pass consent states to the server container and respect them in all endpoints.
Conclusion
Treat Consent Mode as part of your consent program, not a shortcut. Keep CMP, tags, and policies in sync, prove behavior with logs, and align with the Cookie Policy Generator, Privacy Policy Generator, and Terms of Service Generator.