Swap a vendor tag across brands in one reviewed batch

The pattern

Vendor swaps are a common multi-brand job: a new pixel, a different consent-mode version, a replacement for a deprecated tag. Done one container at a time, they leave a long stretch where some brands run the old tag, some the new one, and a few run both.

Inventory & Cleanup lets you stage the whole swap as one batch:

1. Add the replacement to every brand, with Create for a built-in type or Copy for a vendor template.
2. Pause the old tag in every brand.
3. Rename the old tag with a [retired] suffix, so it is easy to find later.

Everything goes into one workspace per container and one review. The old tag stays paused, not deleted, until the new one has proved itself.

Stage the replacement

If the new tag is a built-in type, create it across every brand that needs it (see Create in every brand at once). If it is a vendor template, set it up and test it in one container, then copy it to the rest (see Roll out a Community Template tag).

Give the new tag a name that clearly differs from the old one. If both share a name, the copy is skipped as already existing.

Pause and mark the old tag

In the same session, before you review:

1. Filter by the old tag's name, for example Name contains: Legacy Pixel, with Entity: Tags.
2. Select all shown, and check that only the old tags are selected.
3. Press Pause.
4. Open Rename…, turn on .*, find $ (the end of the name) and replace it with [retired]. Then Apply to names.

Each old tag now has two pending changes: a pause and a rename. Both are in the same batch as the new tags.

Review the whole swap per container

Press Review & apply. For each container you should see three things together: the new tag (would copy or would create, with any template install), the rename of the old tag and its pause. If a container lacks something the new tag needs, it is skipped there with a reason. Fix that before you apply, or that brand will end up with the old tag paused and nothing in its place.

Publish, verify, then retire for good

Publish container by container in GTM, testing each brand's key journey in preview mode first. Check with the vendor's own tools that the new tag is receiving data. Keep the old tags paused for an agreed comparison window, so you can roll back by reactivating them if the new tag misbehaves.

When the window closes, extract again, filter by [retired] and delete the paused tags in a final batch. See Clean up orphans in one batch for the triggers and variables they leave behind.

Keep going

• Use case: build once, stage it in every brand
• Pause, delete or retain a GTM tag?
• Read the Review & apply preview