Who this is for
Businesses whose tracking scripts are pasted into the theme, so nobody knows what is installed and an update wipes half of it. Marketing teams who wait two weeks for a developer to add a conversion tag. Companies that inherited a container from an agency with 40 tags, no naming convention and no notes. And anyone starting ads who wants the measurement built once, correctly.
What Tag Manager actually does for you
It separates marketing tracking from the website code. Once the container is installed, tags, triggers and variables are managed in a web interface with version history, a preview mode and the ability to roll back. That means a new conversion tag, a new pixel or a changed event takes an hour rather than a sprint, and a mistake can be undone rather than deployed. It also means one place to answer the question every audit asks: what is running on this site, and who put it there?
What a GTM implementation includes
- Container setup and installation in the correct positions on every template, including any subdomain or checkout that sits outside the main site.
- A naming convention for tags, triggers and variables, applied consistently. This is what stops a container from becoming unreadable in year two.
- A data layer plan. The events and values the site should push, agreed with your developer, so tracking does not depend on fragile CSS selectors that break at the next redesign.
- Tags built: GA4 configuration and events, Google Ads conversions and remarketing, Meta Pixel, LinkedIn or TikTok tags where you advertise there, call tracking, chat and WhatsApp click events.
- Triggers for the actions that matter: individual form submissions, button clicks, scroll depth where it means something, video plays, file downloads and checkout steps.
- Consent mode wired in where your markets or your legal advice require it, so tags respect a choice rather than being blocked at random.
- Cleanup of an existing container: duplicate tags removed, dead tags deleted, hard-coded scripts migrated out of the theme, and the whole thing versioned before anything is changed.
- Server-side tagging where the volume and the ad spend justify the running cost. For most small businesses it does not, and I will say so.
How the setup runs
- Inventory (day one). Every script currently on the site, listed with what it is and whether anyone still uses it. This step usually finds a pixel from an agency that left in 2023.
- Plan. The measurement plan shared with GA4 setup and audit: the actions, their names and their parameters. Tagging without this produces a container full of guesses.
- Data layer. Where values such as order total, form name or product ID are needed, I specify what the site should push and work with your developer to add it.
- Build in preview. Tags and triggers built and tested in GTM preview mode before anything is published.
- Verify on a real device. Every trigger tested from a phone: forms submitted, buttons tapped, calls started. Tag Assistant and GA4 DebugView both have to agree.
- Publish and document. A named version with notes, plus a tracking document listing every tag, its trigger and its purpose, and access for your team.
One to two weeks for a standard site. Longer where a data layer has to be added to a store or an application.
What you receive
- A configured container in your own Google account, with your team as users.
- A documented tag, trigger and variable list explaining what each one is for.
- A data layer specification your developers can keep using.
- Verification screenshots from preview mode and DebugView.
- A published version with notes, so the change history is readable.
- A recorded walkthrough covering how to add a tag and how to roll back.
Container problems I see most
- Both a hard-coded GA4 tag in the theme and a GA4 tag in GTM, doubling every session.
- Tags named “Tag 1”, “copy of Tag 3”, “test final”, with no notes and no owner.
- Triggers built on CSS classes that a theme update renamed, so conversions silently stopped three months ago and nobody noticed.
- Every form on the site sharing one trigger, so a newsletter signup and a quote request are the same conversion.
- Ad pixels still firing for platforms the business no longer uses, slowing the site for no benefit.
- Nobody ever opening the version history, so an unexplained drop cannot be traced to the change that caused it.
Where this fits
Tag Manager is the delivery mechanism; the meaning of the data is set in GA4, the platform side is Google Ads conversion tracking and Meta Pixel and Conversions API, and what you do with the numbers is dashboards and reporting. The overview of how these pieces fit is on analytics and tracking.
Pricing pointer
Fixed-price project, scoped by the number of sites, conversion actions and platforms, with cleanup of an existing container quoted after the inventory. Prices are on request. Tag Manager itself is free; server-side tagging adds a hosting cost you pay directly.
Next step
Request a free tracking check. Send me your site URL and container access if you have it, and within 4 business hours I will tell you what is firing, what is broken and what it takes to fix.