Product Analytics

Product Analytics

The analytical discipline of measuring what users do inside a product, why, and whether it creates value — then feeding that back into product decisions. Distinct from generic web analytics (page-level) and from instrumentation (the plumbing). Product analytics is event-centric, user-centric, and decision-oriented.

This skill covers the analysis layer. Leave to adjacent skills:

Overview

A product-analytics practice answers four recurring questions: (1) Are users reaching value (activation)? (2) Do they keep coming back and going deeper (engagement/adoption)? (3) Where do they drop off (funnels/paths)? (4) Is the whole thing growing toward a single meaningful outcome (North Star)? The analytical quality of every answer is capped by the quality of the event taxonomy underneath it — so taxonomy and governance come first, not last.

Core Concepts

1. Event taxonomy & tracking plans

A taxonomy is the hierarchical naming + classification scheme for events and properties so a platform can produce comparable insights. Design it deliberately before instrumenting.

2. North Star metric (NSM) framework

A single metric that best captures the value customers get, that product/marketing can influence, and that leads revenue.

3. Funnel & conversion analysis

Map an ordered multi-step flow, measure step-to-step conversion, diagnose the biggest drops.

4. Activation & the “aha moment”

Activation = the set of early actions that correlate with later retention. The “aha moment” is when the user internalizes core value; the activation metric is its measurable proxy.

5. Feature adoption (breadth / depth / time / duration)

6. Engagement & stickiness (DAU/WAU/MAU)

7. Session & path analysis

8. Metric frameworks: AARRR vs HEART

9. Experimentation operations (the ops layer, not the stats)

10. Governance & data quality

Tools / Frameworks

Tool Strength Notes (2025–26)
Amplitude Behavioral cohorts, governance, metric trees, Journeys Best for analysis depth + cross-functional scale; MTU pricing. (Amplitude best tools, 2026)
Mixpanel Fast event analytics, clean funnels/reports Relaunched experimentation + added flags/replay late 2025; event-based pricing. (Cotera comparison, 2026)
PostHog All-in-one for dev-led teams (analytics + flags + experiments + replay + warehouse) Modular, open-source, self-host option. (PostHog alternatives, 2025)
Heap Autocapture — records everything, define events retroactively Fast start, less upfront taxonomy discipline. (PostHog Heap alternatives, 2025)
June Pre-built SaaS company-level reports on top of Segment Lightweight, B2B-oriented; thinner than the majors for deep analysis.
Avo Tracking-plan governance + Inspector observability Sits upstream of the analytics tool to guarantee data quality. (Avo, 2025)
Statsig Experimentation-first unified pipeline Strong ops/experiment scale; CUPED/sequential built in. (Statsig vs PostHog, 2025)

Frameworks summary: Taxonomy (Object-Action) → NSM + inputs (metric tree) → lifecycle lens (AARRR) or UX lens (HEART) → activation/aha → adoption (breadth/depth/time) → funnels & paths → governance loop.

Methodology (end-to-end)

  1. Frame the decision — what product question are we answering? (Don’t start from “what can we track?”)
  2. Define the taxonomy — Object-Action events + properties, owners, in a versioned tracking plan.
  3. Pick the NSM + 3–5 inputs; draw the metric tree.
  4. Instrument & validate (hand to instrumentation/governance) — verify live events match the plan.
  5. Establish activation — find the aha-moment metric empirically; validate against retention.
  6. Build core funnels (4–7 steps, stated window) and run path analysis to discover real journeys.
  7. Measure adoption & engagement — adoption rate, breadth/depth, DAU-WAU-MAU/stickiness, segmented.
  8. Experiment to move inputs; read out against pre-registered metrics.
  9. Review quarterly — prune the taxonomy, re-validate the NSM, refresh benchmarks.

Practical Patterns

Anti-Patterns

Troubleshooting

References