> 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.md).

# Set up GTM Data Layer

Use GTM window\.dataLayer events in JENTIS without custom code.

## Set up GTM Data Layer

### Introduction

JENTIS natively supports Google Tag Manager's `window.dataLayer`. You no longer need custom code to connect an existing GTM data layer to your JENTIS container.

Keep the data layer implementation already running on your website. Select the GTM data layer vendor, then configure mappings through the JENTIS interface.

A GTM data layer contains objects pushed by your website as visitors interact with it. These objects include an event name and related properties, such as product, cart, transaction, or value data.

JENTIS provides default mappings for standard GTM page view and ecommerce formats. This helps you start tracking quickly with the default GTM ecommerce model.

Customize the mappings when your implementation uses custom event names or properties.

### Before you begin

Your website must already push events to `window.dataLayer`.

{% hint style="info" %}
Remember to remove any custom code or states that translate your dataLayer into JENTIS States or \_jts.push()-calls if you activate the nativly supported data layer mapping. So your mapping is not applied redundantly.
{% endhint %}

JENTIS supports the default GTM ecommerce tracking model. Custom event structures can also be mapped.

### Next steps

Read on to learn how to configure GTM data layer mappings for your container. The following sections describe how to map events and properties in detail.


---

# 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.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.