> 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/privacy-documentation/jentis-and-privacy-use-cases/jentis-and-google-tag-manager.md).

# JENTIS and Google Tag Manager

As a general rule, Google Tag Manager (GTM) on both client and server side always requires user consent to comply with Art.25(1) TTDSG. It cannot be argued that GTM is used on the basis of "strict necessity" because the data is being accessed by a 3rd party (Google) and it can be used for its own purposes (different from the purposes of the website operator).

The main challenge with the GMT is to leverage data in both consent scenarios (with consent and without consent of users). Using GMT without any additional data protection measures is connected to high regulatory risk. Without consent of a user the website operator when relying on GMT is faced with a choice:

* completely stop tracking data that is not connected to user consent; or
* find a technical solution to enable compliant capture of first party data.

JENTIS as proxy solution for GMT provides a compliant way to capture data not connected to user consent in the first party context on client side and direct it to Google in the server side. In this case, the website operator has a possibility to minimise and modify data parameters to the extent it then falls under the ePrivacy consent exception in the first party context and only then share selectively the modified data parameters with Google.

***

For any questions, feel free to reach out to your direct contact at JENTIS or to the JENTIS Compliance & Legal Team via email at <privacy@jentis.com>.


---

# 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/privacy-documentation/jentis-and-privacy-use-cases/jentis-and-google-tag-manager.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.