How to establish a CMP Connection
How to Establish a CMP Connection
To use a CMP (Consent Management Platform) connection in JENTIS, you simply need to connect two elements:
Which JENTIS Tag Manager (JTM) container will use which CMP connection
Which tool/vendor in JENTIS is mapped to which category or unique identifier in the CMP’s API
This section will guide you through the setup process.
1. Container–CMP Connection
The first step is to navigate to Legal Hub → Consentbars in your JENTIS account. Here, you will see a list of available third-party CMP connections.
Open the edit screen for your chosen CMP.

Select the JENTIS Tag Manager container you want to connect.

This step establishes the communication link for consent information on the corresponding website.
Note: This connection is mandatory to activate tracking in a JENTIS Tag Manager container. If you do not connect a CMP (and do not use the JENTIS Consent Engine), no data will be processed by your JENTIS Data Capturing Platform.
2. Vendor and Tool Mapping
The mapping of consent is always a 1:1 relationship between JENTIS and the CMP. Depending on the CMP and your setup, consent can be mapped:
By category – A group of tools in JENTIS is mapped to a corresponding CMP category
By tool/vendor – Each JENTIS vendor is mapped to a specific vendor ID in the CMP

Mapping by Category
In the advanced settings of a tool, you can select the vendor category. This category is then linked to the CMP’s category.
Mapping by Tool/Vendor
For CMP connections that operate at tool level:
Map the vendor in JENTIS to the vendor ID in the CMP.
If applicable, select a specific category for that tool.
Tip: Accessing a tool’s CMP ID can sometimes be challenging, as not all CMPs provide public documentation. In most cases, JENTIS predefines these mappings because CMP IDs are static. If you are unsure, contact JENTIS Customer Support.

✅ Summary:
Connect your JENTIS container to a CMP via Legal Hub → Consentbars
Map tools/vendors to CMP categories or vendor IDs
Ensure the mapping is correct for accurate and compliant tracking
Last updated
Was this helpful?