ROAS vs CPI: Which KPI Should You Optimize For?

• CPI (cost per install): spend divided by installs. Measures acquisition efficiency at the top of the funnel. Says nothing about what users do next.
• CPA (cost per action): spend divided by a chosen post-install event — registration, purchase, deposit, subscription. Measures efficiency at a specific funnel step.
• ROAS (return on ad spend): revenue generated by a cohort divided by the spend that acquired it, at a fixed day (D7, D30, D90). Measures value returned.
• LTV (lifetime value): predicted total revenue per user. ROAS at a given day is a partial read of LTV.

If a bidder is told only to minimize CPI, it will find the users who are cheapest to convert into an install. Those are often users with low intent — accidental clickers, incentive seekers, devices that churn. CPI drops, revenue per install drops faster, and the business loses money while the dashboard looks green.

CPI is still a useful diagnostic. It tells you whether creative and store conversion are healthy, and it is the denominator for every other unit cost. It should be monitored, not maximized.

• Pre-launch and soft-launch tests where the goal is to measure creative appeal or market interest.
• Ad-monetized apps with very flat user value, where volume of active users is the business model — though even here, retention matters.
• Very early campaigns before any post-install signal is available, as a short-lived bootstrap.

CPA is the bridge between installs and revenue. Pick an event that is strongly correlated with long-term value and frequent enough for the bidder to learn — typically at least dozens of events per day per campaign. Registration and tutorial completion are common early choices; first purchase or first deposit are better when volume allows.

The risk with CPA is choosing an event that is easy to hit but weakly linked to revenue. Validate the correlation in your own data before committing.

ROAS optimization works when revenue events are reported reliably through your MMP (including ad revenue for hybrid apps), there is enough paying volume for the model, and the business has a clear ROAS target at a defined day.

ROAS depends on the day you read it. D7 ROAS is fast but partial; D30 is more complete but slower. The right target comes from your payback curve: if historically a cohort's D30 revenue is roughly a stable multiple of its D7 revenue, you can set a D7 target that implies the D30 or D90 outcome you need.

Illustrative example: if your data showed that D90 revenue is typically 2.5× D7 revenue, and you need 100% ROAS by D90, then a D7 ROAS target of about 40% would be the implied break-even threshold. The multiplier is hypothetical; calculate yours from your own cohorts.

Most programs move through stages rather than switching overnight:

• Stage 1 — Launch on CPI or a shallow CPA while collecting post-install data.
• Stage 2 — Move to a deeper CPA (purchase, deposit) once event volume supports it.
• Stage 3 — Introduce ROAS bidding for campaigns with enough payers; keep CPA on smaller geos.
• Stage 4 — Use predicted LTV signals to bid on early behavior that forecasts long-term value.

• Judging ROAS campaigns on day-one data — revenue has not arrived yet.
• Excluding ad revenue for hybrid-monetized apps, which understates ROAS.
• Changing targets too often, so the model never finishes learning.
• Comparing ROAS across channels with different attribution windows.
• Ignoring iOS measurement limits — SKAN-based ROAS is estimated, not exact.

Channel-level ROAS is based on attributed revenue, which means it inherits every limitation of attribution: last-touch bias, SKAN estimation on iOS and overlap between channels that reach the same users. Blended ROAS — total revenue from all new users divided by total UA spend — is a useful sanity check at the business level. Incremental ROAS, measured through holdouts or geo tests, tells you what a channel truly added. Mature UA teams track attributed ROAS for daily decisions and check blended and incremental views monthly or quarterly to make sure the attributed numbers are telling the truth.

It helps to see how CPI, CPA and ROAS relate in one cohort. The following figures are an illustrative example only — hypothetical numbers chosen to make the arithmetic clear, not benchmarks.

Imagine a campaign spends $10,000 and acquires 4,000 installs, a CPI of $2.50. Of those installs, 400 make a first purchase in the first week, a CPA of $25.00 per payer. Those payers, plus ad revenue from non-payers, generate $3,000 of revenue by day seven: a D7 ROAS of 30%. By day thirty, cumulative revenue reaches $6,500, a D30 ROAS of 65%.

Now compare a second hypothetical campaign with a CPI of $3.50. It acquires fewer installs for the same spend, but a higher share purchase and D30 ROAS reaches 80%. On CPI the first campaign wins; on the KPI the business cares about, the second one does. This is the core reason to move optimization toward value as soon as your data allows.

Subscription apps complicate ROAS because revenue arrives in renewals. A trial started on day one may convert to paid on day seven and renew monthly afterward. Early ROAS therefore understates value, sometimes dramatically. Many subscription teams optimize toward trial starts or first paid conversions, then use historical renewal curves to project LTV and set an implied early target, the same way games use payback curves.

Refunds and cancellations matter too. Make sure the revenue events you send through your MMP are net of refunds, or at least that refunds are tracked, otherwise ROAS-based bidding can learn to favor sources that produce short-lived subscribers.

KPI choice is not only a UA decision. Finance cares about payback period and cash flow; product cares about retention and engagement; UA cares about scale and efficiency. Agreeing on one north-star target — for example, a D30 ROAS threshold derived from a 180-day payback goal — avoids teams pulling in different directions. Review the target quarterly as monetization and retention change, and document the assumptions behind it so new team members understand why it was set.

Small cohorts are noisy. A campaign with a handful of payers can swing from excellent to poor ROAS on one purchase. Before scaling or cutting, check that the cohort is large enough for the result to be meaningful, look at the trend over several cohorts rather than one, and compare against a control or baseline where possible. Disciplined reading of data is often worth more than a more sophisticated model.

Adora X supports CPI, CPA and ROAS-oriented buying in the same platform. We start with the deepest KPI your data can support, report all three side by side by source and creative, and move campaigns to value-based bidding as cohorts mature.