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

# Google Tag Manager Integration

> Fueled's Google Tag Manager Integration, as well as its data layer and data layer listeners, are available on all of our Shopify plans.

Learn more about working with our data layer and exposing it to Google Tag Manager variables and tags at:

{% content-ref url="/pages/ZSY7ECOW7NtnKmDGjZKN" %}
[Working with Fueled’s Shopify Data Layer](/apps/shopify/shopify-event-tracking/working-with-fueleds-shopify-data-layer.md)
{% endcontent-ref %}

### GTM Container Template

You can also get started with the following sample Google Tag Manager Container configuration.

{% hint style="success" %}
Note: The following GTM Tags, Triggers and Variables are provided as is, without warranty. Occasionally, we may update this GTM container snippet. It's the merchant's responsibility to manage this recipe.

Also, please be sure respect your customers' privacy and implement consent mode in GTM. Compliance with privacy laws is the responsibility of the merchant.
{% endhint %}

To use this template, download the json file below and then upload it into a GTM container. Be sure to pay attention to any tag, trigger, or variable names that are shared, so as not to override existing work in GTM.

{% embed url="<https://gist.github.com/seanberto/fc3144f2c6f152994d84b6c16936b28c>" %}


---

# 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://learn.fueled.io/apps/shopify/google-tag-manager-integration.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.