The systematic collection and analysis of user behavior data from digital products. Tells you what is happening at scale but never why it is happening.
Definition: The systematic collection and analysis of user behavior data from digital products. Tells you what is happening at scale but never why it is happening.
Analytics captures what users do in your product—page views, clicks, feature usage, session duration, conversion events. It is the broadest source of behavioral data available to product teams and the most commonly misinterpreted.
Analytics tells you that 60% of users never open the settings page. It cannot tell you whether they did not need settings, could not find them, or did not know they existed. Every "why" question requires qualitative research.
Teams often instrument everything and analyze nothing. Thousands of tracked events, dozens of dashboards, zero insights. The value of analytics is not in the volume of data you collect but in the questions you ask of it.
Start with a question. Then check whether your data can answer it. If it can, great. If it cannot, that question needs a different method.
Data generated by users without direct prompting from a researcher—analytics, A/B tests, support tickets, social listening. Ideal for uncovering unexpected patterns and generating new hypotheses.
A metric explicitly chosen to track progress toward a specific business or product goal. Not every metric is a KPI—only the ones tied to decisions you will actually make.
Tracking how users move through a sequence of steps and where they drop off. Shows you exactly where your process loses people—and how many.
This term is referenced in the following articles: