> For the complete documentation index, see [llms.txt](https://integrations.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/google-tag-manager/introduction.md).

# Introduction to GTM

{% hint style="info" %}
**What's new:** Incorporate Google Tag Manager with Advocate. Learn how to leverage your GTM integration to [run your referral program on your website](https://integrations.impact.com/integration-guides/for-brands/advocate/advocate-tracking-integrations/integrate-google-tag-manager-with-advocate).
{% endhint %}

Google Tag Manager (GTM) is a tag (pixels, scripts, and tracking code) management system that allows web developers to deploy marketing tags to track advertising performance. It is a free tool used to deploy tags on websites and mobile apps.

For example, information from one data source (your website) is shared with another data source (impact.com) through GTM.

{% hint style="success" %}
**Note:** This guide assumes GTM is configured on your website with the necessary variables outlined in your technical integration plan. The code used in this guide is intended to guide your integration efforts and your developer team should change the code (or use custom code) to best integrate impact.com's tags via GTM for your website.
{% endhint %}

## How it works

With GTM, your website communicates with GTM servers. You can then use the UI to set up tags, establish triggers that cause tags to fire when certain events occur, and create variables for simplifying and automating tag configurations.

The collection of these tags, triggers, variables, and related configurations you've installed on your website or mobile app, is called a container. Containers are used to gather data you want to track or information you want to collect.

## What to expect

This integration guide is simplified into two main steps.

1. Complete the [Installation steps](/integration-guides/for-brands/tracking-integrations/google-tag-manager/implementation.md) on your site.
   * This involves publishing the container, and taking your tags live.
2. Complete an [End-to-End Test](https://integrations.impact.com/integration-guides/end-to-end-tests) on your site.
   * This involves testing the conversion tracking tag, completing a conversion, and previewing the changes.

## Check before integrating

* See [Create an Event Type](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/event-types/create-an-event-type) for the steps to create your UTT event type.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://integrations.impact.com/integration-guides/for-brands/tracking-integrations/google-tag-manager/introduction.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 `build a script that syncs our docs to a CMS` 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.