LTV is the central economic measure of a mobile-app business. It answers: "what is the total revenue a single user generates over their relationship with this app?" Every UA decision sits inside the LTV / CPI ratio. If your LTV is $30 and your blended CPI is $8, you can afford to buy almost any user on any channel β you'll recoup 3-4Γ your spend. If your LTV is $4 and your CPI is $8, you're burning cash on every install. All paid acquisition strategy fits inside that single ratio.
That $0.02 median D30 LTV is a derived IAP-only proxy β computed by multiplying each app's measured ARPDAU by the trapezoidal integration of its D1/D7/D30 retention curve. Real lifetime LTV is several times higher because (a) revenue continues past D30 on the asymptotic retention tail and (b) ad revenue is not in this dataset. Treat it as the shape of the catalog β a steep right-skew where most apps generate pennies of D30 IAP value per install, and only a thin tail clears a dollar.
LTV is almost always modelled, not observed. True lifetime revenue takes years to materialise; UA decisions need to happen this week. The three dominant modelling approaches:
- Retention-curve extrapolation: fit a curve (typically a power-law decay) to your first 30-60 days of cohort revenue and project it out 12-24 months.
- ARPU Γ tenure: estimate average paying-user ARPU and multiply by an expected tenure (months of active use). Simple, useful for early-stage modelling.
- Parametric churn models (Pareto-NBD, BG-NBD): probabilistic models that estimate the probability a user is still active given their purchase frequency. Standard in subscription businesses.
Subscription LTV has a closed-form approximation: LTV β ARPPU_monthly Γ· monthly_churn_rate. A $10 / month subscription at 10% monthly churn implies an LTV of roughly $100 per paying user; at 5% churn, $200; at 20% churn, $50. This is why "reduce churn by 1 percentage point" is one of the highest-ROI moves a subscription app can make β it compounds across every future cohort.
Blended LTV hides everything that matters. A single LTV number averaged across the whole user base typically obscures a 4-10Γ spread between cohort types. Users acquired from a Tier-1 country on rewarded video may have 4Γ the LTV of users acquired from an emerging market on cheap banner inventory β and yet a blended bidding strategy charges them all to the same UA budget. Mature UA programmes segment LTV by acquisition channel Γ country Γ creative cluster, and bid into each segment separately.
Common pitfall: confusing gross revenue LTV with net contribution LTV. Gross LTV is the revenue you collect from a user. Net contribution LTV is what's left after Apple/Google's 30% commission, hosting/serving costs, content licensing, and customer-service overhead. For UA decisions, what matters is whether net contribution exceeds CPI β not gross revenue. A $10 LTV against an $8 CPI looks fine on gross but is unprofitable on net.
LTV maturity ladder for an app: at launch, you have no observed LTV and must rely on industry benchmarks. By month 3, you can fit a basic retention curve and project. By month 12, you have your first observed full-year cohorts to anchor the model. By year 2-3, your LTV model can be highly accurate β but at that point your bigger problem is usually keeping the model fresh against changing acquisition channels and product changes, not initial modelling.
Three LTV modelling approaches compared
| Method | Data required | Accuracy | Best for |
|---|---|---|---|
| Retention-curve extrapolation | 30-60 days cohort revenue | Good once retention plateau is visible | Most consumer subscription apps |
| ARPU Γ tenure | Period ARPU + average tenure estimate | Rough; early-stage estimates only | New apps without enough cohort history |
| Parametric (Pareto-NBD / BG-NBD) | Per-user purchase frequency + recency | Highest for repeat-purchase products | F2P games, transactional apps, B2B SaaS |
Subscription apps have a fourth shortcut: LTV β monthly ARPPU Γ· monthly churn rate. A $10/mo subscription at 10% monthly churn implies LTV β $100. At 5% churn, $200. This is why "reduce churn 1 point" compounds so heavily.
The histogram exposes the LTV power law in action. Roughly 80% of measurable apps generate under $0.10 of D30 IAP LTV per install; perhaps 5% clear $0.25; a handful pass $1. That's why blended LTV reporting is so misleading β the top 5% drives most of the dollar volume while the long tail anchors any unweighted median you compute.
D30 LTV proxy β median and top-decile by category (IAP only, US iOS)
| Category | Median D30 LTV | Top-10% D30 LTV |
|---|---|---|
| Game | $0.03 | $0.19 |
| Social & Communication | $0.01 | $0.13 |
| Education & Knowledge | $0.01 | $0.07 |
| Media & Entertainment | $0.01 | $0.07 |
| Lifestyle & Well-being | $0.01 | $0.05 |
| Productivity & Tools | $0.01 | $0.07 |
Game apps lead category medians (no surprise β IAP is the game-native model), but the top-decile gap is what's interesting. Games' top-10% D30 LTV is roughly 7Γ their median, while Productivity's is only ~5Γ. Inside Games, the high-end tail is where whale-economics show up (gambling-mechanic games, mid-core RPGs, dating-as-game). For non-game apps, the top-decile is mostly subscription-driven β predictable revenue per active user but a smaller multiplier.