Whats the Typical Customer Acquisition Cost for Apps

Customer acquisition cost is one of those numbers that looks straightforward until you try to act on it. A benchmark tells you what other apps are spending per install. It does not tell you why your cost is higher, whether that cost is sustainable, or what is actually driving it. And in most cases, the figure teams are watching is the attributed cost, which is a different thing from the real cost entirely.

The real acquisition cost only reveals itself once you account for how many users actually stay.

The gap between what you pay to acquire a user and what that user is actually worth depends almost entirely on what happens after the download. Onboarding, core experience, retention mechanics, these are not product concerns that sit separately from acquisition budgets. They are the variables that determine whether every pound you spend on paid install campaigns is working or being quietly wasted.

We spend a lot of time with teams who are trying to bring acquisition costs down by adjusting their paid media. That sometimes works. More often, the problem sits upstream in the product itself, and no amount of creative testing or bid optimisation touches it. This article walks through how to read CAC benchmarks properly, where the hidden costs accumulate, and what a realistic target looks like once churn is factored in.

What Are the Actual CAC Benchmarks for Apps?

Published benchmarks for cost per install vary enormously depending on the source, the category, the platform, and whether the figure represents attributed or incrementality-adjusted spend. That distinction matters more than engineers typically realise. INCRMNTAL's analysis of 11 app developers across iOS and Android found that the average attributed cost per install on Android was $1.49 against $7.35 on iOS, a difference that looks dramatic but is largely a measurement artefact caused by iOS 14.5 attribution limitations rather than a true reflection of what iOS users cost to acquire. When the same developers were measured using incrementality-adjusted CPIs, iOS was only 19% more expensive than Android, not four times more expensive.

That single finding should make any team cautious about benchmarks drawn from attributed data, which is most of the published research. The figures below are a rough orientation, not targets.

These ranges shift based on geography, seasonality, and how competitive the paid channels are at any given moment. What they do not capture is the effective cost per retained user, which is the number that actually matters when you are trying to run a sustainable product.

Why the Same Benchmark Means Different Things Across Categories

A $5 cost per install in a casual gaming app and a $5 cost per install in a subscription fitness app are not equivalent. In gaming, a user who plays once and churns still completes the minimum viable interaction, they saw the product. In a subscription fitness app, a user who installs and does not complete onboarding has cost you $5 and generated nothing. The benchmark number is the same. The outcome could not be more different.

Category determines the relationship between acquisition cost and lifetime value. An app that generates £40 per year from a retained subscriber can absorb a £12 CPI if it keeps users for three or more years. An app that relies on ad revenue from daily active users cannot absorb the same cost unless it also retains those users daily. This is why looking at a competitor's CPI in isolation tells you almost nothing useful, you do not know their retention rate, their monetisation model, or whether they are profitable at that spend level.

App Store category also shapes organic acquisition, which reduces the effective CPI on paid spend. We advise clients to think about category selection in two stages when a product could plausibly sit in more than one. Launching in a less competitive category generates more organic impressions and downloads from a standing start, builds usage and awareness, and creates a foundation before moving into the primary, more competitive category later. A lower organic share means every user costs more on average, which inflates the apparent CPI even when paid media is performing well.

How App Store Listings Affect Who Downloads, and What That Costs You

An install from a user who does not understand what your app does is a delayed churn event. The person will open it, feel confused or disappointed, and leave within a few days. You have paid for the install and received nothing in return. This is one of the most consistent patterns we see, and it is almost always traced back to an App Store listing that prioritises visual polish over clear communication.

We worked on a gifting and wishlist platform where the client was reluctant to invest time in App Store Optimisation, believing that word-of-mouth referral from the social, group-oriented nature of the product would do the work instead. Our position was that ASO matters regardless of referral mechanics. The icon, copy, category, and screenshots all need to be immediately clear so that users can self-select in or out before downloading. The goal is to make sure that the people who do download are already pre-sold on what they are getting, which brings abandonment rates down considerably.

When a listing accurately communicates what an app does, users arrive with correct expectations. They are not discovering what the product is during onboarding, they already know. That alignment between expectation and experience is one of the cheapest ways to reduce early churn, and it costs nothing in paid media.

An install from a user who misunderstood the listing is money spent on someone who was never going to stay.

This is also where category selection intersects with listing quality. A product placed in a less competitive category but with a listing that does not match that category's user expectations creates a mismatch that paid media cannot fix. Both decisions, category and listing, need to work together to attract users who are genuinely likely to stay.

Write your App Store description as though explaining the product to someone who has never heard of it. If it relies on category familiarity or assumes prior context, it will not self-select the right audience.

Onboarding Is Where Most Paid Installs Go to Die

By the end of day one, according to Business of Apps, 25% of users have already left an app for good. That figure is an average across all apps and all categories, which means for products with weak onboarding it is considerably worse. Every one of those day-one exits represents a paid or organic install that generated nothing, no activation, no revenue, no data about whether the product even worked.

Onboarding problems cluster around a handful of consistent causes. Forced registration before the user has seen any value is one of the most reliable ways to lose 15 to 20 percent of users before they have experienced the product at all. Excessive permission requests without clear explanation, too many tutorial screens, and slow loading in the first three to four seconds all compound the problem. Users abandon quickly and they abandon silently, there is no complaint, no cancellation reason, just a session that ends and never restarts.

We worked with a fitness social network where the onboarding flow asked users to share their location before they had built any rapport with another user. The conversion rate from sign-up to users successfully meeting another person was around 20%. After redesigning the flow to use approximate proximity rather than precise location, and sequencing conversation before location disclosure, that conversion rate rose to around 60 to 70 percent. One behavioural change in the onboarding sequence, the same paid acquisition budget, produced roughly three times the outcomes.

Test your onboarding with someone who has never seen the product before. If they hesitate at any permission request or registration screen, that hesitation is a drop-off you are currently paying for.

When Core Experience Problems Masquerade as an Acquisition Problem

Teams often respond to rising CAC by adjusting their acquisition strategy, testing new creatives, moving budget between channels, or trying a different paid platform. Sometimes that is the right call. But a consistent pattern is that the actual problem sits in the product, and acquisition changes do not touch it.

We worked on an art-based auction game with real money prizes. Early retention sat in the mid-sixties to low seventies percentage range, which is strong. As the quantity of available games declined over time, usage became sporadic rather than ongoing, and retention dropped to around 30 to 35 percent. The team raised this concern, but the client's response was to add new features rather than address the core content supply problem. New features bring new acquisition costs and new onboarding complexity. They do not fix the underlying reason users are leaving.

It was only when retention hit that low point that the focus shifted back to ensuring enough games were available, the core user journey, which eventually restored retention to the mid-sixties to low seventies. But rebuilding that trust took time. Every pound spent on acquisition during the period when retention was poor was effectively subsidising churn rather than growth.

The question to ask before adjusting any acquisition budget is whether users who reach the core experience are staying. If they are not, the acquisition strategy is not the problem.

How UX Decisions Create Hidden Costs That Inflate CAC

Not all acquisition costs appear in the media spend report. Some of them show up as rework budgets, delayed launches, and product sections that have to be rebuilt from scratch because a decision made early in the project created a contradiction further down the line.

On a dating app project focused on verified profiles and preventing bots, the client chose to skip discovery for the messaging component and focus the budget on onboarding instead. The reasoning was that messaging is standard functionality and does not need the same level of research. What was built was a generic messaging feature that allowed automated and fake messages, which directly contradicted the verification work done during onboarding. The mismatch between the rigorously verified entry flow and the permissive messaging system meant the entire messaging section had to be rewritten. That decision cost approximately £15,000 in additional budget and two months of extra work.

UX decisions that skip discovery in one area to save time reliably create downstream costs that exceed whatever was saved. That £15,000 did not appear in an acquisition report, but it reduced the budget available for paid media, delayed the product launch, and meant the verified onboarding users experienced a messaging system that undermined the product's core promise.

Clarity around costs within the product creates the same kind of hidden drag. During a marketplace checkout project, we observed that confusion around platform fees, specifically whether a fee was added on top of a displayed price or already included, caused measurable hesitation and drop-off even when the amounts involved were small. The financial magnitude of the fee was not the issue. The ambiguity around it was. Users who did not understand the fee structure did not feel comfortable proceeding, and that hesitation inflates effective acquisition cost by reducing the conversion rate on every paid install.

Retention Rate Is the Multiplier on Every Pound You Spend Acquiring Users

On average, 77 percent of apps lose their daily active users within the first three days. Even well-built products typically see a 40 to 50 percent retention drop over the same period. The gap between those two figures, 77 percent versus 40 to 50 percent, is where good product decisions are worth real money. A team spending £10,000 a month on user acquisition and retaining 45 percent at day three is getting more than twice the active users from the same budget as one retaining 23 percent.

Retention shapes effective CAC more directly than any channel optimisation. A day-one retention rate below 50 percent is a warning sign regardless of how good the acquisition numbers look. Download counts rising while day-three, day-five, and day-seven retention quietly declines is a pattern that produces a false sense of product health. The growth looks real in the dashboard. The retained user base tells a different story.

We tracked this closely on a water tracking app we developed. The top ten personal finance apps lose approximately 71 percent of daily active users between day one and day thirty, a figure that reflects how common the problem is even in established, well-funded products. We saw a similar pattern on the water app, and part of the issue was interpreting user silence as satisfaction. Users who stopped using the app did not complain. They simply stopped. In mobile apps, no news is not good news.

According to research attributed to Bain and Company, increasing an app's retention rate by just 5 percent can drive up profits by as much as 95 percent. The compounding effect of retention on acquisition economics is why retention rate is the most important variable in any CAC calculation.

What a Realistic CAC Target Looks Like Once You Account for Churn

A realistic CAC target is derived from your own retention numbers and the lifetime value those retention numbers produce. The calculation is straightforward in principle, though teams often avoid it because the outputs are uncomfortable.

1. Start with your day-one retention rate and track it through to day thirty.
2. Estimate the average revenue per retained user over twelve months.
3. Multiply that by your retention rate at thirty days to get effective LTV per install.
4. Set your CAC target at a fraction of that figure, accounting for the margin the business needs.

If day-thirty retention is 25 percent and average annual revenue per active user is £40, the effective LTV per install is £10. A £12 CPI is already above that. No amount of creative optimisation fixes the underlying mismatch, the product needs to retain more users before acquisition spend scales.

Where a product can genuinely push day-thirty retention above 50 percent, the economics shift substantially. AppsFlyer's mobile onboarding studies found that users who experience friction in their first session are 2.7 times less likely to return by day seven. Removing that friction, through clearer onboarding, better expectation-setting in the App Store listing, and a core experience that delivers immediate value, compounds across every cohort of paid users. The acquisition budget does not change. The number of users it produces does.

Calculate your effective cost per retained user at day thirty, not just cost per install. If that number exceeds what a retained user is worth in twelve months, the acquisition budget is outpacing the product's ability to make use of it.

Conclusion

CAC benchmarks are useful as a rough orientation, but they are not a target and they are not a diagnostic. A $5 cost per install in a product with 25 percent day-thirty retention is a problem. The same cost in a product with 60 percent retention is a different business entirely. The number that matters is effective cost per retained user, and that number lives downstream of the acquisition channel, in the App Store listing, the onboarding flow, the core experience, and the mechanics that bring people back.

The patterns are consistent. Skipping discovery creates rework costs that compound. Listing copy that attracts the wrong users inflates churn before it can be measured. Onboarding that asks too much too early loses users who were genuinely interested. And core experience problems that go unaddressed, like the auction game that ran out of games to play, absorb acquisition spend without producing retained users.

None of these are acquisition problems in the conventional sense. They are product and UX problems that show up in acquisition economics. The teams who bring their effective CAC down are usually the ones who stopped trying to fix it through paid media and started looking at what happens after the install.

If you want to work through what your retention numbers mean for your acquisition strategy, let's talk about your app's retention and CAC.

Frequently Asked Questions