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

# Google Tag Manager

1. [Login](https://app.engineroom.com.au/login) to your EngineRoom account
2. In the left menu, click on **Integrations**
3. Click **EngineRoom Pixel**
4. Copy the setup code
5. Login to your [Google Tag Manager](https://tagmanager.google.com/) account and navigate to the container installed on your website
6. In the menu on the left, click **Tags**
7. Click **New**
8. Click on the **Tag configuration** box. In the **Choose tag type** list select **Custom HTML**
9. Paste the code snippet on your dashboard in the **HTML** box that appears
10. Click **Advanced Settings** below the box
11. Set the **Tag firing priority** to 100
12. Set the **Tag firing options** to **Once per page**
13. Click the **Triggering** box
14. Under **Choose a trigger,** select **All Pages** to enable EngineRoom to track your entire site
15. Enter "**EngineRoom - Pixel**" as the name for your code in the upper left corner
16. In the upper right corner of the overview click **Submit**
17. Give the new version a descriptive name and click **Publish**


---

# 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.engineroom.com.au/engineroom-pixel/setup/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.