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

# Google Tag Manager

Connect GTM so AdPage can read your tags, triggers and variables and audit your tracking setup.

Connect Google Tag Manager so AdPage can read how your tracking is actually built: which tags fire, on what triggers, using which variables. This is what turns "your conversions look low" into "this tag has no trigger".

Unlike the other integrations, GTM has **two access levels**, and the difference matters.

### Read-only or edit

| Level                   | Scope requested              | What it allows                                                                                          |
| ----------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Read-only** (default) | `tagmanager.readonly`        | Read tags, triggers and variables. Audit your setup. AdPage cannot change anything.                     |
| **Edit**                | `tagmanager.edit.containers` | Everything above, plus reading the server container configuration and creating containers during setup. |

Read-only is the default and is enough for auditing. Edit access is requested only when AdPage is provisioning server-side tagging for you, because the server container snippet cannot be read without it.

{% hint style="warning" %}
**Edit access is real edit access.** Granting it means AdPage *can* write to your containers. It is used for the setup steps you asked for, but if you are not in the middle of a server-side tagging project, connect read-only.
{% endhint %}

### Before you start

You need a Google account with at least **View** permission on the GTM containers you want to read — or **Publish** on the account if you are granting edit access for a server-side setup.

As with every Google platform, the access belongs to the account you approve with, and all three Google integrations share it.

### Connect Google Tag Manager

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **Google Tag Manager** tile.
{% endstep %}

{% step %}

#### Approve access at Google

Select connect. Read the consent screen before approving: it names whether AdPage is asking to *view* or to *manage* your containers. That is the read-only/edit difference, in Google's own words.
{% endstep %}

{% step %}

#### Choose your containers

AdPage lists your GTM accounts and, per account, their containers. Expand an account, tick the containers that belong to this AdPage container, and save.

Connect both the **web** container and the **server** container if you run server-side tagging — they are separate containers and both carry part of the picture.
{% endstep %}
{% endstepper %}

### What you get

A readable inventory of your tracking setup, and the checks built on top of it:

* **GTM audit** — tags without triggers, duplicate conversion tags, tags still pointing at a decommissioned endpoint, and consent settings that silently block firing.
* **Answers about your own setup.** Ask the Data Assistant which tag sends your purchase event, or what fires on the checkout page, instead of clicking through the GTM interface.
* **Setup support.** When something is not being measured, support can see the cause rather than asking you for screenshots.

### Reading the numbers

**AdPage reads the live version.** Changes sitting in a workspace, unpublished, are not what your visitors get and are not what the audit reflects. If you fixed something and the audit disagrees, check whether it was published.

**A tag existing is not a tag firing.** The audit reads configuration, not traffic. A correctly configured tag can still be blocked by consent mode, a browser, or a condition that is never met. To see what actually arrived, use **AdPage Tracking**.

### Troubleshooting

**No containers appear.** The approved Google account has no GTM access. Check in Tag Manager under **Admin → User management**.

**The server container configuration is missing.** That requires edit access. Reconnect and grant the higher level — read-only genuinely cannot retrieve it.

**The tile says the connection expired.** Reconnect. Check Google Analytics and Google Ads too: one Google access covers all three.

**The audit flags something you deliberately did.** The audit reports patterns that are usually mistakes, not always mistakes. If a finding is intentional, say so to support and it can be excluded.

Still stuck? Contact <support@adpage.io> with the container and the GTM container ID (`GTM-XXXXXX`).


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adpage.io/data-and-insights/marketing-integrations/google-tag-manager.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.