GTM workflow · Inventory & Cleanup
Make GTM cleanup a reviewed decision
Find candidates, check their purpose and dependencies, and review proposed changes before they reach a workspace.
Start with the task in front of you
An old name or paused status is a reason to investigate, not a reason to delete. Build a cleanup list you can explain to the account owner.
The Triggers and Orphaned tiles highlight and the table narrows to orphaned triggers across brands.
Make the next decision clearer
Find candidates
Use the inventory's filters and usage information to focus the review.
Keep context attached
Check ownership, timing and shared dependencies before deciding the action.
Inspect the proposed change
Review the exact scope of edits before applying them to the intended workspace.
A practical way to use it
Collect a focused list
Extract the account and filter the relevant container and items.
Review each decision
Separate retain, investigate and change candidates. Keep unresolved items out of bulk deletion.
Review, apply and test
Inspect the proposed edits, apply only the approved scope and test before manual publication.
A review dialog lists would-delete lines for two containers with a typed DELETE confirmation.
What the result can tell you
Usage findings need interpretation. ODDVX does not automatically publish a GTM container, and a completed cleanup action is not proof that every journey still works.
Before you start
Does a cleanup candidate mean safe to delete?
No. Confirm business purpose, relevant dependencies and the retest plan before making that decision.
What do I need to get started?
Use ODDVX for Windows with authorised access to the relevant account or test target. Start with a scope you understand. Free provides individual runs and on-screen findings; Premium adds supported batch and delivery options.
Start with one useful result
Bring this workflow to your next review.
Use the guide to define the scope, interpret the result and decide what happens next.