> For the complete documentation index, see [llms.txt](https://docs.edgetag.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.edgetag.io/channels/google-tag-manager.md).

# Google Tag Manager

Google Tag Manager (GTM) integration allows you to easily load and initialize your GTM container on the website without modifying the site’s code. This integration focuses solely on loading GTM, enabling you to manage and configure your marketing tags directly within the GTM interface, without any additional event tracking or browser data streaming handled by us.

### Details

Channel name:  `googleTagManager`

NPM package: [@blotoutio/providers-google-tag-manager-sdk](https://www.npmjs.com/package/@blotoutio/providers-google-tag-manager-sdk)

### Event Flow

The Google Tag Manager integration loads your GTM container on the website, allowing you to manage all tags, triggers, and configurations directly within your GTM workspace.

The integration works by:

* Loading your GTM container script during page load
* Initializing GTM to manage tag execution based on your configured triggers and settings

{% hint style="warning" %}
We don't handle `dataLayer` for you or add anything to it.
{% endhint %}


---

# 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.edgetag.io/channels/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.
