Definition

Consent Mode is a Google framework that adjusts tag behavior based on user consent choices for cookies and data collection — allowing analytics and ads tags to respect GDPR, UK GDPR, and similar privacy laws while still modeling conversions when consent is denied.

Detailed Explanation

Consent Mode v2 (required for EEA/UK advertisers since March 2024) communicates consent status to Google tags via ad_storage, analytics_storage, ad_user_data, and ad_personalization parameters. When users deny consent, tags run in limited mode and Google uses modeling to fill measurement gaps.

Implementation requires a Consent Management Platform (CMP) or custom banner integrated with Google Tag Manager’s Consent Initialization trigger.

Nepal Context

Nepal’s Individual Privacy Act, 2075 (2018) sets general privacy duties but has no Consent Mode-style rules for ads. Even so, Nepali businesses targeting EU/UK customers or using Google Ads globally must implement Consent Mode v2 or face restricted remarketing and conversion tracking in those regions. Agencies serving export-oriented clients should standardize GTM consent templates.

Practical Examples

  1. GTM: Consent Initialization → Default denied → Update on banner accept.
  2. Verify with Tag Assistant: consent state should propagate to GA4 and Google Ads tags.
  3. Compare modeled vs. observed conversions in GA4 after implementation.

How to Check It

  1. Use Tag Assistant to confirm the default consent state loads before any Google tag fires.
  2. Test from an EU or UK location (a VPN works) to see the banner and confirm consent updates after a choice.
  3. In Google Ads, check the consent mode status in conversion diagnostics after a few days of traffic.

Key Takeaways

  • Consent Mode v2 is mandatory for EEA/UK Google Ads measurement.
  • Tags still fire in limited mode — you do not lose all data when consent is denied.
  • Implement via GTM + CMP for maintainability.

Common Mistakes

  1. Blocking all tags when consent denied — loses modeling benefits; use Consent Mode instead.
  2. Not testing in EEA VPN — consent banner may not appear for Nepali IP testing.
  3. Outdated Consent Mode v1 — upgrade to v2 with ad_user_data and ad_personalization.