Skip to content

Guide 102 · Container · GA4 + Tag Manager

Save, name and restore container versions: the snapshot that lets you roll back

Checked 11 November 2026 · Verification: container fragment validated structurally (16 checks, all passed) · Steps traced to Tag Manager Help, opened 11 November 2026 · 5-minute read

A version is a snapshot of a container configuration at a particular time. Google's publishing page says you can save the current state of a workspace as a version at any time, and that versions make it easier to recover from mistakes — if someone publishes a container version before it is ready, you can revert to an earlier version and publish that instead. Every publish records a version automatically; a named version saved before publishing is the snapshot you can point at later. This guide saves one, names it properly, and restores an older one.

Expected signal

After step 2, the Versions tab lists the new version with the name and description you wrote. After step 4, the container's latest version is the older snapshot, and the bad publish is no longer the version the site loads — until you publish again.

Download the container fragment: the version snapshot fragment (JSON) (export format version 2, 1492 bytes, MD5 94eb15a1a1d28cae97aca8c162888a6b). It holds the container state being snapshotted: the Google tag on Initialization plus a GA4 scroll event tag on a scroll depth trigger. The file is a hand-built import template, validated structurally — it was not exported from a live container.

What you need

  • A workspace with changes in it. A version snapshots the workspace's current state, so there must be something to snapshot — the Google tag from the snippet guide is enough.
  • Approve access or higher. Users with Approve access or higher can create versions. Edit access alone can change the workspace but cannot save it as a version.
  • A name that says what changed. The version name and description are the only record of what the snapshot holds. Write the business change, not the mechanics.

The trace

  1. Click Submit in the workspace. Submit sits at the top right of the workspace. The Submit Changes screen offers two options: Publish and Create Version, or Create Version on its own. Choose Create Version to save the snapshot without putting it live.
  2. Enter a Version Name and a Version Description, then click Create. Name it after the change — GA4 scroll tracking added, not Version 2 — and put the full list of changes in the description. The version is numbered automatically: a new container starts at version 1, so after 3 publishes the container sits at version 1 + 3 = 4.
  3. Find the version on the Versions tab. The Versions tab lists every saved and published version in order, newest first. The snapshot is now stored whether or not it is ever published.
  4. To undo a bad publish, restore the older version. On the Versions tab, open the good version and select Set as Latest Version. That replaces the current container version with the previously saved one — the whole container state, not a single tag — and the restored version becomes the latest. Publish it to put the older state live, which is the publish guide.

Dead ends

DEAD END — A VERSION WITH NO NAME. An unnamed version is a snapshot nobody can identify. Three months after the fact, Version 14 says nothing about what it held, and the rollback decision gets made by guessing. The name is the rollback tool.

DEAD END — RESTORING WITHOUT CHECKING WHAT ELSE CHANGED. Set as Latest Version replaces the entire container state. Restoring a version from last month also restores last month's tags, triggers and variables — including any that were deliberately deleted since. Review the version's changes first.

DEAD END — EDIT ACCESS TRYING TO SAVE A VERSION. Edit access lets you change the workspace, but only Approve access or higher can create versions. An Edit user who clicks Submit and finds no Create Version option is not looking at a bug — the permission is missing.

End state

One named snapshot saved, the Versions tab holding the full history in order, and the restore path known: Set as Latest Version, then publish. The version the site loads is still the last published one until a publish happens.

Sources

Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened 11 November 2026. No step in this guide was run inside a live Analytics property or a live Tag Manager container, because both need a Google sign-in and this site does not sign in as anyone. The container file was validated structurally instead: export format version 2, every tag's firing trigger resolves, every variable the tags reference exists in the file, and the tag types are the documented ones. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map. The container fragment for this guide is 1492 bytes (1.46 KB, 0.73% of the reported 200 KB container size limit), MD5 94eb15a1a1d28cae97aca8c162888a6b, and passed 16 structural checks.