Use Case 2 – Customized Categories and Vendors
In this use case we discuss how JENTIS can submit consent information to Google Consent Mode when working with custom vendors or categories that you define in your Consent Management Platform (CMP).
Why Use Custom Vendors?
In some scenarios you may want to define a custom vendor or custom category in your CMP.
For example, you might create a category called “Analytics Tools” that functions as a surrogate for a Google Consent Mode setting such as analytics_storage
.
This allows you to treat a Google Consent Mode signal just like any other cookie or vendor consent option provided to your users.
Aligning Custom Vendors with JENTIS
To align this setup with JENTIS and the Google Tag (gtag
), follow these steps:
Create a custom vendor in JENTIS:
Go to Legal Hub → Vendors in your JENTIS DCP.
Click Add New Vendor and define the vendor (e.g. “Analytics Tools”).


Map Google Consent Mode settings in this new vendor:
Within the vendor settings, select which Consent Mode strings (e.g.
analytics_storage
) should be tied to this vendor’s consent status.
Link the CMP vendor to the JENTIS vendor:
Ensure your CMP and JENTIS both use this vendor category.
Once consent is granted in the CMP, JENTIS will translate it to the corresponding Consent Mode signal.
✅ Now, when the visitor consents to “Analytics Tools” in your CMP, JENTIS will submit analytics_storage: granted
to the Google Tag.
Example
A custom vendor “Analytics Tools” is created in JENTIS and linked to analytics_storage
.
If the visitor consents to “Analytics Tools,” JENTIS automatically applies:
analytics_storage: granted
If consent is denied, JENTIS applies:
analytics_storage: denied
Resolving Conflicts
You might wonder: What happens if multiple vendors in JENTIS are linked to the same Google Consent Mode setting?
JENTIS resolves this with a “single signal wins” method:
If any vendor linked to
analytics_storage
is granted consent, JENTIS will submit:analytics_storage: granted
Even if other vendors linked to the same setting are denied, one granted signal is enough to set the status as granted.
This ensures that consent signals are consistently passed to Google Tag, without ambiguity.
👉 This approach gives you maximum flexibility in designing your CMP categories while still ensuring a reliable connection to Google Consent Mode through JENTIS.
Last updated
Was this helpful?