Skip to content

Guide 101 · Container · GA4 + Tag Manager

Workspaces and folders in Tag Manager: one workspace per job, folders by purpose

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

A workspace is Tag Manager's answer to two people editing at once: a separate draft copy of the container where a set of changes is built, tested and then published as one version. Google's workspaces page says a workspace lets you create multiple sets of changes for your container, and that it helps prevent teammates from inadvertently publishing someone else's unfinished changes. Folders are the second organizer: they group tags, triggers and variables by purpose inside a workspace. This guide creates a workspace for one job and folders for the four kinds of work in the container.

Expected signal

After step 3, the workspace list shows the new workspace next to the Default workspace, and the Folders list shows the four new folders. Tags created in the new workspace appear in its Changes list only — the live container is untouched until the workspace is published.

Download the container fragment: the workspaces and folders fragment (JSON) (export format version 2, 1390 bytes, MD5 26c733ee070c5bd2f5e3430e89f79a1c). It holds 4 folders — GA4, Ads, Forms, Utilities — with the Google tag and one data layer variable filed under GA4. The file is a hand-built import template, validated structurally — it was not exported from a live container.

What you need

  • A container with at least one tag, trigger or variable to organize. Folders are empty boxes without items; the worked example uses the Google tag from the snippet guide.
  • Edit access to the container. Creating a workspace and a folder are edits. Read access shows the lists but cannot add to them.
  • One job to put in the workspace. A workspace holds one set of changes. Two unrelated jobs in one workspace publish together, ready or not.

The trace

  1. Open the Overview tab and open Manage Workspaces. Every container starts with a Default workspace. From Overview, open the workspace menu and select Manage Workspaces to see the list. A regular account holds the Default workspace plus up to 2 additional workspaces — 1 + 2 = 3 workspaces in all. Tag Manager 360 accounts can create an unlimited number.
  2. Add a workspace and name it after the job. Click Add, enter a name and a description. The name and description may later become the version name and version description, so name it after the objective — GA4 scroll tracking, not Workspace 2. The workspace is an empty draft copy of the container at this point.
  3. Switch into the new workspace before you edit. Pick the workspace from the Workspaces page. Any tag, trigger or variable you create now belongs to this workspace's Changes list, and nobody else's publish can take it live early.
  4. Create four folders, one per purpose. Go to Folders, click New Folder, and create GA4, Ads, Forms and Utilities — 4 folders. When a workspace is versioned or published, the workspace is then removed and the Default workspace is recreated, so folders belong to the container, not to the workspace: they survive the publish.
  5. Move the items into their folders. Select a tag, trigger or variable and move it into the folder that matches its purpose — the Google tag goes into GA4. Folders change where an item sits in the lists, nothing else: moving a tag into a folder does not change when it fires.

Dead ends

DEAD END — DOING ALL WORK IN THE DEFAULT WORKSPACE. The Default workspace is shared: a teammate who publishes from it publishes your half-finished changes along with their own. One workspace per job keeps a publish to exactly the changes that were tested.

DEAD END — EXPECTING A PUBLISHED WORKSPACE TO STAY AROUND. When a workspace is versioned or published, its name, notes and list of changes are recorded with the version — and the workspace is then removed. The Default workspace is recreated after it. A workspace is a draft, not a permanent branch.

DEAD END — FOLDERS AS FIRING CONTROL. A folder is a label in the list. Moving a tag into a folder named Disabled or Do not use does not stop it firing; only pausing the tag or removing its triggers does that.

End state

One workspace holding one job, four folders grouping the container's items by purpose, and the live container untouched. When the workspace is published it becomes a version and disappears; the folders stay. Version naming and the publish step itself are the versions guide and the publish guide.

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 1390 bytes (1.36 KB, 0.68% of the reported 200 KB container size limit), MD5 26c733ee070c5bd2f5e3430e89f79a1c, and passed 15 structural checks.