CMP Integration with Google Consent Mode v2 | Adslytics | Adslytics

Consent Mode How-To Guide

Integrating Your CMP with Google Consent Mode v2

By Muhammad Farooq · April 7, 2026 · 5 min read
Integrating Your CMP with Google Consent Mode v2

Why CMP Integration Matters

A cookie banner that looks correct to users can be completely non-functional from a Consent Mode perspective. If your CMP is not properly integrated with Google Consent Mode v2 — specifically, if it does not call gtag('consent', 'update', ...) when a user makes a choice — your Google tags never receive the consent signal. The result: all users are tracked as if consent was denied, regardless of what they chose in the banner.

Google-Certified CMP Partners

Google maintains a list of CMPs that have been verified to correctly implement Consent Mode v2. These include:

  • Cookiebot (Usercentrics company)
  • OneTrust
  • Usercentrics
  • Complianz (WordPress)
  • CookieYes
  • Didomi
  • TrustArc

Using a Google-certified CMP significantly reduces integration risk — these CMPs publish tested GTM tag templates in the GTM community gallery that handle the consent signal correctly.

The Integration Mechanism

When a user accepts or declines consent in the banner, the CMP must fire:

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

This update must:

  1. Fire on the same page as the consent decision, not just on page reload
  2. Map the CMP's consent categories to the correct Google consent types
  3. Fire correctly on return visits (reading the stored consent choice from a cookie)

CMP Category Mapping

A common integration issue: the CMP uses different category names ("Statistics", "Marketing") that must be correctly mapped to Google consent types:

  • Statistics/Analytics → analytics_storage
  • Marketing/Advertising → ad_storage + ad_user_data + ad_personalization

Verify this mapping in your CMP's Consent Mode integration settings. An incorrect mapping (e.g., Statistics mapped to ad_storage instead of analytics_storage) causes wrong consent signals for wrong Google services.

Verification in GTM Preview

To verify your CMP integration:

  1. Open GTM Preview Mode and browse to your website in an incognito window (no prior consent cookie)
  2. The consent banner should appear
  3. Check the "Consent" tab in Tag Assistant → shows current consent state for all four types (should all be 'denied' initially)
  4. Click "Accept All" in the banner → the Consent tab should update immediately to show all types as 'granted'
  5. Accept only "Analytics" (not Marketing) → analytics_storage should be 'granted', ad_storage/ad_user_data/ad_personalization should remain 'denied'

Summary

CMP integration with Consent Mode v2 requires the CMP to fire gtag('consent', 'update') when users make choices, with correct category mapping. Use a Google-certified CMP with a published GTM tag template to reduce implementation risk. Verify integration in GTM Preview Mode's Consent tab — check that consent state updates immediately when the user interacts with the banner, not only on page reload.

See our Consent Mode v2 Implementation service for CMP integration setup.

Need CMP and Consent Mode integrated correctly? Contact Adslytics.

Need expert tracking setup?

Our Google Tag Manager experts have delivered 500+ tracking setups with a 98% success rate.

Get a Free Consultation →
← Back to Blog
Muhammad Farooq

Author

Muhammad Farooq GTM & Analytics Expert · Adslytics Founder

Tracking specialist with 10+ years of experience in Google Tag Manager, GA4, Server-Side Tracking, and Google Ads. Founder of Adslytics — a dedicated analytics agency with a 98% success rate across 232+ projects on Upwork.

Top Rated Plus LinkedIn Visit the author's profile →