An event is a recorded interaction or occurrence in an analytics system.
In plain English
This is a measurement term. The number is never the goal by itself. Start with the decision you are trying to make, then ask whether this measurement gives you useful evidence for that decision.
A real example
A page view, button click, video start, file download or purchase can be recorded as an event.
The number becomes useful only when you know what you are comparing it with and which decision it should influence.
Why it matters
Events let you measure behaviour beyond simply counting visits.
Analytics becomes useful when it changes what you do next. A dashboard full of numbers can still tell you very little. A small set of well-chosen measurements can show where people arrive, where they struggle and whether an important action actually happens.
When do you actually need to care?
You need to care when you are deciding what to improve, which marketing activity is worth continuing, whether a redesign helped, where people abandon a process, or whether an important business action is happening at all. You do not need another metric simply because a platform can display it.
Useful questions to ask
- Which decision will this number help me make?
- What should I compare it with: another period, page, channel or audience?
- What would I actually do differently if the number changed?
What should you do with this?
Write the business question first and the metric second. If knowing the number would not change a decision, it probably deserves less attention than a measurement that will.
What this does not mean
An event is not automatically important. Analytics tools can collect many events that never affect a decision.
The short version
Track interactions because they answer a question, not because the button exists.
Related: conversion events and analytics.
Further reading: Google Analytics on events.