> 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/data-capture/web-tracking-setup/set-up-gtm-data-layer/enable-and-configure-gtm-datalayer-mapping.md).

# Enable and Configure GTM dataLayer Mapping

Connect your Google Tag Manager data layer to JENTIS events and properties. Enable the GTM data layer vendor, then map custom values where needed.

### Enable the GTM data layer with your JENTIS Container

To enable the mapping of GTM `dataLayer` events and properties follow these steps:

1. Open your JENTIS account and navigate to container overview.
2. Select a container and click "Data Layers" in the left hand navigation:\
   ![](https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FM59EchI12qDWDU5Mtkm0%2Fimage.png?alt=media\&token=40ef0f80-05b9-4baf-8bea-180dd703b0b1)
3. If your data layer is not recognized automatically click "Add manually" to add a new GTM data layer mapping.\
   ![](https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2F3y3B0ANFcp3o5YxaEFzC%2Fimage.png?alt=media\&token=10bdb9fc-47c5-4e0a-9ecf-1acde15422a2)
4. Now you can add customizations to your data layer events and properties with JENTIS.

JENTIS displays the data layer mapping interface after activation in the list.

{% hint style="info" %}
How the data layer mapping works: you can map events and their respective properties to JENTIS native data layer pushes (via \_jts.push() API calls). This way you continue using your own data layer with your website while all the default JENTIS tag templates and triggers will work out of the box.
{% endhint %}

### Map events and properties

To customize individual event and parameter mappings select the newly created or existing data layer mapping.

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2Fg5z97cltKxBcr8TNfVwb%2Fimage.png?alt=media&amp;token=f8ec5652-7f1c-4286-97c3-342ffa22204e" alt=""><figcaption></figcaption></figure>

Use the mapping interface to connect GTM data layer values to JENTIS events.

1. Choose the GTM event you want to process.
2. Map the event to the matching JENTIS track-command.
3. Map each required data layer property to its JENTIS key.
4. Save the mapping.

Create mappings for any custom events or properties your implementation uses.

### Default mappings

JENTIS preconfigures mappings for standard GTM page view and ecommerce events.

Review these mappings before publishing. Adjust them only when your data layer differs from the default GTM ecommerce structure.


---

# 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/data-capture/web-tracking-setup/set-up-gtm-data-layer/enable-and-configure-gtm-datalayer-mapping.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.
