Analytics and Tracking

Tracking

Also called event tracking, tagging

The technical capture of what people do on a site or app, and the sending of it to reporting tools.

Quick facts: Tracking

Category
Analytics and Tracking
Also called
event tracking, tagging
Level
Beginner
Affects
Reporting accuracy, ad platform bidding, attribution
Where to see it
Google Tag Manager preview, GA4 DebugView, Meta Events Manager, browser developer tools
In this article4
  1. How tracking works
  2. Why tracking matters
  3. Where tracking goes wrong
  4. How to act on it

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.

Do and do not

Do

  • Deploy tags through a tag manager, not page templates
  • Test every event fires once on a real device
  • Re-check tracking after any website or form change

Do not

  • Track a phone-number click as a phone call
  • Leave test conversions running in a live account
  • Collect data you have no decision for

Questions people ask about this

Do I need Google Tag Manager to track anything?

No. Tags can be placed directly in a site's code, and some platforms have built-in integrations that need no extra work. A tag manager becomes worth it as soon as you have more than one or two tags, because it lets you add, test and remove them without a developer and keeps a version history you can roll back to.

Is tracking still legal with privacy laws?

Tracking is lawful when people are told what is collected and, where the law requires it, asked first. What is not lawful is quietly collecting personal data and burying the fact in a policy nobody reads. In practice that means a clear privacy notice, a consent mechanism where your audience is covered by such rules, and collecting only what you actually use.

Why did my conversions suddenly drop to zero?

Almost always a broken tag rather than a market collapse. Site updates, changed form plugins, new page templates and unpublished container changes all stop events firing. Check the tag manager preview on a genuine submission first. If the event does not fire there, the problem is technical, and no bidding or budget change will fix it.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.