> 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/vendor-consent-settings.md).

# Vendor Consent Settings

In **JENTIS Tag Manager**, every vendor has a dedicated **Consent Settings** option.\
These settings determine **how and when** a vendor’s tools are activated, based on your consent configuration.

This allows you to control whether a vendor’s tools require user consent before running, and if so, how they behave in different consent scenarios.

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2F73I1KMbNPuLNCJs2S1xH%2Fimage.png?alt=media&amp;token=6be6fca5-bbf1-4eb9-95d2-1b957bb3073f" alt=""><figcaption></figcaption></figure>

### Available Modes

#### 1. Consent Mode

* **Behavior:** Tools linked to this vendor activate **only after user consent is received**.
* **Use case:** When you must strictly follow the user’s opt-in decision for compliance.

#### 2. Essential Mode

* **Behavior:** Allows a **split configuration** for each tag in this vendor’s tools:
  * One configuration when **consent is given**
  * Another configuration when **consent is denied**
* **Use case:** When essential functions must still run without full tracking, but enhanced features should only run after consent.

#### 3. No Consent Mode

* **Behavior:** The tool activates **immediately**, regardless of user consent.
* **Use case:** For tools that are legally permitted to run without consent (e.g., certain strictly necessary services).

✅ **Tip:**\
Carefully review the legal requirements in your jurisdiction before choosing **No Consent Mode**. This ensures that your configuration remains compliant with applicable data protection regulations.


---

# 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/vendor-consent-settings.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.