Google Tag Manager setup and cleanup for US businesses
Google Tag Manager setup and cleanup that turns a cluttered container into something you can read. I remove dead and duplicate tags, rebuild what matters with clear naming, test everything in Preview mode, and document it so anyone can take over after me.
Typical turnaround: within a week
Sound familiar?
Nobody knows what half the tags in your GTM container actually do anymore
Tags fire twice, or don't fire at all, and no one's sure why
Only one person (who may not work there anymore) understands the current setup
Here's what changes
A container with only the tags you actually need, clearly named and organized
Confidence that what's firing is what you think is firing
Documentation good enough that someone else could take it over without you
How it works
Audit and clean
Map every existing tag, trigger, and variable, and remove what's dead or duplicated.
Rebuild what's needed
Reconstruct the tags that matter with a naming convention and folder structure that makes sense.
Test and document
Validate every tag fires correctly in Preview mode, then hand over documentation, not just access.
Hiring for Google Tag Manager setup and cleanup? Here is what it should actually include
Most Google Tag Manager setup work I see is really cleanup. The container has passed through a freelancer, an agency, and maybe an in-house hire. Tags were added for campaigns that ended years ago, nobody removed them because nobody was sure what depended on them, and now tags fire twice, or not at all, and no one wants to touch it. Starting from a blank container is the easy version of this job.
Here is what a proper setup and cleanup should include. First, an audit that maps every tag, trigger, and variable, and what each one feeds. Second, removing what is dead or duplicated. Third, rebuilding what matters with a naming convention and folders that make sense to a stranger. Fourth, testing in Preview mode before anything is published. Fifth, publishing with a clear version name and description, so every change can be traced later. Last, documentation you keep, not just access to a container.
The part that separates careful work from risky work is the first step. A tag that looks dead may still feed a platform someone reports on, so I check dependencies before deleting anything. Another common cause of double counting is a tag installed both in Tag Manager and directly in the site's code, and that needs to be found and resolved on both sides. Every publish in Tag Manager creates a saved version, so changes are traceable and an earlier version can be restored if something goes wrong.
You also get one person doing the work, and a container you can hand to someone else without starting over. If the numbers this delivers do not match across your ad platform and GA4, I fix it for free until they do. Most cleanups are done within a week once I have access.
Who GTM setup and cleanup is for, and who does not need it
This fits if you inherited a container nobody can explain, if the person who built it has left, if tags are firing twice or not firing, or if you are about to add more tracking on top of a setup you do not trust. It also fits after a site redesign or platform change, when old triggers quietly stop working.
It is probably not what you need if your site has one or two simple tags and everything reports correctly. A small, working setup does not need a rebuild. If your question is simply whether your tracking is right, a tracking audit gives you a written answer without changing anything. You may not need Tag Manager at all if your platform handles your tracking natively and you never plan to add more than a tag or two. And if you want a developer team making daily changes under formal code review, that is a different kind of engagement than I offer.
Real results, not theory
What You Get:
Full container audit and cleanup of dead or duplicate tags
Rebuilt tag structure with clear naming conventions
Trigger and variable documentation
Testing in Preview mode before anything goes live
Handoff documentation so you're never locked in
The Tracking Accuracy Guarantee
If the numbers this delivers don't match across your ad platform and GA4, I'll fix it for free until they do. No time limit, no extra charge.
Frequently asked questions
How long does a Google Tag Manager setup or cleanup take?
Within a week. The audit of existing tags comes first, then cleanup, rebuilding, and testing in Preview mode. Timing depends mostly on how quickly I get access and how many tags the container has. If something needs a one-time change in your site's code, that can add time on your developer's side.
What access do you need to my Google Tag Manager account?
Access to the container at a level that lets me edit it and, once testing passes, publish. I work through the audit and rebuild before anything goes live, and you can remove my access afterward. The container should live in an account you control. My guide to sharing Google Tag Manager access shows the exact steps.
Will cleaning up my GTM container break my tracking?
Not if it is done carefully, but I will not promise zero risk on a container I did not build. I map what depends on each tag before removing it, test every change in Preview mode, and publish with a clear version name. Each publish is saved as a version, so an earlier one can be restored if something looks wrong.
How is GTM setup different from GA4 tracking setup?
GTM setup is about the container itself: tags, triggers, variables, naming, and documentation. GA4 tracking setup is about the analytics property: which events and key events matter and how they are configured. They often go together, since GA4 events are commonly sent from Tag Manager, but a messy container can be fixed without touching GA4, and the reverse is also true.
What is the difference between GTM setup and server-side tracking?
A standard Tag Manager container runs in the visitor's browser. Server-side tracking adds a separate server container on your own subdomain, so key tags can fire from the server instead. I treat them as separate projects. A clean browser-side container is usually the right foundation before moving anything server-side.
Do I actually need Google Tag Manager?
Not always. If you only have a tag or two, adding them directly can work. Tag Manager earns its place once you have several, such as GA4, Google Ads conversions, and call tracking, because you can manage, test, and version them in one place without editing your site each time. The tradeoff is that a container needs to be kept tidy.
Guides on this topic
- How to Share Google Tag Manager AccessShare Google Tag Manager access in four steps, plus which of the five permission levels to actually give someone and why it matters.
- GTM Now Writes Version Descriptions With AIWhen you publish a GTM version now, an AI writes the name and a tag-by-tag description of what changed, without you typing a word. Here's what I saw.
- What Is a Google Ads Conversion?A conversion is a specific action you've told Google Ads to count as valuable, not a click or a visit. Here's what counts and how to set one up.
Related services
I'm Filip Steiner - your Google Ads & Conversion Tracking Specialist
Over the past 5 years, I've managed 100+ ad accounts across the US, from local services to ecommerce.
My background in analytics and conversion tracking helps me turn ad chaos into profitable systems.
I don't just run ads. I build measurement systems that show you exactly where every dollar goes, and what it returns.