Google Consent Mode – Vendor Settings

In this article we will delve deeper into the topic of Google Consent Mode and the corresponding vendor settings in the JENTIS Data Capturing Platform (DCP). Our focus is on how to activate the right settings for all Google Tags in both your client-side and server-side configurations.

If you are new to the subject and would like to understand the fundamentals of how JENTIS and Google Consent Mode work together, please read the introduction guide first: 👉 Google Consent Mode Guide with JENTIS and Essential Mode

Why This Matters

Correctly configuring Consent Mode is crucial to:

• Ensure compliance with legal requirements (GDPR, ePrivacy).

• Control how Google services behave before and after consent.

• Keep data collection consistent across tags, vendors, and execution environments.

Use Cases at a Glance

This article covers three main use cases for configuring JENTIS vendor settings with Google Consent Mode (Version 2):

1. Basic Use of JENTIS Vendor to Consent Mode Setting

   • Direct mapping of Google-related vendors inside JENTIS.

2. Mapping Consent for Custom Vendor Configurations

   • Linking your Consent Management Platform (CMP) settings to JENTIS vendor definitions.

3. Mapping CMP-Based Consent Mode Information with JENTIS

   • Passing CMP consent signals through JENTIS to Google.

Key Preconditions & Settings

Before implementing, be aware of the following factors that determine how your configuration behaves:

1. Google Tag – Consent Mode Signals

• Update vs. Default settings Which application provides Consent Mode signals (update and default) to gtag()?

  • CMP

  • Your website

  • JENTIS

It is essential to define the source clearly, otherwise conflicting consent updates may occur.

2. Tag Execution

Consider where your Google tags are executed:

• Client-side (in the browser)

• Server-side (via JENTIS Server Tagging)

• Hybrid (a mix of both)

Each execution layer may require different configurations and consent mappings.

Use Case Scenarios

Use Case 1: Client-Side Tag with Consent Mode in JENTIS

• Google tags execute in the browser.

• Consent Mode settings are applied via JENTIS vendor configurations.

• JENTIS ensures correct propagation of consent signals (ad_storage, analytics_storage, etc.) to gtag().

Use Case 2: Client-Side Tag without Google Vendor

• Tag executes client-side but is not tied to a standard Google vendor in JENTIS.

• You configure Consent Mode manually in JENTIS.

• Useful for custom setups where Google services are embedded indirectly.

Use Case 3: Server-Side Tags with CMP/JENTIS Consent Mode

• Tags execute on the server (through JENTIS).

• Consent Mode information can come from:

  • CMP (direct push)

  • JENTIS (mapped vendor consent)

• Requires careful mapping to ensure signals passed downstream to Google remain consistent.

Next Steps

• Define your consent source of truth (CMP, JENTIS, or direct website integration).

• Decide on execution type (client, server, or hybrid).

• Configure JENTIS vendor settings accordingly.

• Test in preview mode to confirm signals are sent correctly.