> 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/jentis-dcp-elements/tags/how-to-configure-a-tag/essential-mode.md).

# Essential Mode

With the [Essential Mode](https://jentis.atlassian.net/wiki/spaces/DD/pages/842727535) enabled in your JENTIS Tag Manager you will get new configuration options in a tag.

Now a tag has two columns for each tag field configuration. The following toggle-button will show/hide the settings (this button is not activating any functionality but simply a visual element to the UI):

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2Fgit-blob-f47d6ecf196c6f6866210e8b9830cc2e031807d4%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>

Each value of a parameter can be treated according to the consent of a user. Instead of configuring a tag twice (with two different triggers that act on consent and without) this makes each tag configuration more convenient. Simply select all parameters that must be anonymized or pseudonymised in the “Essential Mode Value” column.


---

# 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/jentis-dcp-elements/tags/how-to-configure-a-tag/essential-mode.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.
