> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/tag-manager/publish/publish-to-the-staging.md).
# Publish to the Staging
## Introduction
After creating any elements, you must first publish to the Staging Environment and then in the Production environment.
## Procedure
To publish the tag to Staging, perform the following steps:
**Step 1:** Select **Publish** from the left navigation panel.
**Step 2:** Click the staging tab.
**Step 3:** Click **Publish to Staging**.
**Step Result**: The *Publish to Staging* screen appears. Any newly created elements remain in a pending publish status, and you can view them here on this screen.
**Step 4:** Select the element and click **Review** on the top-right corner of the screen.
**Step 5:** Enter the Publishing Name in the **Name** field and provide **Description.**
**Step 6:** Review the tags that are selected and click **Publish to Staging**.
**Step 7:** Click the refresh icon on the top right to change the status from Publish to Staging->Queued->Finished->Published.
**Step Result**: The Published tag appears with the Published status.
{% embed url="" %}
---
# 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://docs.ingestlabs.com/tag-manager/publish/publish-to-the-staging.md?ask=&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.
