Mobile app KPIs: the metrics that actually predict growth

A mobile app KPI is a number that tells you whether the product is working: are people coming back, are they engaged, are they paying, and is the app stable. This is a reference glossary of the metrics that matter, with a plain-English definition, the formula, and a healthy benchmark for each, followed by how to group them and how to pick the few you should actually track.

By Kanika Mathur, Head of Service Delivery

Reviewed by Resourcifi engineeringPublished Feb 13, 2026Updated Feb 13, 202610 min read

Analytics

Key takeaways

The short version

Retention is the headline KPI. A typical app keeps roughly a quarter of users on day 1, around an eighth by day 7, and under a tenth by day 30, so day 30 retention is the clearest early read on product-market fit.
Stickiness, the DAU divided by MAU ratio, shows how habitual the app is. Around 20 percent is healthy for most apps, while social and messaging apps run much higher.
Money KPIs come in pairs. ARPU spreads revenue across every user, ARPPU only across payers, and lifetime value must beat acquisition cost by a comfortable margin to grow profitably.
Quality is measurable. Crash-free users and sessions, plus your store rating, gate everything else, because an unstable or poorly rated app loses installs and reviews before any growth tactic can help.
Track few, not many. Pick one north-star plus a handful of supporting KPIs across acquisition, engagement, monetization, and quality, and benchmark inside your own category rather than against unrelated apps.

The mobile app KPI glossary

The core mobile app KPIs are retention, stickiness, churn, conversion, ARPU and ARPPU, lifetime value, customer acquisition cost, crash-free rate, and store rating. Each answers a different question: are people coming back, how often, how many leave, how many pay, how much they are worth, what they cost to acquire, and how reliable the app feels. The table below gives the definition, the formula, and a healthy benchmark for each. Treat the benchmarks as directional and typical, not guarantees, because the right number depends heavily on your category.

Mobile app KPIs: what each measures, how it is calculated, and a healthy benchmark
KPI	What it measures	How it is calculated	Healthy benchmark
DAU and MAU	Daily and monthly active users	Count of unique users active in a day, and in a 28 to 30 day window	Grows with installs; read alongside stickiness
Stickiness (DAU/MAU)	How habitual the app is	DAU divided by MAU, as a percentage	Around 20 percent is healthy; social apps far higher
Day 1 retention	Returning the day after install	Users active on day 1 divided by users on day 0	Roughly 25 percent across categories
Day 7 retention	Returning after a week	Users active on day 7 divided by users on day 0	Roughly 12 to 13 percent across categories
Day 30 retention	Returning after a month	Users active on day 30 divided by users on day 0	Roughly 6 to 7 percent across categories
Churn rate	Users or revenue lost in a period	Users lost in the period divided by users at the start	The inverse of retention; lower is better
Conversion rate	Free users who take the key action	Users who convert divided by eligible users	Freemium often 2 to 5 percent; trials can exceed 25 percent
ARPU	Average revenue per user	Total revenue divided by all active users	Category dependent; track the trend
ARPPU	Average revenue per paying user	Total revenue divided by paying users only	Always higher than ARPU; track the trend
Lifetime value (LTV)	Total revenue from a user over time	ARPU times average lifetime, adjusted for margin and churn	Should exceed CAC by a wide margin
Customer acquisition cost (CAC)	Cost to acquire one paying user	Acquisition spend divided by users acquired	LTV to CAC of about 3 to 1 or higher
Crash-free users	App stability per user	1 minus crashed users divided by all users	Aim for 99.9 percent or higher
Crash-free sessions	App stability per session	1 minus crashed sessions divided by all sessions	Top apps reach 99.95 percent or higher
Store rating	Public quality signal	Average of recent star ratings on the store	Keep above 4.0, ideally near 4.5

If you are still scoping the product, decide which of these you can even measure before you build, because instrumentation is far cheaper to add early. Our guide on how to build an app covers where analytics fits in the plan.

Mobile app KPIs by group

It helps to sort KPIs into four groups that map to the user lifecycle: acquisition, engagement, monetization, and quality. Acquisition tells you how cheaply and effectively you bring users in. Engagement tells you whether they stay and form a habit. Monetization tells you whether that attention turns into revenue. Quality tells you whether the experience is reliable enough to sustain the other three. A balanced dashboard carries at least one KPI from each group, because optimizing one in isolation usually damages another.

Acquisition: installs, customer acquisition cost, and install-to-signup or install-to-trial conversion. These show whether growth is efficient, not just large.
Engagement: DAU, MAU, stickiness, session length, and day 1, 7, and 30 retention. These show whether the app earns a place in the user's routine.
Monetization: ARPU, ARPPU, lifetime value, paid conversion, and trial-to-paid rate. These show whether attention becomes durable revenue.
Quality: crash-free users and sessions, app start time, and store rating. These are the floor; weak quality quietly caps acquisition and retention.

Quality and engagement are tightly linked. Apps that are unstable tend to lose ratings, and a low rating depresses installs, so stability work is growth work. For products with paid tiers, the monetization group connects directly to your pricing model; see app monetization strategies for how the model shapes which KPIs matter most.

Reading benchmarks without fooling yourself

Benchmarks are useful as a sanity check, not a target. Cross-category averages hide enormous variation, so a number that looks weak for a social app can be excellent for a niche utility. Industry data puts typical retention near 25 percent on day 1, around 12 to 13 percent on day 7, and 6 to 7 percent on day 30, with stickiness near 20 percent for many apps. On quality, leading apps hold crash-free sessions above 99.9 percent and keep store ratings above 4.0. Use these to spot order-of-magnitude problems, then benchmark seriously against your own category and your own past cohorts.

~25%

Typical day 1 retention across app categories, falling to roughly 6 to 7 percent by day 30.

AppsFlyer

~20%

A healthy stickiness ratio, meaning daily actives are about a fifth of monthly actives.

Mixpanel

99.9%

Crash-free target that strong apps hold to protect ratings and retention.

Firebase

One practical rule: never compare a raw number across categories without context. A games app and a banking app have completely different usage rhythms, so their healthy retention curves and stickiness look nothing alike. Compare like with like, and weight your own trend over any external figure.

How to choose which KPIs to track

Pick one north-star metric that best captures real value for your app, then support it with a small set of KPIs across the four groups. For a subscription app the north-star is often retained paying users or net revenue retention; for a content app it may be weekly active users; for a marketplace it may be completed transactions. Around that north-star, track one acquisition KPI, two or three engagement KPIs, one or two monetization KPIs, and at least one quality KPI. Resist the urge to watch everything, because a dashboard with fifty metrics hides the five that move the business.

Start from value: choose the single metric that means a user got what they came for, and make it your north-star.
Cover every group: add at least one KPI each from acquisition, engagement, monetization, and quality so no blind spots remain.
Make them actionable: keep KPIs a team can influence this quarter, and pair each with the lever you would pull to move it.
Review on a cadence: trend KPIs over cohorts and weeks, not single days, and revisit the set as the product matures.

Choosing KPIs early also informs scope and cost, because the metrics you commit to measuring shape what you instrument first. See our breakdown of MVP cost and timeline for where analytics belongs in a first build, or talk to our mobile app development team about instrumenting these KPIs from day one.

Frequently asked

Mobile app KPI questions

What are the most important mobile app KPIs?

The metrics that matter most are retention, stickiness, and a money pair of revenue and cost. Retention on day 1, day 7, and day 30 shows whether people come back, and stickiness shows how habitual the app is. On the money side, lifetime value must comfortably exceed customer acquisition cost. Quality KPIs like crash-free rate and store rating sit underneath all of these, because an unstable or poorly rated app loses users before any growth tactic can help.

What is a good app retention rate?

There is no single good number, because retention varies sharply by category and use frequency. As a rough cross-industry guide, typical apps keep about a quarter of users on day 1, around an eighth by day 7, and under a tenth by day 30. Day 30 retention is the figure most teams watch, since it is the clearest early signal of product-market fit. The honest way to judge yourself is against your own category and your own past cohorts, not a global average.

What is the DAU MAU stickiness ratio?

Stickiness is daily active users divided by monthly active users, expressed as a percentage. It tells you how often a typical monthly user actually opens the app. A ratio near 20 percent is healthy for many apps and means roughly one in five monthly users is active on a given day. Social and messaging apps run far higher because people check in many times a day, while occasional-use apps run lower. Read it alongside retention rather than on its own.

What is the difference between ARPU and ARPPU?

ARPU is average revenue per user and divides total revenue across every active user, including people who never pay. ARPPU is average revenue per paying user and divides the same revenue only across the users who actually spend. ARPPU is always higher than ARPU. If an app earns ten thousand dollars from ten thousand users where only two hundred pay, ARPU is one dollar while ARPPU is fifty dollars. Track both, because each answers a different question about your revenue.

What is a good crash-free rate for an app?

Crash-free users is the share of people who used the app without hitting a crash, and crash-free sessions is the share of sessions that did not end in one. Strong consumer apps aim for crash-free sessions of 99.9 percent or higher, and the best teams reach 99.95 percent and above. High-stakes apps like banking and healthcare target the higher end. Stability matters beyond comfort, because apps that crash more often tend to attract lower store ratings, which then reduces installs.

How can I improve my app store rating?

Start with stability and performance, because crashes and slow launches drive most one-star reviews. Then ask for a rating at a happy moment, such as just after a user completes a valuable action, rather than on launch. Respond to reviews and ship fixes for the complaints you see repeated, since visible responsiveness lifts scores over time. Most stores weight recent ratings more heavily, so steady improvement compounds. Aim to stay above four stars, ideally near four and a half, to protect downloads.

Kanika Mathur

Head of Service Delivery, Resourcifi

I am Kanika Mathur, Head of Service Delivery at Resourcifi. We help product teams decide which KPIs to track before they build, then instrument them properly, because the wrong dashboard hides the few numbers that actually predict growth. This glossary reflects the metrics we set up and watch with clients across the apps we have shipped since 2017.

Resourcifi on LinkedIn →

Sources

AppsFlyer, app retention benchmarks, 2025 (day 1, 7, and 30 retention across mobile categories).
Firebase Crashlytics, crash-free metrics documentation (definitions, formulas, and recommended targets).
Mixpanel, monthly active users and stickiness, 2024 (DAU/MAU ratio benchmarks and methodology).
App Radar, Google Play ratings and reviews guide, 2024 (app store rating thresholds and best practices).