Mobile app metrics are the measurements that show how users discover, install, activate, engage with, and create value for an app. The most useful set connects marketing activity to post-install behavior and business outcomes.
That definition covers dozens of numbers, and no universal dashboard fits every team. A subscription app with a seven-day trial, a marketplace that earns on repeat orders, and a game funded by ads need different priorities. So do a startup still testing its first channel and a company spending seven figures a month on paid media.
This guide treats mobile app metrics as a decision system rather than a checklist. It covers the four metric groups and how to pick a small operating set for your business model. It then shows why cost per install misleads on its own, how to read results by cohort, and how to build a dashboard around each team’s decisions.
What Are Mobile App Metrics?
Mobile app metrics measure acquisition, activation, engagement, retention, and revenue. Each describes a step in the user journey, from first impression to first payment and beyond.
Three terms often get mixed up. A metric is any measured value, such as installs, day-7 (D7) retention, or average revenue per user. A KPI, or key performance indicator, is a metric the team has selected and tied to a defined business objective, with an owner and a target. A business outcome is what the company ultimately needs: contribution margin, cash flow, a growing base of paying users. Most metrics never become KPIs, and that is healthy.
The test for any metric is whether it feeds a decision. If a number can move by a fifth without anyone changing budget, creative, targeting, or the product, it is report decoration.
Metrics support decisions only when everyone calculates them the same way. That requires a written definition for every event, a stated reporting window, and an agreed attribution source. Tools disagree on basics. AppsFlyer builds cohort days on calendar days, while Adjust counts each cohort day as 24 hours from install, so D1 retention for the same users can differ between them. App Store Connect separates Sales from Proceeds, which exclude taxes and Apple’s commission, so every revenue metric should say which one it uses.
The Four Groups of Mobile App Metrics
Which mobile app metrics should you track? It depends on your business model and valuable post-install event, but almost every useful metric fits one of four groups.
Acquisition Metrics
Impressions and CPM (cost per thousand impressions) describe reach and its price. CTR (click-through rate) divides clicks by impressions, an early read on creative relevance. Store visit rate divides product page views by store impressions. CPI (cost per install) divides spend by installs, CPA (cost per action) divides it by users who complete a chosen action, and CAC (customer acquisition cost) is the full cost of a new customer. Each should name the costs and users it covers.
Activation and Engagement Metrics
Activation rate is the share of installs reaching a first meaningful action, such as a first search. Onboarding completion shows where they drop off. DAU, WAU, and MAU count daily, weekly, and monthly active users, and DAU/MAU shows how habitual use is. Session frequency and feature adoption reveal whether engagement comes from behavior that predicts revenue. Define “active” explicitly: Apple counts a session only after two seconds of use.
Retention Metrics
To measure app retention, take an install cohort and calculate the share of users who return, or perform a defined action, on a stated day after install. D1, D7, and D30 are the usual checkpoints. AppsFlyer, for example, divides unique users who opened the app that day by the cohort’s conversions. Churn is the share of users who stop using the app or cancel in a period. Cohort retention compares these curves across install dates and sources. Reactivation counts lapsed users who return, organically or through re-engagement campaigns.
Revenue and Unit Economics Metrics
ARPU (average revenue per user) divides cohort revenue by all users, while ARPPU divides it by paying users only. Conversion to payer is the share of a cohort that makes a first payment. ROAS (return on ad spend) is cohort revenue divided by spend over a stated window, such as D7 or D30. LTV (lifetime value) estimates revenue per user over a defined horizon, stated as actual or predicted. CAC payback is the time a cohort needs for cumulative margin to cover its acquisition cost.
| Metric group | What it answers | Example decision |
|---|---|---|
| Acquisition | Are installs priced sustainably? | Shift budget; pause a fading creative |
| Activation and engagement | Do new users reach first value? | Fix onboarding before scaling spend |
| Retention | Do users come back? | Re-engage a lapsing segment |
| Revenue and unit economics | Does the cohort pay back? | Raise or cap bids against target payback |
How to Choose the Right Metrics for Your App
Answer five questions before opening any analytics tool:
- Business model. Subscription, transactions, in-app purchases, advertising, or a mix.
- Valuable post-install event. The earliest action that reliably predicts revenue.
- Acquisition channels. Their reporting limits shape what you can measure by source; iOS postbacks, for example, arrive late and without user-level detail.
- Target payback period. Set it from your cash position and funding plan.
- Decision owner. A metric without an owner rarely changes anything.
The answers cut the list to a handful of mobile app metrics to track weekly, usually fewer than ten. The valuable event differs sharply by vertical:
- Subscription app: trial start, trial-to-paid conversion, first renewal, and retention of paying users.
- Ecommerce app: first purchase, repeat purchase, and contribution margin after discounts and returns.
- Fintech: completed registration including identity checks, account funding, and first transaction.
- Gaming: tutorial completion, payer conversion, and D7 retention.
- iGaming: qualified registration, first-time deposit, and repeat deposit.
In each case one event sits at the center. Some teams call it the North Star metric, but the label matters less than the discipline. Pick one outcome the whole team optimizes for, then choose two or three supporting metrics per funnel stage that explain its movements. Everything else belongs in ad hoc analysis.
A strong valuable event happens early enough to guide spend within days, correlates with revenue in your own historical cohorts, and is measured the same way on both platforms. If trial-to-paid conversion arrives only after a seven-day trial, trial start becomes the early proxy and trial-to-paid the check on it.
Why CPI Is Not Enough
CPI is not enough because low-cost installs may not activate, retain, or create revenue. It prices the first funnel step and says nothing about the steps that pay.
Consider a US grocery delivery app that spends $20,000 on each of two sources in the same month. Source A delivers installs at a $2.50 CPI: 8,000 installs, 3,200 activated users, and 640 first orders within seven days. Source B costs $4.00 per install and brings in 5,000 installs, 3,000 activated users, and 800 first orders.
On CPI, Source A looks almost 40% cheaper. Per activated user, the two sources are close, at $6.25 and $6.67. Per first order, Source B wins: $25.00 against $31.25. Assume buyers from both sources generate the same $26 in contribution margin by day 60. Source B’s cohort has then paid back its acquisition cost, and Source A’s has not.
Figure 1. Spend to payback for two traffic sources. Illustrative numbers, not benchmarks.
The ranking flips between install and first order, and only the full chain shows it. For the CAC formula and target-setting, see our guide to app user acquisition cost.
How to Read Metrics by Cohort
Cohort analysis in mobile apps groups users by a shared starting point, such as install date, source, or segment, and compares what each group does over the same time since install. Useful cuts include:
- acquisition source, campaign, and creative;
- geo and platform;
- install week or month;
- audience segment, such as new versus lapsed users.
Comparisons hold only for like-for-like cohorts. A D30 value for users who installed twelve days ago is partial, and AppsFlyer flags such periods as incomplete. Compare D7 with D7, only for cohorts past day 7. Daily and weekly cohort views don’t align either.
Attribution windows matter too: Apple’s AdAttributionKit sends up to three postbacks for conversion windows covering days 0–2, 3–7, and 8–35 after first launch, each after a random delay of up to six days. iOS data measured this way can’t be read day by day against real-time Android data. Singular advises against comparing cohort data across tools unless attribution and cohort methods match.
Example. A casual game spends $30,000 a month on each of two ad networks. At D7 they look alike: 18% ROAS on Network A, 17% on Network B. Split by creative, the cohorts diverge. On Network A, 70% of D7 payers came from one ad, and D30 retention is 6% against 9% on Network B. By D30, ROAS reaches 26% on A and 42% on B. The team moves $15,000 from A to B and briefs new concepts close to B’s best-retaining ad. If B holds 40% at the higher budget, blended D30 ROAS rises from 34% to about 36.5% on the same total spend, and the account no longer depends on one creative.
Figure 2. Same D7, different D30: the budget follows the cohort.
A Mobile App Metrics Dashboard That Supports Decisions
A mobile app metrics dashboard should include acquisition, activation, retention, revenue, and cohort quality, plus the context needed to act on them. Context means the date range, the attribution source behind each number, and a note of what changed recently. The tool matters less than the structure: most analytics platforms and mobile measurement partners (MMPs) can support these four views, and a spreadsheet can at small scale.
| View | Core metrics | Decision it informs |
|---|---|---|
| Executive | Spend, revenue, CAC payback | Overall budget and growth pace |
| UA | CPI/CPA by source, source quality, creative performance | Where the next dollar goes |
| Product | Activation, engagement, D1/D7/D30 retention | Which product step to fix first |
| Cohort | Value and behavior after install, by week and source | Whether a source holds value after install |
Keep post-install metrics next to CTR in the UA view. A creative that wins the click can still attract the wrong users, which is why creative production should be judged on downstream results. Each view should show only what its owner can change; an executive screen with thirty metrics hides the three that matter. Annotate launches, price changes, and tracking updates on every chart, so nobody reads a measurement change as a performance change.
Metrics That Often Mislead Growth Teams
Each of these looks like a signal and often behaves like noise:
- Install volume without quality. A spike in installs means little until that source’s activation and retention catch up.
- Blended averages. One overall CPI or retention figure can hide a strong geo subsidizing a weak one, or iOS masking Android.
- Premature ROAS conclusions. Many apps keep earning after D7, so an early verdict can cut a source that would have paid back. We cover the D7 versus D28 ROAS trade-off separately.
- Retention without cohort context. Overall retention can rise simply because acquisition slowed and the user base aged, not because the product improved.
- Inconsistent event definitions. If “registration” means email capture on iOS and a verified account on Android, the platform comparison is void.
- Platform-reported versus MMP-reported numbers. Self-reporting networks can count conversions under their own lookback windows, and Play Console counts only first-time installers, unlike Google Ads conversions. Pick one system of record per metric.
Conclusion: Track Metrics That Change the Next Decision
A good metric set is small, written down, and tied to owners. Start from the post-install event that predicts revenue, choose a few metrics per funnel stage, and read them by cohort and source before comparing totals. When a number moves, someone should already know what they will do: shift budget, rework a creative, fix onboarding, or adjust bids. If nobody can name that action, the metric belongs in an appendix, not on the dashboard.
Teams that need measurement setup, source-level analysis, and paid-growth optimization can work with ROCKAPP’s mobile user acquisition team.
