> 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/final-steps.md).

# Final Steps

The final step in the impact.com tag placement journey is to publish the GTM container. Doing this will publish your tags to your production or staging environment, wherever you have placed the GTM tags. If you are deploying to your production environment, you will have to move the GTM tags to your production site pages.

You have options to [configure different environments](https://support.google.com/tagmanager/answer/6311518) from within GTM. For example, if you wanted different environments to test like "Staging" and a production environment, "Live".

## Steps to implement

Follow the steps below to publish your GTM container.

1. Select **Publish and Create Version** at the top of your GTM container.
2. Optionally, give the version a name as well as a description for the workspace changes.
3. Optionally, select the environment. If you are moving from staging to live, this step is required.
4. Select **Publish**.

<div data-with-frame="true"><figure><img src="https://files.readme.io/15d6d68-CA329879-C072-4597-B7BA-E384B05073C8.png" alt="" width="563"><figcaption></figcaption></figure></div>

### End-to-End Testing

Once the impact.com app is fully installed, you can begin end-to-end testing to ensure everything is working properly. Learn how to proceed with [End-to-End Testing](/integration-guides/end-to-end-tests.md).


---

# 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://integrations.impact.com/integration-guides/for-brands/tracking-integrations/google-tag-manager/final-steps.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.