How tracking works
Tracking is the plumbing beneath every report. A small piece of code on your site — usually a tag deployed through a tag manager — watches for something happening, packages it as an event with a name and a few parameters, and sends it to a destination such as GA4 or an ad platform. Nothing appears in any report that was not captured by that chain first.
There are two broad ways to do it. Browser-side tracking runs in the visitor’s browser: simple to set up, and easy for ad blockers, extensions and privacy settings to stop. Server-side tracking passes the event through a server you control before it reaches the destination, which is more resilient and considerably more work to build and maintain.
Why tracking matters
Every decision downstream inherits the quality of the tracking. Bid strategies in Google Ads and Meta learn from the conversions you send them, so if a conversion event fires on the wrong page, or fires twice, the system is being taught the wrong lesson and will keep spending against it. Bad tracking does not just mislead you; it actively steers the money.
It also decides whether you can prove anything. A question as basic as which channel produced last month’s enquiries can only be answered if those enquiries were tagged at the moment they happened. Reconstructing it afterwards from memory is not evidence.
Where tracking goes wrong
Duplicate events are the classic fault. A thank-you page that also fires a form-submission event counts one enquiry twice, and both the ad platform and the analytics report inherit the error. Test fires left running in a live account do the same damage more quietly.
The other frequent fault is tracking the easy thing instead of the valuable one. A click on a phone number is not a phone call. A form submission is not a qualified lead. Where the gap between them is wide, the numbers flatter the campaign, and proper conversion tracking means closing that gap rather than measuring around it.
Consent is the third. Where a visitor declines, a compliant setup must not send their data, and the report will be short by exactly that group. That is expected behaviour, not a bug to be worked around.
How to act on it
Decide what you need to know before you install anything, then track that plus the steps immediately before it. A short, correct list beats a long, half-broken one every time.
Deploy through Google Tag Manager rather than pasting code into page templates, so tags can be added, tested and removed without touching the site and every change has a version history. Use the preview mode to watch each event fire once, from a real device on a real connection, before you trust it. Then check the totals against something outside the browser: the enquiries actually sitting in your inbox are the honest count.
Re-test after any site change. A theme update, a new form plugin or a redesigned checkout will break tracking silently, and the first symptom is usually a campaign that appears to have stopped working overnight.
