> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/consent-center/how-jentis-handles-consent/jentis-cmp-connectors.md).

# CMP Connectors

### Native CMP Connectors in JENTIS

JENTIS offers **convenient, easy-to-use native connectors** to all major Consent Management Platforms (CMPs). These connectors make it simple to integrate your CMP with JENTIS, ensuring your tracking setup is always compliant with user consent decisions.

**Examples of available native connectors** (list constantly growing):

* OneTrust
* CookieBot
* Usercentrics
* Borlabs Cookies (WordPress)
* Datareporter
* Truendo
* CookieFirst
* Consentmanager
* iubenda
* Commanders Act (TrustCommander)
* Sourcepoint
* Clickskeks
* CCM19
* Didomi
* DC-Shopsystem
* Shopware Cookie Consent Manager

#### How the JENTIS CMP Connection Works

When you use a third-party CMP, JENTIS creates a **native communication stream** in the background. This connection is **managed, developed, and maintained by JENTIS**, so you can rely on your tracking to always align with your CMP’s consent decisions.

This native connection ensures that both:

1. **Explicit consent updates** – changes a user makes in real-time
2. **Existing stored consent** – consent decisions saved from previous sessions

…are applied correctly in your tracking setup.

#### Technical Details

JENTIS connects to available APIs provided by your CMP—such as event listeners, cookies, or local storage—based on the provider’s documentation. These APIs are used to **synchronize consent data** with the JENTIS Tag Manager, ensuring both real-time and persisted consent information is respected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jentis.com/consent-center/how-jentis-handles-consent/jentis-cmp-connectors.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.