Content
Try for free

Mobile App Retention Rate: How to Calculate and Improve

Mobile app retention rate is the share of users from a starting group who are still using your app, or still paying for it, after a set period. The app retention rate formula is: retention rate = (users from the cohort who are active on day N ÷ users in the cohort) × 100. A cohort is everyone who installed the app, or started a trial, in the same period.

There is no single good retention rate for an app. It depends on your category, your pricing model, how you define "active" and which day you measure. The reliable way to judge your number is to compare your own cohorts over time and to test changes against each other. This guide shows how to calculate it, which app retention metrics to track and how to increase app retention.

What mobile app retention rate measures

Retention answers one question: of the people who showed up, how many stayed? It is the mirror image of churn. If a cohort retains a given share of users on day N, the remaining share has churned by then.

Two details cause most of the confusion:

  • The cohort. Decide who counts as a starting user: an install, a registration, a first purchase or a trial start. Mixing these gives numbers that cannot be compared.
  • The activity event. Decide what counts as "retained". Opening the app is the loosest definition. A meaningful action, such as completing a workout, a lesson or a chat, is more honest for most subscription apps.

Write both definitions down once and reuse them in every report. Most disagreements about retention between marketing and product come from different definitions, not different data.

How to calculate app retention rate, step by step

You can do this in a spreadsheet or in your analytics tool. The logic is the same.

  1. Pick a cohort. For example, all users who installed the app in a given week.
  2. Pick a retention day. Choose the day after install you want to measure, such as the day after, a week later or a month later. Use the same days every time.
  3. Count the starting users. This is the size of the cohort.
  4. Count the retained users. These are cohort members who performed your activity event on the chosen day.
  5. Divide and multiply by 100. Retained users ÷ starting users × 100 is the retention rate for that cohort on that day.
  6. Repeat for each cohort. Put cohorts in rows and days in columns. This grid is the retention curve.

To get the churn side, subtract the retention rate from 100. To get a subscription version, replace "active in the app" with "subscription still active" and count paying users in the starting cohort instead of installs.

Read the curve, not a single number. A curve that drops quickly and then flattens means a core group of users has found value. A curve that keeps falling with no flat part means the product is not yet sticky for anyone. Check the formula against your own data before you act on it, and sanity-check that cohort sizes match what your attribution tool reports.

Which app retention metrics to track

Retention is not one metric. Three versions are common, and they answer different questions. Here they are side by side.

What it counts

  • Classic N-day retention: users who were active on exactly day N after install.
  • Rolling retention: users who were active on day N or any later day.
  • Subscription retention: subscribers whose plan is still active after N billing periods.

Best used for

  • Classic N-day retention: judging onboarding and early habit formation.
  • Rolling retention: apps used irregularly, where a missed day does not mean the user left.
  • Subscription retention: revenue planning, LTV estimates and paywall decisions.

Watch out for

  • Classic N-day retention: it looks harsh for apps with weekly or occasional use.
  • Rolling retention: it can only go down and hides users who are effectively gone.
  • Subscription retention: a user can stay subscribed and never open the app, so pair it with usage data.

Alongside these, track a few neighbouring app retention metrics: churn rate, stickiness (daily active users divided by monthly active users), sessions per user, time to first key action and refund rate. Break every one of them down by acquisition source and by onboarding path. An average hides the fact that users from one channel may retain far better than users from another. If your analytics setup is still taking shape, the web2wave analytics guide covers what to send to which tool.

What is a good retention rate for an app?

A good retention rate for an app is one that is stable or rising across cohorts and high enough that your lifetime value covers your cost to acquire a user. Published averages are tempting, but they mix categories, platforms, definitions and traffic quality. A meditation app with daily use and a language app with lessons several times a week should not be judged against the same line.

Use these reference points instead:

  • Your own history. Compare this month's cohort with last month's at the same day N.
  • Your own channels. If paid social retains differently from organic or influencer traffic, that tells you where to spend.
  • Your own economics. Work out your break-even point. Take your cost per paying subscriber and your average revenue per subscriber per period. The number of periods a subscriber must stay to cover that cost is the retention you need. Every figure comes from your data, so no outside benchmark is required.
  • Your own product shape. If the product is meant for a short, goal-based programme, a flat curve may never happen, and completion rate may matter more than long-term retention.

As a public example, MyMental AI GURU reports that about 55% of its subscribers remain active, with refunds under 5% of revenue and paying users from 40+ countries. That figure describes one app, one audience and one definition of active. Treat it as an example of how to report retention, not as a target.

How to increase app retention

Retention is mostly decided early. Users who reach value quickly come back, and users who do not rarely return. Work through these levers roughly in order.

  1. Shorten the time to the first result. Find the action that your retained users usually perform early, and remove steps between install and that action.
  2. Personalize onboarding. Ask a few questions about goals, level and schedule, then reflect the answers back in the first session. A plan that feels built for the user gives them a reason to return.
  3. Set expectations before the paywall. Users who understand what the subscription includes, what renews and when, are less likely to refund or cancel in frustration. Clear pricing and easy cancellation also protect your reputation.
  4. Build a reason to return. Streaks, scheduled sessions, progress views and new content all work when they match the product. Reminders help when they are relevant and not frequent.
  5. Use lifecycle messages. Push notifications and email sequences that react to behaviour, such as a skipped session or an unfinished lesson, bring back users who would otherwise drift away.
  6. Fix the leaks you can see. Look at where cohorts drop most: the first session, the first week or the first renewal. Address the biggest drop first.
  7. Test one change at a time. Split users into groups, change one thing and compare retention at the same day N. The A/B testing guide explains how to avoid reading noise as a result.
  8. Match acquisition to the product. If one channel brings users who churn quickly, retention work in the app will not fully compensate. Adjust targeting and messaging so the promise in the ad matches what the app delivers.

Allow enough time and enough users in each test. Early retention days settle quickly, while later days need patience, so decide in advance which day N you will judge by.

How web onboarding funnels can support retention

Retention starts before the install. A web2app funnel moves onboarding and payment to the web: an ad leads to a landing page or quiz, then a personalized plan, a paywall and payment, and finally the user installs the app and logs in. Because the user has already told you their goal and has already paid, they open the app with intent and context. Whether that improves your retention is something to measure with your own cohorts, not assume.

Funnels also give you a place to run the tests listed above without waiting for an app release. You can change quiz questions, plan wording and paywall order and compare the resulting cohorts. The same quiz data can feed personalization in the app and lifecycle messages after install.

If you want to try this without building it in-house, web2wave is one option. It is a no-code builder for web2app funnels, with quiz and onboarding flows, web paywalls, A/B experiments, UTM attribution, a user CRM, email sequences and AI localization. It connects to subscription tools such as RevenueCat, Adapty, Qonversion, Superwall and Apphud and to analytics tools such as Amplitude, PostHog and Mixpanel, so retention can be tracked by funnel variant (see the integrations overview). Over 3,000 web funnels are active on the platform. For a public example of scaling a funnel across markets, see Leya AI, which scaled its funnel roughly tenfold with localization.

One caution: store rules on selling subscriptions outside the app vary by region and change over time. Before you move payments to the web, check the current App Store Review Guidelines and Google Play policy, and read the web2app funnel compliance guide. Nothing here is legal advice, and the commission you can avoid depends on where and how you sell.

FAQ

What is the formula for app retention rate?

Retention rate = (users from the cohort who are active on day N ÷ users in the cohort) × 100. Define the cohort, the activity event and the day N before you calculate, and keep them the same across reports.

How do I calculate app retention rate if I have little data?

Use weekly cohorts instead of daily ones so each group is large enough to read. Calculate the rate for the same day N for each cohort and compare the cohorts. If a group is very small, treat the result as a signal to watch, not a conclusion.

What is a good retention rate for an app?

It is the rate at which your cohorts hold steady or improve and your subscribers stay long enough to cover your acquisition cost. Compare your own cohorts, channels and break-even point instead of a generic industry average.

What is the difference between retention and churn?

They are two sides of the same measure. Retention is the share of a cohort that stays, and churn is the share that leaves. Subtract one from 100 to get the other. Churn is often reported per billing period for subscriptions.

How can I increase app retention fastest?

Start with the biggest drop in your cohort curve. For many apps that is the first session, so shortening the path to the first valuable action and personalizing onboarding are usually the first tests. Change one thing at a time and compare cohorts at the same day N.

If you want to see how a web2app funnel could fit your retention plan, book a demo or start free.

Share this Article

Build your web funnel with web2wave

Start using web funnels: Launch faster, convert better, and keep more revenue with no app store limitations