Server-Side Tracking
Google Tag Manager Setup, Done Right
Almost every site has Google Tag Manager. Far fewer have it set up so the numbers it feeds can actually be trusted. The gap between those two is where most analytics quietly go wrong.
What "Right" Means
On your account, not a new one
A setup done right builds on the Google Tag Manager account you already have — it doesn't replace it, and it doesn't move your tracking into someone else's control. You keep using GTM the way you already do. What changes is what sits underneath it: a first-party foundation built to hold up, instead of a container script that loses a little more data every time a browser update ships.
Don't have a GTM account yet? That's fine — the right setup includes standing one up cleanly from the start, so the foundation is correct before anything gets built on it.
How It Usually Goes Wrong
A tag that fires twice is worse than no tag
The common failure isn't a missing setup — it's a sloppy one. A tag that fires twice double-counts every event. A conversion that stopped recording after a redesign nobody flagged to the analytics account. Events layered on over years by different hands until nobody's sure which number means what. The dashboard still loads; it's just reporting fiction with total confidence.
A tag that fires twice is arguably worse than no tag at all, because at least an empty report looks empty. A double-counted one looks like success — and you make decisions on it.
Built To Last
Set up once, verified, and kept honest
Done right, a setup isn't a one-time paste-and-pray. It's configured to be complete and durable, checked to confirm each thing you care about actually records, and paired with the server-side foundation so the collection doesn't quietly decay as browsers change. The point isn't a longer list of tags — it's fewer numbers you have to second-guess.
This is the plumbing underneath everything else Audry reads. Get it clean and every report built on top inherits the accuracy. Leave it tangled and every report inherits the mess.
What Audry Does Here
Untangling a decade of half-setups
A site's analytics show twice the leads the sales team can actually find. The culprit is almost always mundane: a form-submit tag that was duplicated during a past redesign, so every submission counts twice. Nobody notices, because "leads are up" is exactly the kind of number nobody questions.
Audry rebuilds the Tag Manager setup cleanly on the owner's own account, removes the double-fire, confirms each conversion records exactly once, and puts it on the server-side foundation so it stays correct as browsers change. The lead count drops to the real number — which is the point. You can't fix a funnel you're measuring twice.
Keep Reading
Next in this guide
Understand why the foundation lives off the browser in Server-Side vs. Client-Side Tracking, and why the data landing in your own account matters in First-Party Data: Why It's Yours to Keep. Or return to the full Server-Side Tracking guide.
Have your tracking set up to tell the truth
Audry's tracking setup is being built now. Join the waitlist to be first to hand your Tag Manager account to a crew that will get it clean and keep it that way.
No spam — one email, the day it's ready.