← Back to blog
GCMGuide

Google Consent Mode v2: the complete guide for Webflow

Everything you need to know about GCM v2 and how to set it up correctly.

t

theConsent Team

· 6 min read

If you run Google Analytics or Google Ads, Google Consent Mode v2 is no longer optional in the EEA. Here's what it is and how to implement it.

The four signals

GCM v2 introduces two new signals on top of the original v1:

  • ad_user_data — whether user data can be sent to Google for advertising
  • ad_personalization — whether personalized ads are allowed

Plus the existing v1 signals:

  • ad_storage
  • analytics_storage
  • functionality_storage
  • personalization_storage
  • security_storage

Default vs update

You must call gtag('consent', 'default', {...}) before any GA4 or Ads tags load. After the user makes a choice, call gtag('consent', 'update', {...}).

How theConsent does it

theConsent emits the defaults synchronously on script load. This means even if your GA4 tag is <script async>, the defaults are already in dataLayer by the time the tag fires.

Set up in three clicks: Banner Builder → Behaviour → toggle "Google Consent Mode v2".