Google Ads Consent Mode v2: What Nonprofits Need to Know
If your nonprofit's website receives visitors from the European Economic Area (EEA) or the United Kingdom, Consent Mode v2 affects how your Google Ad Grant tracks conversions. Since March 2024, Google has required advertisers targeting EU/UK users to implement Consent Mode v2 for accurate conversion measurement and audience features.
For many nonprofits, this sounds more complicated than it is. Most of the heavy lifting is handled by cookie consent platforms, and the actual impact on your Grant performance is manageable. This guide explains what Consent Mode is, whether you need it, and how to implement it.
Key Takeaways - Required for any advertiser showing ads to EU/EEA/UK users since March 2024 - Consent Mode lets GA4 and Google Ads respect cookie consent while still modeling conversions - "Advanced" mode (recommended) sends anonymized pings even when consent is denied, enabling conversion modeling - Most implementation is handled by cookie consent platforms (Cookiebot, OneTrust, etc.) - Nonprofits with primarily domestic (non-EU) traffic are less affected but should still implement
What Is Consent Mode?
Consent Mode is a framework that connects your cookie consent banner to your Google tags (GA4, Google Ads). When a visitor accepts cookies, your tags work normally. When they deny cookies, Consent Mode adjusts what data is collected.
Without Consent Mode: If a visitor denies cookies, your GA4 tag either fires anyway (violating GDPR) or doesn't fire at all (you lose all data from that visitor).
With Consent Mode: When a visitor denies cookies, Google's tags adjust their behavior automatically. In "Advanced" mode, they send anonymized, cookieless pings to Google, which Google uses to statistically model the conversions it can't directly observe.
Do You Need It?
Yes, if: Your Google Ad Grant campaigns target any EU/EEA country or the UK, or your website receives significant traffic from these regions (even if you don't actively target them).
Technically optional but recommended if: Your nonprofit is based outside the EU/UK but your website receives some international traffic. Implementing Consent Mode is increasingly considered best practice globally, and other regions (Brazil, Australia, Canada) have their own privacy regulations that may require similar measures.
Probably not urgent if: Your nonprofit serves only a local community in a non-EU country, your website traffic is almost entirely domestic, and you don't target any EU/UK audiences.
Basic vs Advanced Consent Mode
| Feature | Basic Mode | Advanced Mode (Recommended) |
|---|---|---|
| When consent is denied | No Google tags fire at all | Tags fire with limited, anonymized data |
| Conversion tracking for denied users | Zero data collected | Google models conversions using anonymized pings |
| Impact on conversion data | Can lose 30-70% of conversions in EU/UK traffic | Recovers most lost conversions through modeling |
| Compliance | Fully GDPR compliant | Fully GDPR compliant |
Why Advanced is recommended: In Basic mode, you lose all conversion data from visitors who deny cookies. In regions where 40-60% of visitors deny cookies, that's a massive data gap. Advanced mode fills the gap through statistical modeling.
Requirements for conversion modeling: At least 700 ad clicks over 7 days per country/domain, 7 full days of data collection, and a reasonable consent rate (typically 20%+).
How to Implement Consent Mode v2
Step 1: Choose a Consent Management Platform (CMP)
A CMP provides the cookie consent banner on your website and communicates consent signals to Google's tags. Popular options compatible with Consent Mode v2:
| CMP | Cost | Complexity |
|---|---|---|
| Cookiebot | Free for up to 1 domain | Low |
| OneTrust | Paid (free tier limited) | Medium |
| Complianz (WordPress) | Free and paid tiers | Low (WordPress only) |
| CookieYes | Free for small sites | Low |
| Termly | Free tier available | Low |
| iubenda | Free and paid tiers | Low |
For most nonprofits, Cookiebot or CookieYes on the free tier is sufficient.
Step 2: Install the CMP on Your Website
Follow your chosen CMP's installation instructions. Most provide:
- A JavaScript snippet to add to your website's
<head>section - WordPress plugins for easy installation
- Integration instructions for GTM
Step 3: Configure Consent Mode in GTM
If you're using GTM (recommended for Grant accounts):
- In GTM, go to Admin, then Container Settings
- Enable Consent Overview (if not already enabled)
- Go to Tags, then edit your Google Tag (GA4 Configuration)
- In Consent Settings, select "Require additional consent for tag to fire" or configure the built-in consent types
- Set the default consent state:
- For EU/EEA/UK visitors:
denied(until they accept) - For all other visitors:
granted
- Your CMP's GTM integration will automatically update consent state when visitors interact with the banner
Step 4: Set Default Consent State
Add a default consent configuration that fires before any other tags. In GTM:
- Create a new Custom HTML tag (or use your CMP's provided template)
- Set the default consent:
analyticsstorage: denied,adstorage: deniedfor EU visitors - Set the trigger to fire on Consent Initialization - All Pages (fires before all other tags)
- Your CMP updates these to
grantedwhen the visitor accepts cookies
Step 5: Verify Implementation
- Visit your website with your CMP's test mode or in an incognito window
- Before accepting cookies: Check that Google tags fire in a limited mode (in GTM Preview, you should see consent-related adjustments)
- After accepting cookies: Confirm full tracking activates
- In Google Ads, check your conversion diagnostics. If conversion modeling is active, Consent Mode is working.
Impact on Your Google Ad Grant
For nonprofits targeting only non-EU countries: Minimal impact. Most of your visitors grant consent by default (or consent isn't required). You may see a small data gap from international visitors, but it won't significantly affect Smart Bidding or compliance.
For nonprofits targeting EU/UK audiences: You'll likely see 10-30% fewer directly measured conversions compared to pre-Consent Mode numbers. Advanced Consent Mode's modeling recovers most of this gap, but not all. Your reported conversion numbers may be slightly lower than actual conversions.
For Smart Bidding: Google's bidding algorithms are designed to work with Consent Mode data. They account for modeled conversions when optimizing bids. You don't need to adjust your bid strategy after implementing Consent Mode.
For compliance: Consent Mode actually helps your conversion tracking compliance by maintaining a conversion signal (even if modeled) rather than losing all data from denied-consent visitors.
Common Implementation Mistakes
Not setting a default consent state: If you don't set defaults to "denied" for EU visitors, tags fire fully before the consent banner loads, which violates GDPR.
Using Basic mode instead of Advanced: Basic mode loses all data from denied visitors. Advanced recovers it through modeling. Always use Advanced unless you have a specific legal reason not to.
Only implementing on some pages: Consent Mode must be active on every page of your website, not just landing pages. Visitors navigate between pages, and consent state must persist.
Forgetting to test: Use GTM Preview mode and your CMP's test tools to verify consent signals are being sent correctly.
Check Your Consent Mode with GrantMax
GrantMax checks whether Consent Mode is affecting your conversion tracking and whether conversion modeling is active for your account.
Check My Tracking Setup - Free
Prefer to hand it off to an expert? Our GA4/GTM setup add-on includes Consent Mode v2 implementation. Explore Grant Services
Frequently Asked Questions
Is Consent Mode required for all Google Ad Grant accounts? It's required for any advertiser showing ads to users in the EU/EEA or UK. If your Grant doesn't target these regions and you receive minimal traffic from them, it's not strictly required but is increasingly recommended as a global best practice.
Will Consent Mode reduce my conversion count? It may reduce directly measured conversions from EU/UK traffic by 10-30%. Advanced Consent Mode's modeling recovers most of this. Overall impact on non-EU accounts is minimal.
Do I need a developer to implement this? For most CMP solutions (Cookiebot, CookieYes), a non-developer can handle the implementation using their WordPress plugin or GTM integration. Complex custom implementations may need developer support.
Is the implementation the same for nonprofits in all countries? The technical implementation is identical. What varies is whether it's legally required (EU/EEA/UK: yes; other regions: varies by local law). The recommendation is to implement it regardless of location, as privacy regulations are expanding globally.
Key Takeaways
- Required for EU/EEA/UK targeting since March 2024; recommended globally
- Advanced mode (recommended) models conversions from denied-consent visitors
- Choose a free CMP (Cookiebot or CookieYes) and install via GTM or WordPress plugin
- Set default consent to "denied" for EU visitors; your CMP updates it when they accept
- Impact is manageable: 10-30% fewer direct conversions, mostly recovered through modeling
- Smart Bidding accounts for modeled conversions automatically
- Test your implementation using GTM Preview mode and your CMP's tools
Published: March 2026 | Last Updated: March 2026 | Author: GrantMax Category: Tracking & Reporting | Tags: Conversion Tracking, Compliance