> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/web-tools/tag-manager/version-history.md).

# Version history

Tag Manager Version History records each published workspace version with its changes, author and date.

The **Version History** page provides a full record of changes made in your Tag Manager workspace. Each version represents a snapshot of your workspace at the time of publishing, including all tags, triggers, and variables.

This ensures that you can:

* Track what changes were made, by whom, and when.
* Roll back to previous versions if needed.
* Maintain accountability and transparency across your team.

### Step 1: Open Version History

From your **Workspace**, select **Version History**.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FMcI7D42Nuakjg4vjcWVu%2FScreenshot%202025-09-23%20at%2014.28.36.png?alt=media&#x26;token=c41c8e4c-320c-4fb5-9a80-88ee818f414a" alt=""><figcaption></figcaption></figure>

### Step 2: Review Versions

At the top of the page, you will see a summary:

* **Live Version** – the currently published version number and who published it.
* **Tag Count** – total number of tags in the workspace.
* **Trigger Count** – total number of triggers in the workspace.
* **Variable Count** – total number of variables in the workspace.

Below the summary, a table lists all published versions with:

* **Version** – the incremental version number.
* **Release Note** – description of what was changed in that version.
* **Published at** – timestamp of when the version was published.
* **Published by** – the team member who published the version.
* **Actions** – options to view, compare, or roll back.

The latest version is marked as **LIVE**.

### Step 3: Use Actions

For each version, you can:

* **Fork** – Create a copy of that version to use as a starting point. This is useful if you want to branch off an older version without overwriting it.
* **Publish** – Make that version the **live workspace**. This overwrites the current live version with the selected one.
* **Preview** – Test the selected version before publishing. This allows you to validate tags, triggers, and variables in a safe environment.

### When security review is enabled

If [Security review](/netmera-user-guide/web-tools/tag-manager/security-review.md) is enabled for your app, Version History also tracks the approval state of each version.

Versions carry one of three statuses:

* **Waiting Review** – submitted and waiting for a Security Reviewer decision.
* **Live** – approved and published.
* **Rejected** – reviewed and declined. Can be edited and sent to review again.

Actions change accordingly:

* **Publish** is no longer available as a direct action. The only route to production is an approval.
* **Review Actions** appears for Security Reviewers and opens the Approve / Reject panel.
* **Fork** and **Preview** remain available to all roles, including on a version waiting for review.
* **Download Version** appears for Security Reviewers on every version.

The version waiting for review is listed first, with the live version below it.


---

# 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://user.netmera.com/netmera-user-guide/web-tools/tag-manager/version-history.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.