Metrics·Glossary term

Customer Retention

Customer Retention A/B testing Reference guide

Customer Retention is a concept used in metrics, kpis & business outcomes.

Quick definition: Customer retention is the proportion of a defined customer or account population that remains active, subscribed, or purchasing at a stated later point or throughout a stated period.

What is customer retention?

Customer retention measures whether a business continues relationships after acquisition. The appropriate definition depends on the product: a subscription account may be retained when its paid plan remains active; a retailer may retain a customer when they make another purchase; a workflow product may retain an account when it completes a meaningful activity. “Active” must reflect normal use rather than an easy-to-trigger event.

Retention is not engagement, renewal rate, repeat purchase rate, or churn, though they are related. Engagement counts behavior intensity. Renewal rate focuses on contracts reaching a renewal decision. Repeat purchase rate asks whether buyers purchase again. Churn measures losses. Retention asks what share of an initial or eligible population is still present under the agreed rule. A product can show high daily engagement among retained users while retaining only a small fraction of its original cohort.

The central analytical choice is cohort definition. Acquisition cohorts group customers by first purchase or signup period; behavioral cohorts group them by a shared first meaningful event. Compare customers with equal opportunity to return. A January cohort observed at day 30 should not be compared with a February cohort observed at day 10.

Retention formulas and denominators

For a fixed cohort, the formula is:

retention rate at time t = cohort members meeting retained definition at time t / original eligible cohort members × 100

A period formula can instead use the starting base: period retention = customers from the starting base still retained at period end / customers in starting base × 100. Keep new customers acquired during the period out of that denominator unless the metric is specifically net customer-base growth. This prevents acquisition from disguising attrition.

Retention typeRetained conditionBest use
Subscription retentionPaid subscription still activeRecurring-contract businesses
Activity retentionMeaningful product action in periodUsage-driven products
Repeat-purchase retentionAnother qualifying orderCommerce with repeat cycles
Revenue retentionRecurring revenue preservedAccount expansion and contraction analysis

Choose the interval from user behavior and decision needs. Day-1 retention suits a daily consumer product; 90-day retention may be meaningful for enterprise software or seasonal retail. Do not compress a long lifecycle into an arbitrary daily active-user rule.

Customer retention in A/B testing

Retention is a crucial outcome or guardrail for onboarding, reliability, pricing, plan changes, personalization, and product-value experiments. It captures durability better than a first-session click. It also matures slowly, so a short test may use validated leading indicators while holding a sample for longer follow-up. Treat a leading metric as evidence, not as a substitute for observed retention.

Randomize before the intervention, retain the original assigned population, and define retention with information available consistently in both arms. Do not analyze only customers who clicked an email, completed a setup task, or made a first purchase after exposure; these are potentially affected by treatment. For team products, choose account-level retention if account-level treatment and value are shared.

Before launch, specify the horizon, baseline, minimum meaningful difference, and decision rule. A small point estimate in a rare 90-day outcome can have a wide interval. Sample-size planning and test duration should reflect the actual observation window; see sample-size planning and A/B test duration. Pair retention with customer support, refunds, margin, and service-quality measures.

Worked retention calculation

A product tests a guided first-project flow among 6,000 new workspaces in each arm. Retention means completing at least one successful production task during days 22–28 after signup. Control retains 1,620 workspaces; treatment retains 1,800.

control day-28 retention = 1,620 / 6,000 = 27.0%
treatment day-28 retention = 1,800 / 6,000 = 30.0%
absolute lift = +3.0 percentage points
relative lift = 11.1%

The team checks that the guided flow did not merely make the tracked task easier to trigger. It inspects task quality, failure rates, account cancellation, support contacts, and day-60 behavior. It also confirms that all workspaces had a full 28-day observation opportunity and that setup events were not used to remove non-completers from analysis.

Retention data-quality caveats

Retention data requires stable identity across devices, products, account merges, and billing changes. Define how anonymous visitors become known customers, how a company’s workspace maps to a billing account, and how migrations are treated. A missing activity event can reflect tracking loss rather than disengagement; reconcile telemetry with backend records when the retained action is critical.

Product seasonality and usage cadence can produce false churn. Tax software, travel products, and quarterly reporting tools have expected gaps. Use a retained event and interval that fit the product’s natural cycle, and report cohorts rather than an undifferentiated active base. Avoid silently excluding customers who were not sent a message, because delivery may be influenced by the treatment or data gaps.

Definitions should be versioned. Changing “retained” from any login to a successful task may be an improvement in measurement, but it breaks historical comparability unless both measures are retained and clearly labeled.

Common retention mistakes

  • Including new acquisitions in a starting-base denominator: acquisition can hide losses.
  • Using a trivial retained event: a passive page load may not represent continuing value.
  • Comparing cohorts with unequal age: newer cohorts need equal follow-up.
  • Mixing user and account retention: shared products require a deliberate unit.
  • Removing post-treatment non-engagers: this biases an experiment.
  • Ignoring lifecycle cadence: expected absence is not always attrition.

Frequently asked questions

Is retention the opposite of churn?

They are often related, but definitions and periods must match before treating them as complements.

What is a good retention rate?

It depends on the product’s usage cycle, customer intent, and retained-event definition. Compare equivalent cohorts and focus on durable improvement.

Should retention be measured by users or accounts?

Use the unit that receives value and treatment. Collaborative products often need account or workspace retention.

Can a short A/B test prove a retention effect?

Only if the full retention window is observed with enough sample. Otherwise describe leading signals separately from mature retention.

Why did engagement rise but retention not move?

The treatment may increase short-term activity without changing sustained value, or the retained metric may be more demanding than the engagement event.

Summary

Customer retention is the share of a defined cohort or starting base that remains under a meaningful rule after equal follow-up. Define the unit, activity or subscription condition, interval, and exclusions before analysis. In A/B tests, preserve assigned populations and treat retention as a durable outcome alongside quality, cost, and support guardrails.

Sources