Google Tag Manager

GTM Versions and Workspaces: How to Publish Changes Safely

GTM goes live the moment you publish. Workspaces, Preview, version notes, environments, approvals and rollback are the safety net, so here is a routine and a checklist to use every time.

Cover: Publish GTM without surprises. a GTM timeline of numbered container versions with a workspace draft above it, a Preview check gate, and a rollback arrow pointing to the previous live version.

Ad platforms have drafts, reviews and paused states. GTM has none of that once you press Publish: the new version is live for everyone. That makes the process around publishing the only protection you have, and it is cheap to set up.

The pieces, in plain terms

GTM concepts

What each piece does

 What it isKnow this
WorkspaceA draft area for a set of changesFree containers: Default Workspace plus 2 more. Tag Manager 360: unlimited.
VersionA saved snapshot of the whole containerCreated from a workspace with Create Version or Publish and Create Version.
PreviewTests the workspace on your real site through Tag AssistantOnly your browser sees it. You can share a preview link.
EnvironmentA target such as Live, or a custom staging oneCustom environments have their own snippet; Google recommends the standard snippet on production.
ApprovalA Request Approval step before publishingTag Manager 360 only.
PermissionsWho can read, edit, approve or publishContainer levels: No access, Read, Edit, Approve, Publish. Creating versions needs Approve.

How workspaces behave

When you create a version from a workspace or publish it, the workspace is removed, and its name, notes and change list stay with the version. The Default Workspace is recreated. If someone else published while you were working, GTM tells you your workspace is out of date. Choose Update Workspace, review the incoming changes, and resolve each conflict by keeping yours or taking theirs.

Google’s advice is to create a workspace for each set of related changes that will be published together, and to name it well, because the name can become the version name. In practice that means one workspace for "Meta purchase dedup", another for "GA4 lead event", never one called "Ahmed’s changes".

The publish routine

How to

Publish a GTM change safely

Five minutes of routine that saves a day of reverse-engineering.

  1. 01

    Note the live version

    Open Versions and write down the live version number. That is your rollback.

  2. 02

    Check nobody else is waiting to publish

    Compare the latest version with the live one. If a newer unpublished version exists, publishing yours may push someone else’s work too.

  3. 03

    Read the change list

    On the Submit screen, read Workspace Changes line by line. Anything you don’t recognize stops the publish.

  4. 04

    Preview on the real site

    Walk the affected path on desktop and mobile, with consent denied and granted. Each changed tag fires once with filled values.

  5. 05

    Name and describe the version

    Use the template below.

  6. 06

    Publish when someone can watch

    Not at the end of the week. Check GA4 Realtime and each platform’s event view straight after, and again the next day.

  7. 07

    Roll back if numbers move

    Versions, select the previous version, then Publish To from the Actions menu. Fix the draft afterwards with Set as Latest Version.

Version name and description template

Copy this

Version notes that the next person can use

  1. Name
    Date, area and change: "2026-11-19 | Meta | Purchase event ID for CAPI dedup".
  2. What changed
    Tags, triggers and variables added, edited or removed, by name.
  3. Why
    The ticket, the request, or the finding from the last audit.
  4. How it was tested
    Preview path, devices, consent states, and where the events were confirmed.
  5. Rollback
    The version number to publish if numbers move, and who to tell.

If your team keeps a tracking plan, put the row IDs a version implements in its description, so the plan and the container history point at each other. Name versions with the same discipline as campaigns; the logic in ad naming conventions carries over.

GTM publish checklist

Every publish

Before you click Publish

  • Live version number written down as the rollback point.
  • Latest version equals live, or you know whose unpublished work you are about to include.
  • Workspace holds only related changes.
  • Workspace Changes list read in full on the Submit screen.
  • Preview tested on the real site, desktop and mobile.
  • Consent tested denied and granted.
  • Every changed conversion tag fires once with value, currency and IDs filled.
  • Nothing fires on staging or preview hosts.
  • Version name and description filled with the template.
  • The person publishing has Publish rights and is accountable for it.
  • Someone checks GA4 Realtime and platform event tools right after.
  • Numbers checked again the next day against the day before.

Environments, exports and approvals

  • Environments. Admin, Environments, New creates a custom environment with its own snippet for a staging site. Publish To sends a version there without touching Live. For most teams, a shared preview link is enough; Google recommends the standard snippet on production.
  • Exports. Export the container before large changes. Import can Overwrite or Merge, with conflicting items either overwritten or renamed, which makes an export a practical backup.
  • Approvals. On Tag Manager 360, people with Edit access see Request Approval and an approver signs off. On the free version, agree in writing who publishes and who reviews.

Where this goes wrong

  • Publishing from the Default Workspace by habit. Two people edit it, and one publishes the other’s half-finished work.
  • Empty version notes. Six months later, nobody knows which version broke purchases.
  • Too many people with Publish. Old agencies and former staff keep rights for years. Review users in every audit.
  • Agency and client both editing. Without a rule, the client publishes over the agency’s workspace. Agree whose workspace publishes when.

An inherited container needs the GTM audit checklist before the first publish. The campaign side of a launch is in the paid media launch checklist.

Do it faster with Whathead

Whathead’s Google Tag Manager MCP follows GTM’s own model: changes go into a workspace, and nothing reaches the site until a version is published. From Claude you can read the workspace status (every changed entity and any merge conflict), compare the live version with the latest one, create a named version and publish it after you confirm. Updates and publishes carry GTM’s fingerprint, so a change fails instead of overwriting someone’s newer edit. Whathead is our product.

  • “Show the workspace status for GTM-XXXXXXX and compare the latest version with the live one. Tell me if publishing now would include anyone else’s changes.”
  • “Create a version named 2026-11-19 | Meta | Purchase event ID with this description, then wait for my confirmation before publishing.”

There is no dry-run preview for GTM writes in Whathead. Claude asks before each write, the workspace is the draft, and Preview on the real site is still yours to run.

GTM versions and workspaces: common questions

Can you roll back a GTM publish?

Yes. In Versions, select an earlier version and publish it from the Actions menu. Set as Latest Version also copies it into your draft so you can fix forward.

What is the difference between a GTM workspace and a version?

A workspace is a draft set of changes. A version is a saved snapshot of the whole container, created from a workspace, and only a published version is live.

How many workspaces can I have in GTM?

Three at once on a standard container: the Default Workspace and two more. Tag Manager 360 allows unlimited workspaces.

How do I test GTM changes on a staging site?

Use Preview on the staging URL, or create a custom environment with its own snippet on staging and publish versions to it with Publish To.

Who can publish a GTM container?

Users with Publish permission on the container. Creating a version needs Approve access or higher.

Sources

Written by Ahmed Shahin, founder of Whathead. Last reviewed 19 November 2026.