Free tool

Mobile Game LTV & ROAS Calculator

How many days until an install pays for itself, and what CPI can you afford? Enter your CPI, D1, D7 and D30 retention and ARPDAU: the calculator projects the cohort's cumulative LTV, its ROAS, its payback day and the highest CPI it can carry. No email required; nothing you type leaves your browser.

Inputs

The values below are example inputs, not benchmarks. Replace them with your own.

Acquisition and revenue
Retention, % of installs active

Estimates

Payback day
–
Break-even CPI
–
Estimated ROAS (cumulative net revenue divided by CPI)
DayLTVROAS
Cumulative LTV per install against CPI
Cumulative LTV CPI Payback day

All figures are estimates from a simplified model, rounded to two decimals. Read the limits below before using them in a budget decision.

How the model works

The calculator turns three retention points into a full retention curve, then adds up the revenue each install earns day after day.

  • Retention curve. Every install counts as active on day 0. From day 1, retention follows a power curve, r(d) = a × d−b, drawn through your D1, D7 and D30 values by a least-squares fit on a log-log scale. When the three points do not sit exactly on one curve, the fitted curve passes between them.
  • Net revenue. Net ARPDAU is your ARPDAU multiplied by the share of revenue you keep after platform fees.
  • LTV. The LTV on day N is net ARPDAU multiplied by the sum of retention from day 0 to day N: the revenue an average install has brought in by then.
  • ROAS. ROAS on day N is that LTV divided by your CPI. A ROAS of 1.00 means the install has paid for itself.
  • Payback day. The first day on which LTV reaches the CPI. When it never does within the horizon, the calculator says so.
  • Break-even CPI. The LTV at the horizon: the highest CPI the cohort can carry and still pay back by the end of the horizon.

What the model assumes and leaves out

This is a simplified projection, useful to compare scenarios and to check whether a CPI is in a plausible range. It is not a forecast of your game's revenue.

  • Constant ARPDAU. An active player is assumed to spend the same on day 300 as on day 3. In most games, spending per active user changes with tenure.
  • One blended cohort. All installs are treated as one group. Countries, channels, platforms and campaigns with different retention and revenue are averaged together.
  • No organic uplift. Installs brought in indirectly by paid campaigns are not credited to the CPI.
  • No split between ad revenue and in-app purchases. ARPDAU is one figure, and the revenue share applies to all of it, although ad revenue and purchases are often shared differently.
  • Retention beyond D30 is extrapolated. After day 30 the curve is an extension of the fit, not data. The longer the horizon, the less reliable the estimate.

How to read the outputs

  • Payback day tells you how long your cash stays tied up in each install. Compare it with how long you can fund acquisition before revenue comes back.
  • ROAS at D7 and D30 are the checkpoints most UA dashboards report. Compare the estimate with the cohort ROAS you actually observe: a large gap points to an input or an assumption that does not hold for your game.
  • Break-even CPI is a ceiling, not a target. Buying at that price leaves no margin, and the further the horizon reaches beyond D30, the more it rests on extrapolated retention.
  • Change one input at a time to see which lever moves payback the most: a retention gain, a monetization gain or a cheaper install.

Related reading

Want a second look at your UA economics?

Browse the free guides for checklists and frameworks, or book a call to review your cohort data, CPI and payback before you commit more budget.