Job gtm-container-cleanup-for-one-site · revised 11 October 2026
Clean up one Google Tag Manager container so every tag has a reason
One Tag Manager container is inventoried, stripped of unused and duplicate tags, and saved as a named version for you to publish, with a before and after test.
You might be seeing
- Several tags with similar names send the same event
- Nobody can say which tags are still needed or who added them
No passwords, keys, card details or admin invites needed to start.
What usually happened
A Tag Manager container has accumulated unused tags, paused tags, duplicate Google Analytics tags, triggers that match nothing and variables nobody reads. Without an inventory, each change risks breaking a measurement that still matters, so nothing is removed.
Who it’s for: A site owner or agency inheriting a Tag Manager container full of old tags nobody can explain.
Usually starts when: Tags from former agencies, retired ad platforms or duplicated GA4 setups are still live, and no one dares to change the container.
The result: The container is delivered as a new named version, not yet published, in which every remaining tag has a recorded purpose and owner and the removed tags are listed with their reasons. Each agreed test event still reaches GA4 once with the same name and parameters, the tags that stay fire exactly as before, and the tags that fire differ from the baseline only by the listed removals.
Check whether this job fits
Answer these without sharing container exports or logins.
Checks you can run yourself
Count the tags that never fire
Open Tag Manager preview on three key pages and watch which tags appear under Tags Fired and which do not.
Look for: Tags that never fire on any key page are candidates for review, not for deletion on that evidence alone.
What you get
- An inventory table of tags, triggers and variables with purpose, owner and decision
- A cleaned workspace saved as a named version with notes, not published until you approve
- Before and after preview results for the agreed test events, with the tags that fire counted for each and the removed tags matched to the inventory
Included
- One web container with up to 50 tags, on one site
- Inventory of every tag, trigger and variable with what it sends and whether it fired in preview
- Removal or pause of tags agreed as unused or duplicate, in a workspace for your approval
- A before and after run of an agreed list of up to ten test events, with a count of the tags that fire for each event
Not included
- Rebuilding the measurement plan or adding new events
- Server containers and server-side tagging
- Deciding which advertising platforms you should use
- Removing tags that you or your agency state are contractually required without that confirmation
- Any promise about page speed, ad performance or rankings
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Every agreed test event, performed in Tag Manager preview before and after the clean-up, sends the same GA4 events once each with the same names and parameters. Every tag that stays fires exactly as it did before, and the tags that fire differ from the baseline only by the tags listed as removed or paused in the inventory, each with its reason.
Evidence: Preview summary screenshots for each of the up to ten test events, before and after, side by side, with a before and after count of tags fired per event and the removed tags marked against the inventory.
Every tag left in the container has a recorded purpose and owner in the inventory, and every removed or paused tag is listed with the reason.
Evidence: The inventory table and the version notes.
After you publish, the live site sends the agreed test events to DebugView exactly once each.
Evidence: DebugView screenshots of each event after publication.
Sign-off. You compare the before and after results, the removal list and the inventory, and publish the version yourself; we then run the live check; you sign off in writing after that. Payment follows sign-off.
If it fails. If a tag that stays fires differently, an agreed event is lost or an unlisted tag changes, you do not pay for this fixed scope and the previous version stays the published one. If the live check fails after you publish, we say so and you can republish the earlier version.
When it fits, and when we stop
It fits when
- You can give a scoped role on the container and an account holder who can publish
- The site can be loaded in Tag Manager preview and the agreed test events can be performed without a live charge
- The container has up to 50 tags; a larger one is quoted separately
We stop and tell you if
- Nobody can confirm which advertising or analytics accounts the tags belong to
- The container is shared by several sites and no site can be used for the test list
- The container has more than 50 tags
What could go wrong
Publishing creates a version. If anything is missed, republish the earlier version, which Tag Manager keeps in the Versions list.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A tag that looked unused was serving a report someone still reads. | Uncertain tags are paused first and listed for confirmation; nothing is deleted without a named confirmation. |
| Cleaning changes tag firing order and loses an event. | The same ten test events are run in preview before and after; acceptance needs identical firing for every tag that stays, and every difference must be one of the listed removals. |
A separate reviewer compares the before and after results and the list of removed items, and checks that nothing marked ask was removed. You approve and publish.
How we deliver
We arrange the work and independent review, then show you the result against the agreed checks. You keep authority over your systems.
- Agree the container, the test list and the access route in writing
- Create a baseline by running the agreed events in preview and recording what fires
- Build the inventory and classify each item as keep, pause, remove or ask
- Apply the agreed removals in a workspace and save it as a named version without publishing
- Run the same events again and compare the results with the baseline: the tags that stay must fire exactly as before, and the only differences are the listed removals
- Independent review of the diff, then hand over for your named person to publish; after you publish, run the live check in DebugView
This is a one-off job, not a subscription or emergency cover. We confirm eligibility, the price, a start window and a delivery date before you accept. Work starts only after the agreed inputs and the least access the job needs are in place. Fees charged by Google, Meta, your host or any tool you use are not included. No charge or booking is created by an enquiry.
Need to keep it working?
A standing review can test each future change before it is published.
Ongoing work is separately scoped and quoted: no monitoring, response-time guarantee or automatic subscription is included in this job.
Explore an ongoing engineering lane, or mention the responsibility you need in your enquiry.
What you can check
This is a new service. We have not delivered this job for a client yet.
Other ways to get this done
- Tag Manager keeps every published state as a version, so you can inspect history and republish an earlier version yourself. support.google.com
- Tag Assistant and Tag Manager preview show which tags fire on each page, which you can use for a first look. support.google.com
Questions
Will this make my site faster?
We do not promise that. The outcome is a documented container whose test events behave the same; removing unused tags may reduce what loads, but we do not measure or promise speed.
Do you delete tags?
Only those you agree are unused or duplicate. Uncertain ones are paused and listed, and the earlier version stays available.
Send an enquiry
Send us
- The site address, the number of tags as shown in the container, and who edits it today
- The five or so events you must not lose, such as an enquiry or a purchase
- No logins and no account IDs in the first enquiry.
Later, once you agree
- Approve access to the container, granted to the identity we agree with you before work starts and with no publish rights. Google describes Approve as the level that can create versions, workspaces and make edits but not publish
- Confirmation, from the account holders, of which advertising and analytics accounts are still in use
- The agreed test event list
You own the website, the Google and Meta accounts, the tag manager container and all the data. We ask for the lowest role that lets us do the job. Before any work starts we agree with you in writing which identity receives that role; you grant it and can remove it at any time. We never ask for your passwords. You keep the right to publish: we prepare changes and you publish them.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “gtm-container-cleanup-for-one-site” as the subject.