What it is
Analysis of behavioral data from real usage (page views, flows, drop-offs, conversions) to understand what users do at scale across a live product.
When to use it
During Implement, continuously, to monitor behavior, spot problems, and prioritize research.
Why (value)
Shows actual behavior at scale and reveals where users drop off, which no small qualitative study can quantify.
How to run it
- Define the questions and relevant metrics.
- Verify tracking is correct and complete.
- Analyze flows, funnels, and segments.
- Spot anomalies and drop-off points.
- Pair findings with qualitative research to explain why.
Inputs and outputs
- Inputs: Instrumented product and an analytics platform.
- Outputs: Behavioral metrics, funnels, and prioritized questions.
Time and effort
Medium. Setup and trustworthy instrumentation are the hard parts.
Evidence and limitations
Analytics is strong direct-user behavioral evidence of what happens, but it cannot explain why; correlation is not cause, and bad instrumentation misleads. Pair with qualitative methods. See Evidence and limitations.
Tips and pitfalls
- Validate your tracking before trusting numbers.
- Analytics tells what, not why; pair with research.
- Beware vanity metrics unlinked to goals.
Variations
Funnel analysis, cohort analysis, session replay, and heatmaps.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
Explore related methods
- A/B testing — Compare two live variants with real traffic to see which performs better on a chosen metric.
- UX metrics frameworks — Choose a coherent set of UX metrics tied to goals so you measure what actually matters.
- Usability testing — Watch representative users attempt real tasks to find where the design helps or gets in their way.
