Skip to content

Guide 121 · Container · GA4 + Tag Manager

Resolve a workspace conflict: pick the workspace side or the latest side, one item at a time

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

Two workspaces can change the same tag. When the other workspace publishes first, your workspace goes out of date, and Tag Manager tells you on the next publish attempt: this workspace is out of date, with a prompt to update it. Google's workspaces page says a workspace update will bring in any changes made in other versions of the container since your last update, and if any of these changes conflict with changes in the current workspace, the conflicts will be shown and you will be prompted to resolve them. The resolution tool shows the latest synced version on one side and your workspace on the other, and you pick one per conflict. The worked example has 2 conflicting items.

Expected signal

After step 4, the Workspace Overview page shows no conflict message, the workspace is up to date with the latest version, and the 2 items carry the side you picked for each — 1 from the workspace, 1 from the latest version.

Download the container fragment: the resolved-conflict fragment (JSON) (export format version 2, 1770 bytes, MD5 7c3b1fdc72d958357e75d5d65105670c). It holds the merged state from the worked example: the scroll trigger with the 90 percent threshold from the workspace side, and the Google tag with the corrected Measurement ID placeholder from the latest side. The file is a hand-built import template, validated structurally — it was not exported from a live container.

What you need

  • A workspace that is out of date. The conflict only appears when another version has been published since your workspace was last updated. No newer version, no conflict.
  • Knowledge of what each side changed. The tool shows both versions of the item, but it cannot say which one is right — that is a judgment call, and it needs the person who made the change.
  • Edit access to the container. Resolving a conflict edits the workspace.

The trace

  1. Click Update Workspace when the out-of-date notice appears. When you attempt to publish a workspace and changes from another version have been found, Tag Manager shows a notification that the workspace is out of date. Click Update Workspace to see the list of unmerged versions.
  2. Open Resolve conflicts from the Workspace Overview page. The overview displays a Conflict found message when conflicts are identified. Select Resolve conflicts to open the resolution tool. Each container has one stream of versions, so the comparison is always between your workspace and the latest version in that stream.
  3. Resolve the conflicts one at a time. The configuration of the latest synced version is shown on the left, and your workspace configuration on the right. For each conflicting item, pick one side. In the worked example there are 2 conflicts: the scroll trigger, where the workspace side wins because it adds the 90 percent threshold the latest version lacks, and the Google tag's Measurement ID, where the latest side wins because a teammate corrected a mistyped ID. That is 1 pick from the workspace and 1 pick from the latest version — 1 + 1 = 2 conflicts resolved.
  4. Update the workspace and check it before you publish. After resolving, the workspace is up to date with the latest version, and the conflict message is gone. Preview the merged workspace before publishing — the merge can combine a tag from one side with a trigger from the other in ways neither side tested.

Dead ends

DEAD END — PICKING ONE SIDE FOR THE WHOLE WORKSPACE. There is no resolve-all button, because each conflict is a different decision. Picking the workspace side for every item discards the teammate's corrections; picking the latest side for every item discards your work. Resolve one at a time, on purpose.

DEAD END — UPDATING WITHOUT OPENING THE CONFLICT TOOL. The update pulls in the other version's changes first. Items that do not conflict merge silently, and a change you did not expect can land in your workspace without a prompt. Read the unmerged versions list before you confirm the update.

DEAD END — RESOLVING AND PUBLISHING IN ONE MOTION. A resolved workspace is a merged workspace, and a merged workspace is an untested one. Preview it after the merge — the resolution does not test anything, it only picks a side.

End state

A workspace with no conflicts, up to date with the latest version, carrying 1 item from each side in the worked example. The merge is resolved and the workspace is ready to preview, then publish.

Sources

  • Tag Manager Help — Workspaces — one stream of versions, the out-of-date notice, Update Workspace bringing in other versions' changes, conflicts shown and resolved one at a time, latest version on the left and the workspace on the right

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 1770 bytes (1.73 KB, 0.86% of the reported 200 KB container size limit), MD5 7c3b1fdc72d958357e75d5d65105670c, and passed 16 structural checks.