How Do Free Apps Actually Make Money? The Business Model Behind Ad-Supported Apps

Free apps make money mainly by selling ad space to advertisers, paid per thousand impressions (CPM), not by charging users. Revenue scales with three levers: active user volume, tracking opt-in rates, and ad format. This is the business model behind a free app, not apps that pay you to use them.

How Do Free Apps Actually Make Money With Ads?

An ad-supported app earns revenue every time it shows an ad, not every time someone downloads it. The rate an advertiser pays for that slot, the CPM, is set by an ad network like Google AdMob based on how well the ad can be targeted.

Advertising is one of three real paths to revenue for a free app, alongside in-app purchases and a freemium upsell tier. It asks nothing of the user, fitting products built for mass, zero-friction adoption. Global in-app advertising spend was projected to reach $390 billion by 2025, according to Publift's 2026 in-app advertising statistics report, citing Statista, but that money is spread across billions of impressions, not a handful of downloads. Revenue per user is small, usually cents per thousand impressions, and only becomes meaningful at volume, driven by retention rather than downloads.

The Real Trade-off Most Guides Skip: Privacy Permission Decides Your Revenue

The single biggest lever on ad revenue for an iOS app is not the ad network you pick, it is how many users tap Allow on Apple's App Tracking Transparency prompt. That permission lets an ad network target the ad instead of guessing, and a targeted ad pays a higher CPM. Most monetisation guides list ad formats and stop there, without touching the permission dialogue that decides what those formats are worth.

The opt-in rate is lower than most founders assume. Games have the highest ATT opt-in rate of any app category, topping out at 39%, while less than half of iOS users opt in overall, according to Business of Apps' 2026 ATT opt-in rate data. Plan a revenue model around that ceiling, not a best case.

On a meditation and wellness app we built as embedded CTO, we treated that dialogue as a design problem, not a legal formality. Before Apple's prompt appears, the app shows a plain-language screen explaining why allowing tracking makes the free version better, more relevant ads instead of random ones. That "soft ask," sequenced ahead of the system prompt, lifted the share of users we could target rather than serve blind, one of the levers that got the app to a sustainable ad-revenue break-even. It did not remove Apple's prompt or bypass consent, it gave users a real reason to say yes first, the same logic behind skipping a mandatory sign-up screen at first launch: every extra barrier before a product proves its value costs you revenue.

What to Actually Decide Before You Build an Ad-Supported App

An ad-supported model fits products built for high download volume and frequent, repeatable use, not every free app idea. A mass-market, everyday-use product where a paywall would strangle its own growth is usually a good fit. A low-volume, high-value or B2B product earns more from a handful of paying users, so a subscription fits better there. Work out which camp your idea is in before you commit to a build, the kind of decision we settle early in an MVP development engagement.

Ad format matters as much as ad network. A low-interaction, long-session product like a meditation app cannot run full-screen interstitials without breaking the calm experience it sells, so we used AdMob's Anchored Adaptive Banners, persistent but non-intrusive, instead. Product quality is not separate from ad revenue either: a session that stalls is lost ad-impression time as much as it is a bad experience, the same reasoning behind keeping the screen awake during an active session. Measure the result with Google Analytics 4, tying session length to ad performance to see whether the model works commercially.

An ad-supported app is a real way to build a free product without a paywall, but it only pays off at volume, with a deliberate answer to the tracking-permission question and a format chosen for the product, not borrowed from a template. If your idea needs a handful of high-value customers, this is the wrong model, however well it is built. Get those two decisions right early and the revenue follows the engineering instead of fighting it.

Questions About Ad-Supported App Monetisation

How do free apps actually make money if users never pay anything?

They sell ad impressions to advertisers through a network like Google AdMob, earning a CPM rather than charging the user. Revenue depends on active user volume and session frequency, not on any single user paying. No subscription or purchase step is required.

What is a "soft ask" before Apple's App Tracking Transparency prompt?

A custom screen shown before Apple's own ATT dialogue, explaining plainly why allowing tracking benefits the user. On a wellness app we built, this screen preceded the system prompt and was engineered specifically to lift the opt-in rate, which directly raises what advertisers pay.

Why does ATT opt-in actually affect ad revenue?

Opting in lets an ad network target the ad instead of guessing, and a targeted ad pays a higher CPM than an untargeted one. A higher opt-in rate means more impressions sell at that better rate, which is what moves total revenue.

What's a realistic ATT opt-in rate to plan around in 2026?

Plan around less than half. Games have the highest opt-in rate of any category and still only reach 39%, while less than half of iOS users opt in overall, according to Business of Apps' 2026 data. Build a revenue model on that ceiling, not a best case.

Is an ad-supported model better than a subscription for a new app?

Not universally. It suits mass-market, frequent-use products where a paywall would block needed growth, since the model depends on high download volume and repeatable use. A low-volume, high-value or B2B product usually earns more from a handful of paying customers, so a subscription or one-time purchase fits that case better instead.

What ad format suits a low-interaction app like a meditation or wellness app?

A persistent, non-intrusive banner, not a full-screen interstitial that forces a pause in the experience. On a meditation app we built, we used Google AdMob's Anchored Adaptive Banners because an interruptive format would have broken the calm, long-session experience the product exists to sell, and a broken session is lost ad time too.

How do you measure whether an ad-supported app is actually working commercially?

Tie session length and engagement data directly to ad performance using Google Analytics 4, not just install counts. Break-even is a function of how often people return and how long they stay, so measurement has to track behaviour over time.

Does the app's product quality actually affect ad revenue?

Yes. A session that stalls or gets interrupted is lost ad-impression time as much as it is a poor experience. On a meditation app we built, stopping the screen from dimming mid-session and preloading audio for a gapless loop protected that ad-revenue time directly.