How to Set Up Consent Mode v2 in Webflow (GDPR & GA4 Ready)

With stricter privacy regulations across the EU, implementing Consent Mode v2 is no longer optional. If your website uses Google Analytics 4 or Google Ads, you must ensure user consent signals are properly configured. If you're building in Webflow, this guide will walk you through the setup step by step GDPR-compliant and future-proof.

Read time:
2 minutes
Author:
Bojana Djakovic
Published:
February 23, 2026

What Is Consent Mode v2?

Consent Mode v2 is Google’s updated framework that allows websites to communicate user consent preferences to Google services.

It controls how tags behave based on whether users accept or reject:

  • ad_storage
  • analytics_storage
  • ad_user_data
  • ad_personalization

Without it, you risk:

  • Incomplete GA4 tracking
  • Google Ads data loss
  • Compliance issues in the EU

Before You Start

You’ll need:

  • A GA4 property
  • A Google Tag (gtag.js) or Google Tag Manager
  • A cookie consent banner
  • Access to Webflow site settings (custom code section)

Add Google Tag to Webflow

In Webflow:

Project Settings → Custom Code → Inside <head>

Paste your Google tag snippet from GA4.

It looks like this:

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
</script>

Set Default Consent State

Before any tracking runs, define default consent as denied:

<script>
gtag('consent', 'default', {
 'ad_storage': 'denied',
 'analytics_storage': 'denied',
 'ad_user_data': 'denied',
 'ad_personalization': 'denied'
});
</script>

This ensures compliance until the user makes a choice.

Connect Consent Banner to Consent Mode

Your cookie banner must trigger consent updates.

When the user clicks “Accept”, run:

gtag('consent', 'update', {
 'ad_storage': 'granted',
 'analytics_storage': 'granted',
 'ad_user_data': 'granted',
 'ad_personalization': 'granted'
});

If the user rejects:

gtag('consent', 'update', {
 'ad_storage': 'denied',
 'analytics_storage': 'denied',
 'ad_user_data': 'denied',
 'ad_personalization': 'denied'
});

This can be triggered via:

  • Custom JavaScript
  • Or through Google Tag Manager triggers

Test in GA4

Open:

GA4 → Admin → DebugView

Or use:

  • Google Tag Assistant
  • Browser DevTools → Network tab

Make sure:

  • No analytics fires before consent
  • Events fire only after acceptance

Add Advanced Consent Signals (EU Required)

For EEA traffic, Google now requires:

  • ad_user_data
  • ad_personalization

These must be explicitly passed.

If not implemented correctly, Google Ads remarketing may stop working.

Common Mistakes to Avoid

  1. Loading GA4 before default consent
  2. Forgetting to update consent on button click
  3. Not testing in real-time
  4. Using a cookie banner that doesn’t integrate with gtag

Should You Use a CMP?

For full GDPR compliance, consider a Consent Management Platform (CMP).

Examples:

  • Cookiebot
  • OneTrust
  • Complianz

These tools integrate directly with Google Consent Mode v2 and simplify legal compliance.

Setting up Consent Mode v2 in Webflow is not complicated  but it must be done correctly.

When properly configured, you:

  • Stay GDPR compliant
  • Preserve GA4 tracking accuracy
  • Maintain Google Ads performance
  • Avoid legal and advertising disruptions

For EU-facing businesses, this setup is no longer optional it's infrastructure.

Back to blog page