User Acquisition

Lifetime Value (LTV)

Also known asLTVLifetime ValueCLVCustomer Lifetime ValueLTV mobile

The total revenue (or gross profit) you expect a single user to generate over their entire relationship with the app β€” the denominator of every UA decision.

pillar

MWM data

State of April 2026

Median D30 IAP LTV

$0.01

Per-install IAP revenue earned in first 30 days for the median measurable app

Top-25% D30 LTV

$0.04

Solid monetization Γ— retention combination β€” well-tuned freemium

Top-10% D30 LTV

$0.10

Strong tier β€” subscription productivity, mid-core games

Median active days in D30

4.08

Cumulative engagement-days per install over 30 days (median app)

Key takeaways

  1. 01LTV / CPI is the central UA ratio: if LTV is $30 and blended CPI $8, you can buy almost any user; if LTV is $4 and CPI $8, you are burning cash on every install.
  2. 02LTV is always modelled, never observed β€” true lifetime revenue takes years to materialise, but UA decisions need to happen this week.
  3. 03Three common LTV models: retention-curve extrapolation, ARPU Γ— expected tenure, and parametric (Pareto-NBD / BG-NBD) for subscriptions.
  4. 04Blended LTV hides 4-10Γ— spread between cohorts: Tier-1 country + rewarded-video users vs Tier-3 + cheap-banner users diverge dramatically.
  5. 05Subscription LTV β‰ˆ monthly ARPPU Γ· monthly churn rate. A $10/mo subscription at 10% churn implies LTV β‰ˆ $100; at 5% churn, $200.

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:

  1. 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.
  2. ARPU Γ— tenure: estimate average paying-user ARPU and multiply by an expected tenure (months of active use). Simple, useful for early-stage modelling.
  3. 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

MethodData requiredAccuracyBest for
Retention-curve extrapolation30-60 days cohort revenueGood once retention plateau is visibleMost consumer subscription apps
ARPU Γ— tenurePeriod ARPU + average tenure estimateRough; early-stage estimates onlyNew apps without enough cohort history
Parametric (Pareto-NBD / BG-NBD)Per-user purchase frequency + recencyHighest for repeat-purchase productsF2P 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.

D30 IAP LTV proxy distribution across the catalogPer-install IAP revenue earned in the first 30 days, derived from each app's retention curve Γ— ARPDAU. The distribution is heavily right-skewed β€” most measurable apps generate under $0.10 of IAP LTV per install by D30; the thin tail above $1 captures gambling, dating, and high-spend gaming apps.0125250375500<$0.01: 440$0.01-0.05: 445$0.05-0.10: 126$0.10-0.25: 84$0.25-0.50: 15$0.50-1.00: 13$1-3: 3Strong-tier threshold<$0.01$0.01-0.05$0.05-0.10$0.10-0.25$0.25-0.50$0.50-1.00$1-3D30 IAP LTV per install
D30 IAP LTV proxy distribution across the catalog β€” US iOS apps with β‰₯500 d30 downloads + β‰₯$50 daily IAP revenue + measured Q3 2025 retention. D30 LTV = ARPDAU Γ— trapezoidal-integrated retention curve. IAP only β€” ad revenue NOT included; true lifetime LTV is several Γ— higher than D30., State of April 2026.

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)

CategoryMedian D30 LTVTop-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.

Quick answers

What is a good LTV for a mobile app?

It depends entirely on your CPI. The rule of thumb is LTV Γ· CPI β‰₯ 3 for a sustainable business; β‰₯ 2 if you have other revenue streams or strategic reasons to acquire below payback. For subscription apps, target LTV β‰₯ $50 in Tier-1 markets and β‰₯ $20 in emerging markets. For free-to-play games, the whales-driven distribution means median LTV is misleading β€” track LTV by cohort decile, and ensure the top 10% covers UA spend on the bottom 90%.

How do you calculate LTV?

Three common approaches. (1) Retention-curve fit: project lifetime revenue from your first 30-60 days of cohort data by fitting a decay curve. (2) ARPU Γ— tenure: simple early-stage estimate (e.g., $1 weekly ARPU Γ— 12 weeks = $12 LTV). (3) Subscription closed-form: LTV β‰ˆ monthly ARPPU Γ· monthly churn rate. Sophisticated teams use parametric models (Pareto-NBD, BG-NBD) that fit purchase frequency distributions across the user base.

What is the difference between LTV and ARPU?

ARPU is per-period revenue per user (e.g., monthly revenue Γ· monthly actives). LTV is **cumulative** revenue per user across their entire relationship with the app. LTV = ARPU Γ— expected tenure (in periods). A $5 monthly ARPU with a 12-month expected tenure = $60 LTV. ARPU is observed (you measure it directly); LTV is modelled (you project it).

How does LTV relate to CPI?

LTV is the ceiling on what you can sustainably pay for a user. The LTV / CPI ratio is the central UA economics metric: at LTV / CPI = 3, you triple your money on every paid install (gross); at 2, you double it; at 1, you break even (which is usually a loss after Apple/Google commission and overhead). Healthy paid UA targets LTV / CPI β‰₯ 3 over the relevant payback horizon (often 6-12 months).

Why is LTV always modelled instead of observed?

Because true lifetime revenue takes years to materialise β€” a subscription user acquired today might still be active 3 years from now. UA decisions need to happen this week, so you need a forecast based on early-cohort signal. Even mature apps use modelled LTV for current bidding decisions, then back-test against observed cohort behaviour over time to calibrate the model.

What is predicted LTV (pLTV)?

pLTV is a class of machine-learning LTV models that score individual users (or small cohorts) within their first hours or days of activity based on early-funnel events β€” onboarding completion, first session length, key engagement actions. Major ad networks (Meta, TikTok) now consume pLTV signals to bid into high-pLTV users specifically. Building a usable pLTV model usually requires 3-6 months of historical cohort data plus a feature pipeline to score users in near-real-time.

Back to glossary