Use Case 1 – Basic Use of Vendor Consent Mode Mapping
Last updated
Was this helpful?
In this use case we look at the basic integration of Google Consent Mode via the JENTIS Vendor settings. This enables JENTIS to submit consent information to the Google Tag client side (gtag) based on vendor consent.
To activate this optional feature, you must customize your vendors in JENTIS:
Navigate to Legal Hub → Vendors in your JENTIS account.

Select a Google-related vendor (e.g. Google Analytics 4, Google Ads) or any custom vendor.
Configure its Consent Mode mapping options.

Once activated, this setup will affect all your client-side executed Google Tag libraries, including:
GA4
Google Ads
Other gtag-based services
✅ It works regardless of whether the tag was loaded by JENTIS or another system.
Consent Mode updates can be triggered from multiple sources:
Your Consent Management Platform (CMP)
Your Website directly
JENTIS
All three can submit the same consent signals to Google simultaneously. As long as the signals are not contradictory (all push “granted” or all push “denied”), there is no issue with multiple pushes.
When editing a vendor (for example, Google Analytics 4), you will find options to activate individual Consent Mode strings.
If the vendor receives consent and the corresponding checkboxes are activated, JENTIS will automatically submit the matching consent signals to Google:
Analytics storage
Ad storage
Ad user data
Ad personalization
The value sent will depend on the vendor’s consent state:
✅ Granted → signal is “granted”
❌ Denied → signal is “denied”
⚠️ If a checkbox is not selected, JENTIS will not link this vendor’s consent status to that Consent Mode setting.
If you do not wish to submit any Consent Mode information from JENTIS, simply leave all checkboxes unticked.
In this case:
Consent Mode signals are not managed by JENTIS.
JENTIS tracking and Google Consent Mode operate independently.
Last updated
Was this helpful?
Was this helpful?