Product Analytics: Funnels, Retention & Cohorts

Product Analytics

Product analytics is the discipline of understanding how people actually use your product, by analyzing the events they generate. Where web analytics focuses on traffic and acquisition, product analytics focuses on behavior inside the product: which features get used, where users drop off in a flow, whether they come back, and which segments behave differently. Tools like Amplitude, Mixpanel, and PostHog are built for exactly these questions.

Its power comes from three core lenses — funnels (where do users drop off?), retention (do they come back?), and segmentation (who behaves how?). Together they turn raw events into the insight product teams use to reduce friction, prioritize work, and grow.

TL;DR

Analyzes in-product behavior from event data, tied to persistent users.
Funnels reveal where users drop off; retention/cohorts show whether they return.
Segmentation explains who behaves differently and why.
Powers product decisions: what to fix, build, and double down on.

Quick Example

A funnel measures drop-off between steps of a flow:

The Core Analyses

Funnels

A funnel tracks users through a sequence of steps (signup, onboarding, checkout) and shows drop-off at each. The biggest drop is usually the highest-leverage thing to fix. Funnels turn "our signup is bad" into "62% enter their email but only half verify it."

Retention & cohorts

Retention measures whether users come back over time; cohort analysis groups users (e.g. by signup week) and tracks each group's behavior, so you can see whether a product change actually improved retention for newer users. Retention is the truest signal of product-market fit — acquisition without retention is a leaky bucket.

Segmentation

Breaking metrics down by segment — plan, source, geography, behavior — reveals patterns averages hide: power users vs casual, one channel's users retaining far better than another's. Segmentation is how you turn an aggregate number into an actionable insight.

Key Metrics

Activation — % of new users reaching the "aha" moment / first value.
Retention — % returning over day/week/month (D1, D7, D30).
Engagement — DAU/WAU/MAU and stickiness (DAU/MAU).
Feature adoption — % using a feature, depth of use.
Conversion — completion of key flows (see Conversion Optimization).

💡 Define a North Star metric that captures core value delivered (e.g. "weekly active teams"), and connect feature work to it.

Best Practices

Instrument with a tracking plan — funnels and retention are only as good as consistent events.
Start from questions ("where do new users drop off?") not dashboards.
Use cohorts to judge whether changes actually moved retention.
Segment before concluding — averages hide the real story.
Pair quantitative with qualitative — analytics shows what, user research shows why.

Common Mistakes

Watching vanity metrics

Concluding from averages

FAQ

How is product analytics different from web analytics?

Web analytics (GA4) centers on traffic and acquisition — where visitors come from and whether they convert — largely around sessions. Product analytics centers on behavior inside the product: which features users engage with, where they drop off in flows, and whether they retain, all tied to persistent user identities and analyzed through funnels, retention, and cohorts. They're complementary — web analytics for marketing, product analytics for the product experience — and increasingly fed from the same event stream. See Analytics Platforms.

Why is retention more important than acquisition?

Because acquisition without retention is a leaky bucket — you pour users in the top and they drain out the bottom, so growth stalls no matter how much you spend. Retention measures whether the product delivers lasting value, which is the truest signal of product-market fit. Improving retention also compounds: retained users generate more revenue, referrals, and data over time. Most durable growth comes from retaining and expanding users, with acquisition layered on top of a product people keep using.

What is cohort analysis and when do I use it?

Cohort analysis groups users by a shared characteristic — usually their signup period — and tracks each group's behavior (typically retention) over time. It's how you tell whether a product change actually helped: if the cohort that signed up after your onboarding revamp retains better than earlier cohorts, the change worked. Aggregate metrics blur this because they mix old and new users; cohorts isolate the effect on comparable groups, making them essential for judging whether improvements move the needle.

What's a North Star metric?

A North Star metric is the single measure that best captures the core value your product delivers to users — for example, "weekly active teams" for a collaboration tool, or "nights booked" for a marketplace. It aligns teams around outcomes rather than vanity numbers, and you connect feature work to it by showing how a change drives the inputs that feed it. A good North Star reflects retained value (not just signups), so it grows only when you're genuinely serving users.