Free tool
GTM container diff
Two container exports in, one list out: every tag, trigger and variable that was added, removed or changed between them, and, for each change, the field and its value before and after.
Example:
Also free: GTM container viewer: read any published container by its ID.
When you need it
- Before publishing: what a workspace really changes, including the edits nobody mentioned.
- After something broke: the version that went out on Tuesday against the one before it.
- Staging against live: two containers that should match, and the places they do not.
- A client’s container against your template: what was customised, and what was dropped.
How the comparison works
Each kind (tags, triggers, variables, built-in variables, custom templates, folders) is matched by name, the one key that means the same thing in both files. Ids, fingerprints and paths are left out because they differ between containers without meaning anything. A tag’s firing and blocking triggers are compared by trigger name, GTM’s built-in All Pages and Initialization triggers included. Parameters are read as values, so a change inside a Custom HTML tag or a lookup table shows as that parameter, before and after.
Getting the two exports
- In Tag Manager open Admin → Export Container.
- Pick the version (or the workspace) and export; repeat for the second.
- Drop the older one under Before and the newer under After.
Questions
How do I compare two GTM container versions?
Export both from Tag Manager (Admin, Export Container, pick the version or workspace) and drop the two files here. Tags, triggers, variables, built-in variables, templates and folders are matched by name and every changed field is listed before and after.
Does GTM have a built-in diff?
Inside a workspace, Tag Manager shows the changes against the latest version, and the version history lists what each version touched. Comparing two arbitrary versions, two workspaces, or two containers (staging and live, or a client’s container against your template) is what an export diff is for.
Why does a renamed tag show as removed and added?
The export identifies items by an ID that differs between containers and workspaces, so the only stable key across both files is the name. A rename therefore reads as the old name gone and the new one added.
Are trigger IDs compared?
No. A tag’s firing and blocking triggers are compared by trigger name, so the same setup in two different containers reads as the same, and ids, fingerprints and paths are ignored.
Is my container uploaded anywhere?
No. Both files are read in your browser and nothing is sent or put in the page address.
The Tag Master extension compares containers without exporting anything: the one published on the page against another by ID, and what the container says should fire against what the page actually sent.
Try it on your own site
Tag Master is free, needs no account, and collects no data.
Add to Chrome, it’s free