Google Consent Mode Integration

AdSimple Consent Manager – CMP Partner Validation

Overview

This document demonstrates the successful integration of Google Consent Mode v2 using the AdSimple Consent Manager (CMP). The validation includes both gtag.js and Google Tag Manager (GTM) implementations and shows how consent signals are correctly passed to Google before and after user interaction.

Implementation Details

CMP Name AdSimple Consent Manager
Consent Mode Google Consent Mode v2
Integration Type gtag.js + Google Tag Manager
Website Domains ipl-haarentfernung.at (gtag.js), familylife.at (GTM)
Tested In Chrome Incognito Mode + DevTools Console

Validation 1: gtag.js Integration

Domain: ipl-haarentfernung.at

Setup

  • GA tracking implemented via gtag.js
  • CMP configured to inject Google Consent Mode script

Validation Steps

  1. Before interaction:
    window.google_tag_data.ics.entries
    Result:

    {
  ad_storage: { default: "denied", update: false },
  analytics_storage: { default: "denied", update: false },
  ad_user_data: { default: "denied", update: false },
  ad_personalization: { default: "denied", update: false }
}
  2. After clicking “Accept all”:
    Result:

    {
  ad_storage: { update: true, implicit: true },
  analytics_storage: { update: true },
  ad_user_data: { update: true },
  ad_personalization: { update: true }
}

Validation 2: GTM Integration

Domain: familylife.at

Setup

  • GA4 implemented via Google Tag Manager
  • Consent Mode initialized via CMP or HFCM snippet

Validation Steps

  1. Before interaction:
    window.google_tag_data.ics.entries
    Result:

    {
  ad_storage: { default: "denied", update: false },
  analytics_storage: { default: "denied", update: false },
  ad_user_data: { default: "denied", update: false },
  ad_personalization: { default: "denied", update: false }
}
  2. After accepting cookies:
    Result:

    {
  ad_storage: { update: true },
  analytics_storage: { update: true },
  ad_user_data: { update: true },
  ad_personalization: { update: true }
}

Consent Purposes Used

  • ad_storage
  • analytics_storage
  • ad_user_data
  • ad_personalization
  • url_passthrough (enabled)

Use of wait_for_update Parameter

The AdSimple CMP implementation follows the recommended consent signal sequence by setting denied values by default and updating them only after explicit user interaction.

After technical evaluation, the wait_for_update parameter was deemed unnecessary in this setup. Google tags are only triggered after the CMP updates the consent status, ensuring accurate and compliant behavior without timing conflicts.

This results in a clean and reliable Basic Mode setup, where the Consent Mode logic is applied efficiently without race conditions or premature tag firing.

Mobile SDK

No mobile SDK is available. The AdSimple CMP is currently web-only.

Banner Configuration and UI Template

The AdSimple Consent Manager offers a fully configurable graphical interface that allows clients to customize the appearance, behavior, and text of their consent banner.

The default banner template includes:

  • A clear explanation of the purpose of data collection
  • A link to Google’s privacy page: https://business.safety.google/privacy/ – accessible directly from the banner
  • Visible consent options, including an affirmative action (e.g., “Accept all” button)

Clients are encouraged to use this template when enabling Consent Mode outside the TCF framework.

Consent Mode Type

The AdSimple CMP uses the Basic Consent Mode implementation. In this mode, no Google tags (such as GA4 or advertising tags) are fired before the user gives explicit consent.

All tags are conditionally triggered only after consent is granted, ensuring full compliance with the Basic Consent Mode specification.

This setup avoids premature data collection and ensures that no marketing or analytics data is transmitted before the user makes a choice in the consent banner.

Global Consent Mode Activation

The AdSimple Consent Manager ensures that Google Consent Mode is globally active across all regions. No geolocation-based logic is used to suppress or alter the consent banner.

All visitors – regardless of their country or location – are presented with the consent dialog, and Google Consent Mode is applied consistently on all pages and for all users.

Reference to Google Documentation

To ensure transparency and alignment with best practices, the implementation and validation of the AdSimple Consent Manager follow the official documentation provided by Google.

Summary

The AdSimple CMP meets all requirements for Google Consent Mode v2. It:

  • Initializes denied values by default for all required purposes
  • Sends update signals based on user interaction
  • Supports both gtag.js and GTM setups
  • Allows full consent signal validation via console inspection

Validation video: https://youtu.be/KHbmDirBDgU