# Product Analytics

Product analytics uses behavioral and operational data to understand how people experience a product and to inform improvement decisions.

- Type: practice
- Domain: Data, experimentation & growth
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/product-analytics/>)

## What it means

Product analytics is the practice of collecting, validating, analyzing, and interpreting data about product use and performance. It commonly examines events, users or accounts, funnels, cohorts, retention, paths, experiments, and system conditions. Its purpose is to answer defined questions, not merely populate dashboards.

## Why it matters

Observed behavior can reveal where journeys break, which groups receive value, and whether outcomes change after a release. Combined with qualitative research and domain context, analytics helps teams prioritize investigation, evaluate hypotheses, and monitor product health at a scale direct observation alone cannot cover.

## When to use it

Use product analytics for questions about adoption, activation, engagement, retention, conversion, reliability, and experiment outcomes when those concepts can be measured responsibly. Begin with the decision and question, then determine whether event data, operational records, surveys, or research are appropriate.

## How it works

1. Frame a specific product question, decision, population, and time horizon.
2. Translate the question into measures and an instrumentation plan with governed definitions.
3. Validate identity, event firing, properties, consent, completeness, and known exclusions.
4. Analyze trends, cohorts, funnels, segments, or experiments while checking uncertainty and alternative explanations.
5. Combine findings with qualitative evidence, decide an action, and monitor expected and unintended outcomes.

## A practical example

A budgeting app sees low completion of account connection. Analysts compare cohorts by bank, device, and error type, then review support tickets and usability sessions. The evidence points to authentication failures at two providers, so the team fixes integration reliability instead of redesigning the entire onboarding flow.

## Where it breaks

Behavioral data shows recorded actions, not unobserved intent, inaccessible experiences, or complete causal explanations. Tracking can create privacy and security risks. Missing events, identity errors, selection bias, bots, and changing definitions can produce confident but wrong conclusions.

## Common mistakes

- Starting with an available chart instead of a decision question.
- Treating event counts as self-explanatory evidence of value.
- Ignoring privacy, consent, data quality, and users absent from the dataset.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/product-analytics/#visualization-product-analytics>)

## Sources

1. [What Events Do You Need?](<https://www.amplitude.com/docs/get-started/select-events>) — Amplitude Docs · Official product analytics documentation
2. [About Events](<https://support.google.com/analytics/answer/9322688?hl=en>) — Google Analytics Help · Official analytics documentation
3. [Measuring the User Experience on a Large Scale](<https://research.google/pubs/measuring-the-user-experience-on-a-large-scale-user-centered-metrics-for-web-applications/>) — Google Research · Peer-reviewed framework paper

## Related topics

- [Event Taxonomy](<https://wiki.soroush.uk/topic/event-taxonomy/>)
- [Instrumentation Plan](<https://wiki.soroush.uk/topic/instrumentation-plan/>)
- [Data-Informed Decision Making](<https://wiki.soroush.uk/topic/data-informed-decision-making/>)
