Use Case 3 – Server-side and CMP Based Google Consent Mode Settings Alignment
In this use case, we address how to align Consent Management Platform (CMP) settings with JENTIS vendor configurations when working with Google Consent Mode in a mixed client-side and server-side setup.
CMP-Driven Consent Mode Updates
Some CMPs provide built-in features to submit Consent Mode signals directly to the Google Tag client side. This can be a valid setup, and in such cases you may not need additional configuration in JENTIS for client-side Consent Mode.
However, server-side tags (GA4, Google Ads, Floodlight, etc.) rely exclusively on JENTIS vendor settings. Therefore, you must configure Consent Mode settings in the JENTIS DCP to ensure that server-side tags apply the correct information.
Why Alignment is Required
When multiple tags operate in parallel (client-side and server-side), alignment between CMP and JENTIS becomes critical:
CMP may push Consent Mode updates to the Google Tag.
JENTIS must mirror those same mappings to handle server-side executions.
If JENTIS and the CMP use different mappings, your server-side Google Tags will not reflect the correct consent status.
👉 The recommended approach is to apply the same mapping in both your CMP and in JENTIS.
Example: Mapping with Usercentrics
Different CMPs handle Consent Mode mapping differently. For example, Usercentrics provides a mapping approach documented here: Usercentrics Google Consent Mode Guide
In this guide:
Analytics Service → mapped to Google Analytics
Ads Service → mapped to Google Ads Remarketing
The CMP then generates the following signal in its code example:
ad_storage: e.detail[ucAdService] ? 'granted' : 'denied'
To align with JENTIS:
Vendor Google Analytics 4 in JENTIS must be mapped so that when consent is granted, it applies:
analytics_storage: granted
If denied, it must apply:
analytics_storage: denied
This ensures that both your CMP and JENTIS consistently communicate the same consent state to Google.
Mandatory for Server-Side Execution
This vendor configuration in JENTIS is not optional. Without it:
Server-side tags cannot execute correctly.
Google will not receive the required consent status.
For server-side tags, the JENTIS vendor configuration is always the single source of truth.
Client- and Server-Side Alignment – Possible Issues
When CMPs also push Consent Mode signals to the client-side, the following issues can arise:
JENTIS vendor mapping not activated
If the Consent Mode settings are not enabled for a vendor in JENTIS, server-side tags will not respect consent.
JENTIS and CMP mappings not aligned
If the CMP says
analytics_storage: granted
but JENTIS has no equivalent mapping, the server-side Google Tag will fail to send the correct signal.
Assumption of client-to-server propagation
JENTIS does not read CMP signals from the client-side to apply them server-side.
Server-side consent is derived only from the JENTIS vendor configuration.
Key Takeaway
To ensure smooth operation in a mixed client-side and server-side setup:
Always configure Google Consent Mode mappings in JENTIS vendors.
Mirror the exact same mapping that exists in your CMP.
This way, both the CMP and JENTIS deliver consistent and synchronized consent signals to all Google Tags, regardless of where they execute.
Last updated
Was this helpful?