Cohort retention analysis groups users by when they signed up, then tracks what share of each group stays active over time. Plotting those percentages produces a retention curve; the shape - whether it flattens, keeps falling, or curves back up - tells you whether you have product-market fit, a leaky funnel, or expanding accounts.
Retention is the single number that decides whether growth compounds or leaks, so this methodology sits underneath every other metric you track. If you want the strategic layer on top of the math, pair this with the customer retention marketing guide; this post stays on the analytics - how to build the table, read the curve, and turn the read into action. Use it to diagnose SaaS churn and to see whether customer activation improvements actually stick.
What Is Cohort Retention Analysis?
Cohort retention analysis is a method for measuring how long users keep coming back, by splitting them into groups based on a shared start event and following each group forward in time. A cohort is simply a set of users who share that event - most often the week or month they signed up, but it can be any milestone: first purchase, activation, or the launch of a feature.
The reason cohorts matter is that a single blended retention number lies to you. If you look at "percent of all users active this month," a flood of new signups can mask the fact that older users are quietly leaving. Cohorting isolates each group so that improvements and decay are visible on their own timeline. You can see that your March cohort behaves differently from your June cohort - which is exactly the signal you need when you ship a change and want to know if it worked.
Three ingredients define any cohort analysis:
- The cohort key - what groups users together, usually signup month or week.
- The return event - what counts as "retained." This must be a meaningful action (logged in and did the core thing), not just "opened the app."
- The time window - the buckets you measure across, such as day 1, day 7, day 30, or month 1 through month 12.
Get the return event wrong and everything downstream is noise. "Retained" should mean the user got value, not that a background sync pinged your server.
How Do You Build a Retention Cohort Table?
A retention cohort table is a grid: each row is a cohort (the group that started in a given period), each column is the number of periods since they started, and each cell is the percentage of that cohort still active. Period zero is always 100 percent because everyone is active the moment they join.
The build is four steps:
- Pick the cohort key and grain. Monthly cohorts for slower B2B products; weekly or daily for high-frequency consumer apps. Match the grain to how often a healthy user would naturally return.
- Define the return event. Write it down as a rule: "a user is retained in period N if they performed [core action] at least once during that period."
- Bucket every user into their cohort by start date, then check each period for the return event.
- Divide and lay it out - retained users in period N divided by the cohort's original size, expressed as a percentage, placed in the grid.
Here is an example monthly retention cohort table. Rows are signup-month cohorts; columns are months since signup; cells are the percent of that cohort still active. Blank cells simply have not happened yet.
| Signup cohort | Users | Month 0 | Month 1 | Month 2 | Month 3 | Month 4 | Month 5 |
|---|---|---|---|---|---|---|---|
| Jan | 420 | 100% | 48% | 39% | 36% | 35% | 35% |
| Feb | 510 | 100% | 51% | 42% | 40% | 39% | |
| Mar | 580 | 100% | 55% | 47% | 45% | ||
| Apr | 640 | 100% | 58% | 51% | |||
| May | 710 | 100% | 61% |
Read this table two ways. Down a column shows whether newer cohorts retain better than older ones - here Month 1 climbs from 48 to 61 percent, so onboarding changes are working. Across a row shows the shape of a single cohort's decay - the January cohort drops fast, then flattens near 35 percent, which is the signal you actually care about.
How Do You Read a Retention Curve (What Shapes Mean)?
A retention curve is a single cohort's row plotted as a line: period on the x-axis, percent retained on the y-axis. Every curve starts at 100 percent and falls - the question is how it falls and where it ends up. Three shapes tell three stories.
- The flattening curve (good). Retention drops in the first few periods, then levels off to a stable plateau that stays above zero. A flat asymptote is the clearest quantitative signal of product-market fit: it means a durable core of users keeps coming back indefinitely. The height of that plateau is your retention floor.
- The curve that hits zero (bad). Retention keeps declining every period until nearly everyone is gone. No plateau means no core of habitual users - you have a leaky bucket, and any growth you buy will drain out. Fixing acquisition here is pouring water into a sieve.
- The smile curve (great). Retention falls, flattens, then curves back up - net retention exceeds 100 percent because resurrected users plus expansion revenue outweigh churn. This "smile" shows up most often in revenue retention for products with strong expansion, and it is the holy grail: the cohort is worth more over time, not less.
The practical read is: find the plateau. If the curve flattens above zero, you have a real product and your job is to raise the floor and widen the top of the funnel. If it never flattens, stop spending on acquisition and fix the product until it does.
What Is the Difference Between N-Day, Unbounded, and Rolling Retention?
How you define "retained on day N" changes the number dramatically, and mixing definitions is how teams end up arguing past each other. There are three common definitions, and they answer different questions.
| Definition | What counts as retained on day N | Best for | Trade-off |
|---|---|---|---|
| N-day (classic) | User was active on exactly day N | High-frequency products expected to be used daily | Strict; understates retention for products used weekly or on a cadence |
| Unbounded (rolling) | User was active on day N or any day after | Finding your true long-term retention floor | The most recent periods keep changing as users return later |
| Bracket / range | User was active at any point within a window around day N (e.g. days 5-9 for "day 7") | Products with a natural weekly or monthly rhythm | Requires choosing sensible brackets; less standardized |
N-day retention is the strictest and produces the lowest, spikiest curves - fine for a product people should open every day, punishing for one they use every couple of weeks. Unbounded retention counts a user as retained on day N if they were active then or at any later point, which smooths the curve and reveals the real floor, at the cost of recent numbers still moving. Bracket retention splits the difference by allowing a window. The rule: match the definition to how often a satisfied user would naturally come back, and never compare a curve built one way against a curve built another.
What Are Common Cohort Analysis Mistakes?
Most bad retention decisions trace back to a handful of methodology errors, not to the product itself.
- Using a weak return event. Counting "opened the app" or "logged in" inflates retention and hides churn. Anchor on the core value action - the thing that maps to your activation aha moment.
- Reading blended retention instead of cohorts. A single site-wide number lets a surge of signups disguise decaying older cohorts. Always cohort before you conclude.
- Judging young cohorts too early. The most recent cohorts only have a few periods of data, so their curves look artificially high. Compare cohorts only at the same age.
- Cohorts too small to trust. A 20-user cohort swings wildly on a few churns. If groups are thin, widen the grain from weekly to monthly.
- Confusing survivorship with health. A high plateau built on a tiny surviving fraction is not the same as broad retention. Watch both the floor and the size of the cohort reaching it.
- Ignoring the difference between logo and revenue retention. Users can churn while revenue grows (or vice versa). For the revenue view and its benchmarks, see net revenue retention.
How Do You Turn Cohort Insights into Action?
A cohort table is only useful if it changes what you do next. Read the shape, then act on where the curve fails.
- Steep early drop (periods 0-2). This is an onboarding and activation problem - users never reached value. Fix the first-run experience and the path to the aha moment. Tightening early activation is the highest-leverage retention work you can do.
- No plateau (curve heads to zero). The product is not yet habit-forming for anyone. Pause paid acquisition, interview churned users, and rebuild the core loop before you scale spend.
- Plateau too low. You have a core but it is small. Segment your best cohorts, find what the survivors have in common, and steer more new users into that pattern. Reinforce it with lifecycle messaging - the tactics in churn prevention marketing raise the floor.
- Flat but flat (no smile). Retention is healthy but not expanding. Add expansion paths - upsells, seats, usage tiers - to bend the curve upward into a smile.
Close the loop by shipping one change, tagging the cohort that experiences it, and comparing that cohort's curve against the prior one at the same age. That is the whole point of cohorting: it turns "did our change help?" from an opinion into a measurement you can read straight off the table.
Pair retention analysis with startup attribution modeling to separate channels that acquire retained customers from those that churn.
TL;DR
- Cohort retention analysis groups users by a shared start event and tracks what percent stay active over time - so improvements and decay are visible instead of hidden in a blended number.
- The cohort table is rows = signup cohorts, columns = periods since signup, cells = percent retained. Read down columns to compare cohorts, across rows to see decay shape.
- Curve shapes: flattening above zero = product-market fit; falling to zero = leaky bucket; falling then rising = the smile curve (net retention over 100 percent).
- Definitions matter: n-day is strictest, unbounded reveals the true floor, bracket fits natural cadence - never compare curves built different ways.
- Common mistakes: weak return events, blended reads, judging young cohorts too early, and tiny cohorts.
- Act on the shape: steep early drop -> fix activation; no plateau -> fix the core loop before scaling; low plateau -> raise the floor; flat -> add expansion.
FAQ
What Is Cohort Retention Analysis?
Cohort retention analysis is a method for measuring how long users keep coming back by grouping them into cohorts based on a shared start event - usually the week or month they signed up - and tracking what percentage of each cohort remains active over successive periods. Because each group is followed on its own timeline, cohort analysis reveals whether retention is improving or decaying, which a single blended retention number would hide.
How Do You Read a Retention Curve?
Plot one cohort's retention percentage against periods since signup and look at the shape. A curve that drops then flattens to a stable plateau above zero signals product-market fit - a durable core of users keeps returning. A curve that keeps falling to zero means no habitual core, a leaky bucket. A curve that falls, flattens, then rises is the smile curve, where expansion and resurrection push net retention above 100 percent. The key move is to find the plateau: its height is your retention floor.
What Is the Difference Between N-Day and Unbounded Retention?
N-day retention counts a user as retained only if they were active on exactly day N, which suits products meant to be used daily but understates retention for products used on a slower cadence. Unbounded (rolling) retention counts a user as retained on day N if they were active then or on any later day, which smooths the curve and reveals the true long-term floor, at the cost of recent periods continuing to change as users return. Match the definition to how often a satisfied user would naturally come back.
What Counts as a Good Retention Plateau?
A good plateau is any level where the curve stops declining and holds steady above zero, because a flat asymptote is the clearest evidence of product-market fit. The healthy benchmark varies by product type - daily consumer apps aim higher on short windows, while B2B SaaS looks at monthly plateaus - so the more important test than a universal number is that the curve flattens at all and that newer cohorts plateau higher than older ones.
What Is the Most Common Cohort Analysis Mistake?
The most common mistake is choosing a weak return event, such as "opened the app" or "logged in," which inflates retention and hides real churn. Retention should be defined by the core value action that maps to your product's aha moment. Close behind are reading blended retention instead of cohorts, and judging the most recent cohorts too early when they have only a few periods of data and look artificially high.