App campaign costs: installs and payers

A low cost per install can hide an expensive paying customer. To budget an app campaign, estimate three things: what you spend to acquire installs, how many of those users complete a valuable action, and the production, measurement and management costs around the campaign.

There is no single 2026 CPI that makes a campaign good. A useful comparison needs the same app category, operating system, market, acquisition period and attribution rules. The example below shows how to build a budget when you have those inputs, including what changes when the payer rate disappoints.

First separate the metric, the goal and the bill

Cost per install (CPI) is media spend divided by attributed installs. Cost per action (CPA) is spend divided by the number of defined actions, such as completed registrations or first purchases. These calculations do not tell you what triggers the platform’s invoice.

For example, 100 purchases from 20 new payers produce two different denominators. A campaign optimized for purchases does not automatically acquire 100 customers. A trial start is also different from a paid subscription after the trial ends.

Platform rules checked on October 9, 2026 illustrate the distinction:

• Google App campaigns offer goals and bidding options for installs, in-app actions and value. A target CPI or CPA expresses a desired average outcome cost. It is not a promise that every outcome will cost that amount or a general agreement to bill only for that outcome.
• Apple Ads Basic does charge for installs. Advanced charges per tap. Advanced search results campaigns can use manual Manage Bids or automated Maximize Conversions; automation does not change Advanced into pay-per-install billing.

For any other network, check the chosen campaign’s billing event, optimization event and reporting definition separately. Comparing a cost-per-thousand-impressions (CPM) quote with someone else’s CPI without an impression-to-install rate does not establish which is cheaper.

A worked budget: US$2 installs versus US$5 installs

This is a hypothetical comparison, not client results or a market forecast. Both campaigns promote the same subscription app to new users on the same operating system in the same country. Each spends US$10,000 during July 1–31, 2026 (UTC). Count installs attributed to clicks in that period within seven days of the click, with no view-through attribution. Count each new payer once, within 30 days of their attributed install. The example is read on October 9, after those windows have elapsed.

Campaign B has the higher CPI and the lower cost per payer. The US$2,000 allowance is an invented total for this exercise. It is neither an agency quote nor an industry norm. Allocate shared costs consistently and avoid counting the same invoice twice.

Now suppose B converts only 2% of installs into payers. Its 2,000 installs yield 40 new payers, so media cost per payer rises to US$250 and total acquisition cost reaches US$300. That downside matters more to the budget than a small change in installation price.

Profitability needs another input: contribution from those users after store fees, refunds and variable servicing costs. If the business expects US$180 contribution per payer by day 90 and reserves US$40 for overhead and profit, its chosen acquisition ceiling is US$140. B’s US$120 fits that assumption; the US$300 downside does not. Day-90 contribution is still a forecast for this July click cohort on October 9, so this is not proof of realized payback or incremental profit.

Work backward from a meaningful test

Using B’s base assumptions, a planning goal of 100 new payers requires 2,000 installs at a 5% payer rate. At US$5 CPI, that means US$10,000 media plus the separately scoped work. At a 2% payer rate, the same goal needs 5,000 installs and US$25,000 media, with operating costs estimated again for that scope.

The choice of 100 payers here is arithmetic. It is neither a platform eligibility threshold nor proof of statistical certainty. Set a test goal around the decision you need to make and the uncertainty you can afford. A small budget may support a narrow feasibility test while leaving payer economics unresolved.

Before agreeing the test, record:

1. The app, OS, countries, currency, acquisition dates, and whether the audience is new or returning.
2. The install attribution window, treatment of views, and time allowed for the post-install event.
3. The event definition, duplicate handling, refund treatment and measurement source.
4. The media allowance, production scope, measurement charges and management work.
5. The review date and what evidence would justify another test or a proposed budget change.

Our guide to testing emerging channels develops that decision process. A proposed budget still needs the owner’s approval before anyone changes live spend.

Choose an event that is measurable and useful

Google’s App bidding guidance requires conversion tracking for the in-app actions you want to optimize. Check the current requirements for the particular platform and campaign type. There is no universal rule that every app campaign becomes reliable after 50 conversions a week.

If purchases are sparse, a more frequent event may be worth testing. First check whether users who complete it later become payers. Cheap registrations with little paid conversion can make an event campaign look successful while acquisition economics deteriorate. Keep the eventual payer or contribution measure in the evaluation, even when the bidding system uses an earlier event.

Retargeting needs its own returning-user cohort and costs. Combining it with new-user acquisition can hide how much you paid to reactivate existing customers. Push messages and onboarding improvements also need their own tests; neither guarantees a lower acquisition cost.

Include the work around the media

Scope creative by deliverables: concepts, video versions, languages, revisions and usage rights. Creator fees and the right to run the work as an ad are separate questions. Scope app store work by the listings, screenshots, markets and experiments required. App store optimization (ASO) can test discoverability and store conversion, but it cannot guarantee rankings or profitable installs.

Measurement also needs a separate allowance. AppsFlyer’s current pricing distinguishes its free Zero offering from Growth for paid acquisition measurement. Its billing guide describes a welcome allowance of 12,000 measured conversions or one year, whichever comes first, and additional charges according to plan units and features. Do not assume all installs, purchases and invoice units are interchangeable. Confirm the payable plan, currency, add-ons and usage definition before estimating the bill.

A mobile measurement partner can help reconcile sources, but it cannot remove privacy limits. Apple’s AdAttributionKit limits postback detail according to privacy thresholds, and reports arrive with delays. Keep platform-reported, independently attributed and modeled results labeled. Where a common comparison is unavailable, describe the gap instead of treating missing information as zero.

For delivery support, compare the stated scope of mobile app marketing and paid advertising management. Ask what includes creative, store work, event implementation, reporting and ongoing changes, and identify additional charges. Compare that total against your own expected contribution and cash recovery period.

What counts as a good app acquisition cost?

A good CPI supports an affordable cost per valuable user after the full acquisition bill. Use a mature, comparable cohort to estimate it, show a weaker conversion scenario, and keep future revenue assumptions visible. A network-wide price range cannot answer those questions for your app.