Many websites track events.
Clicks.
Form submissions.
Video plays.
On paper, it looks complete.
But more tracking doesn’t mean better data.
What usually goes wrong
Event tracking often starts with good intentions:
Track everything.
Capture as much data as possible.
But over time:
- naming becomes inconsistent
- logic varies across pages
- context is missing
- reports stop aligning
The issue isn’t volume.
It’s structure.
What good event tracking does differently
Good tracking isn’t about capturing more actions.
It’s about defining them clearly—and consistently.
1. Events are clearly defined
Each event represents a specific, intentional action.
Not:
“button_click”
But:
- event: form_submit
- form_type: contact
- page_context: pricing
The event describes what actually happened—not just what was triggered.
2. Naming is consistent
Similar actions follow the same structure.
- form_submit (not formSubmit, submit_form, form_complete)
- video_play (not play_video, videoStart)
Consistency makes data:
- easier to query
- easier to interpret
- easier to trust
3. Context is included
An event without context is incomplete.
Without context:
actions look the same—even when they aren’t
With context:
each event carries meaning
4. Logic is centralized
Tracking logic shouldn’t live in multiple places.
When it does:
- rules diverge
- updates are inconsistent
- errors multiply
Good tracking is defined once—and reused.
5. Events are stable over time
Once defined, events don’t change casually.
If they do:
- historical comparisons break
- reporting becomes unreliable
Stability is what makes data usable over time.
What good tracking avoids
Good tracking is as much about what you don’t do.
It avoids:
- tracking every interaction
- relying on front-end selectors alone
- one-off events for edge cases
- mixed naming conventions
More events ≠ better tracking.
Where most implementations fall short
Tracking is often treated as:
something to “set up”
Instead of:
something to define and maintain
It becomes:
- reactive
- fragmented
- difficult to scale
How this connects to everything else
Event tracking sits at the start of your data flow.
If it’s inconsistent:
- your data layer becomes unreliable
- your reports don’t align
- your integrations amplify the problem
Everything downstream reflects the quality of your tracking.
A simple way to think about it
Poor tracking:
captures activity
Good tracking:
defines behavior
What to watch for
If your tracking needs work, you’ll start to see:
- similar actions tracked differently
- missing context
- difficulty answering basic questions
- growing reliance on assumptions
These aren’t reporting issues.
They’re tracking issues.
Final thought
Good event tracking doesn’t collect more data.
It creates consistent, structured definitions of what’s happening.
Without that, your data is fragmented.
With it, your data becomes reliable—and everything built on top improves.
Doug McCaffrey
Designs and maintains analytics systems that remain reliable over time.
Explore how this connects across your data estate: