Mobile App LTV: How to Calculate Lifetime Value and Use It to Grow

Why LTV matters

LTV tells you how much a user is worth, which sets how much you can afford to spend acquiring one. Without it, paid acquisition is guesswork: you might stop campaigns that are profitable over time, or scale campaigns that lose money on every user. LTV also helps prioritize product work, because features that improve retention or monetization raise LTV directly.

For ASO teams, LTV adds a value lens to keyword and creative decisions. Traffic from different keyword themes or markets can produce users with very different value. Our guide to ASO ROI and cost benchmarks shows how to connect store improvements to revenue.

The simple formula and its limits

The simplest approach is ARPU per month multiplied by average lifetime in months. If users generate $1.50 per month and stay an average of eight months, LTV is about $12. Another version divides monthly ARPU by monthly churn rate: $1.50 divided by 12.5% churn equals $12.

These shortcuts are useful for rough estimates but hide important details. Churn is rarely constant: many users leave early, and the remaining users are more loyal. Revenue also varies by country, platform, and acquisition source. Cohort-based LTV, described next, captures these patterns.

Cohort-based LTV

Group users by install month and track cumulative net revenue per user over time: day 7, day 30, day 90, day 180, and so on. The resulting curves show how value accumulates and when it flattens. Early cohorts give you real data for older ages, which you can use to project newer cohorts.

Projection methods range from simple multipliers, such as day 180 LTV equals day 30 LTV times a historical ratio, to statistical models. Start simple, validate projections against actual results as cohorts age, and adjust. Our guide to cohort analysis covers the setup.

Use net revenue, not gross

Store fees, taxes, and refunds reduce what you actually keep. Apple and Google typically take 15% or 30% of digital purchases, and both stores deduct sales tax or VAT before calculating proceeds. Our guide to App Store and Google Play fees explains the rates.

Subscription apps should also account for the higher Apple proceeds after a subscriber's first year, trial-to-paid conversion, and refunds. Ad-supported apps should use net ad revenue after network fees. Using gross revenue can overstate LTV by a third or more, leading to overspending.

LTV by monetization model

Subscription LTV depends on trial conversion, price, renewal rates, and plan mix, such as monthly versus annual. In-app purchase LTV depends on payer conversion and spend per payer, often concentrated among a small share of users. Ad LTV depends on sessions, ad impressions, and eCPM, which varies widely by country.

Hybrid apps combine these streams. Model each separately, then sum them, because each responds differently to product changes. A paywall change may raise subscription revenue but reduce ad revenue if fewer users stay on the free tier.

LTV and acquisition cost

Compare LTV with customer acquisition cost (CAC) or cost per install adjusted for activation. Many teams aim for LTV comfortably above CAC, and also look at payback period: how many days until a cohort's revenue covers its acquisition cost. Shorter payback reduces risk and frees cash for growth.

Set acquisition targets by channel and market using LTV for that segment. Users from organic search may be more valuable than users from broad social campaigns, which justifies investing in ASO. Our guide to cost per install explains how to translate LTV into bid targets.

Using LTV in ASO and product decisions

LTV is not only a paid acquisition number. Compare LTV by country to decide where to invest in localization, and by keyword theme or traffic source to see which store audiences are most valuable. A market with fewer installs but higher LTV may deserve localized screenshots before a larger market with low monetization.

Product teams can use LTV to prioritize work. Estimate how a change in trial conversion, renewal rate, or payer conversion would shift LTV, and rank roadmap items by expected value. Pair this with cohort analysis after launch to confirm that changes delivered the expected lift rather than relying on projections alone.

Common LTV mistakes

Using gross revenue instead of net is the most common error. Another is assuming constant churn and projecting far into the future, which inflates LTV. Blending all users together hides big differences between countries, platforms, and sources.

Teams also update LTV rarely, missing changes from pricing, product updates, or shifts in traffic mix. Finally, optimizing only for short-term LTV, such as day 7 revenue, can favor aggressive monetization that damages retention and ratings over time.

A worked example: setting a CPI target

A subscription meditation app tracks cohorts and finds that average net revenue per install reaches $2.10 by day 30, $4.20 by day 180, and about $5.40 by day 365, after store fees and refunds. US users reach $9.80 by day 365; users in other markets average less.

The team sets a target of recovering acquisition cost within 180 days, which implies a maximum cost per install of about $4.20 overall and about $7.50 for US campaigns. It applies these targets to Apple Ads and social campaigns and reviews them quarterly as new cohorts mature.

How to do it, step by step

1. Collect net revenue by userCombine store proceeds, subscription data, and ad revenue, net of fees, taxes, and refunds.
2. Build install cohortsGroup users by install month and track cumulative revenue per user over time.
3. Segment by source and marketCompare LTV curves by country, platform, and acquisition channel.
4. Project and validateProject younger cohorts using older cohort curves, and check projections against actuals.
5. Set acquisition targetsTranslate LTV and payback goals into maximum cost per install by channel and market.

Before and after examples

Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.

Action plan

1. Use net revenue in every LTV model
2. Build cohort-based LTV curves
3. Segment by market, platform, and source
4. Model subscriptions, IAP, and ads separately
5. Set CPI targets from LTV and payback goals
6. Refresh LTV quarterly

Metrics to monitor

• Cumulative net revenue per install by cohort
• Payback period by channel
• LTV to CAC ratio
• Trial-to-paid conversion
• Payer conversion and ARPPU

Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.

Frequently asked questions

Keep reading

Go deeper on this topic

More in Measurement

Browse all 15 Measurement guides

Work with ASOWin