GTM Ultimate Stack
Pause, delete or retain a GTM tag?
Use purpose, timing and verification to choose the right action for a cleanup candidate, then stage it in one container or in every brand that shares it.
Choose the action that fits the reason
Cleanup doesn't always mean deletion. Sometimes the right action is to pause a campaign, keep a shared dependency, or leave an item alone until its owner explains it. Make the reason explicit before you choose a control.
Start in Inventory & Cleanup with the candidate's row: its name, type, status, usage and container. This guide assumes you have already identified the candidate. If not, start with Reading GTM usage verdicts.
A simple decision table
| Situation | Likely next action | What to confirm |
|---|---|---|
| Still supports a required journey | Retain | Owner and expected behaviour |
| A campaign that is off for now | Pause | Restart plan and publication timing |
| Purpose unclear | Investigate | Owner, dependencies and recent or planned use |
| Confirmed obsolete | Delete | Dependencies, approval and retest plan |
A cleanup candidate branches into four situations, each leading to retain, pause, investigate or delete with what to confirm.
Pause and Activate are for tags
Only tags have a paused state in GTM, so Pause and Activate appear only for tags. The buttons light up when your selection contains tags in the opposite state. Triggers and variables can be renamed, deleted or copied.
Before you pause, set Entity: Tags so the selection contains only tags. Then check Pending only before reviewing, so you know exactly what was staged.
A grid of tag, trigger and variable against pause, activate, rename, delete and copy, with pause and activate ticked only for tags.
Seasonal campaigns across brands
Seasonal tags are where pausing pays off, and where managing several brands one at a time hurts most. When a campaign ends:
- Filter by name, for example Name contains: Summer Sale, across every brand.
- Check the rows, then Select all shown and Pause.
- Review, apply, and publish each container in GTM.
When the campaign returns, filter the same name with Status: Paused, select all shown, press Activate, then review and publish. The configuration was never lost, so nothing has to be rebuilt.
Four brand rows for the same promo tag change status to paused, then show staged activate and pause pills.
Keep pause and deletion distinct
Pausing keeps the tag's configuration for a possible return. Deleting removes it from the workspace. In both cases, nothing reaches visitors until you publish the workspace in GTM.
Once a delete is published, it is permanent apart from GTM's own version history. ODDVX keeps no separate backup of deleted items. If you are unsure, pause first and set a date to come back. A paused tag that is still paused in three months is a much easier deletion to justify.
Four stages for a delete: staged in a workspace, still reversible by deleting the workspace, published by you, and gone apart from version history.
Leave a reason the next owner can understand
Record the decision, who approved it and the test that confirms the result. For a pause, add the condition for restarting it. For a deletion, keep enough evidence to explain why the item was no longer needed. Use the workspace name as the reference: it is the same in every container.
If the evidence is incomplete, keep the candidate under investigation. An honest open question is easier to manage than a tracking gap caused by an unnecessary cleanup.
A change-log form fills in the change, reason, approver, workspace, test and restart condition.
ODDVX for Windows
Build once. Stage it in every brand.
Start free on one GTM account. Premium adds several accounts in one run, exports and scheduled reports.