Jun 21, 2026 · 5 min read · GameMantra Team

Ads vs IAP ratio: your genre sets it, not a benchmark

The right ads-to-IAP revenue mix is decided by your genre, not an industry average. Here is why a borrowed ratio quietly misleads.

Someone in a board meeting will eventually ask what the right split between ad revenue and in-app purchase revenue should be. The answer they want is a single number — 70/30, 80/20, something they can hold the team to. That number does not exist, and chasing one borrowed from another company is how studios end up optimising toward a mix their game was never built to support.

The honest answer is that the right ratio is set by your genre, your game's design, and the players it attracts. A puzzle game and a strategy game can both be healthy, profitable, well-run businesses with completely different revenue mixes — and if either tried to match the other's ratio, it would lose money.

The ratios that actually appear in the market

It helps to see how wide the spread is. Across 2026 reporting, hybrid casual action and strategy titles run roughly 82% of revenue from in-app purchases and 18% from ads. Puzzle and lifestyle hybrid casual games sit closer to 50/50. That is not a small difference. One genre earns four-fifths of its money from purchases; another earns half from ads. There is no single "correct" number sitting between them — both are correct for their game.

The broader market context makes the spread sharper. In-app purchases accounted for 77% of global mobile game revenue in 2025, so at the industry level IAP dominates. But hybrid casual IAP grew about 37% in 2026 while overall IAP grew only around 4%, which means the fastest-growing part of the market is precisely the part experimenting hardest with the ad-IAP balance. The average is pulled in several directions at once. Aiming at it is aiming at a point that describes no real game.

Why the genre decides

The reason genre dictates the mix is not arbitrary. It comes down to two things: how willing your players are to pay, and how naturally your game creates moments where an ad fits.

A strategy or mid-core game attracts players who invest deeply, return daily, and are willing to spend meaningfully on progression. That player base supports a rich purchase economy, so most of the revenue can and should come from purchases. Filling that game with ads would interrupt exactly the deep, committed sessions that produce the spending — you would be taxing your best customers to capture small ad revenue.

A puzzle or lifestyle game is the opposite. It attracts a much broader, more casual audience, most of whom will never make a purchase. But that audience plays in short, frequent bursts, which creates many natural breakpoints where an ad — especially an opt-in rewarded ad offering an extra move or a continue — feels useful rather than intrusive. For that game, ads are how you monetise the large majority who would otherwise contribute nothing, so a near-even split is healthy.

So the ratio is downstream of player psychology and session shape, both of which the genre largely sets before you write a line of code. You do not pick the ratio. The game picks it, and your job is to read it correctly.

What goes wrong with a borrowed number

When a studio adopts another company's ratio as a target, the failure is predictable. Suppose a casual puzzle team hears that the successful strategy studios run 80/20 IAP-to-ads and decides to push toward that. To get there, they have to pull back ads and lean harder on purchases. But their audience is mostly non-payers — that is the nature of the genre. Pulling back ads removes the only revenue those non-payers ever generated, and pushing harder on purchases does not convert people who were never going to pay. Revenue falls, and the team concludes their monetization is "underperforming" when in fact they were chasing a target that did not apply to them.

The reverse fails too. A mid-core team that hears casual games run 50/50 and adds interstitials to "diversify" ends up interrupting the deep sessions that drive their purchase revenue. The ad income is small and the disruption to spending is not. They diluted their strongest channel to chase a balance their game does not want.

In both cases the borrowed number was not just unhelpful — it actively pointed the team away from the mix their game was built to support.

The question to ask instead

The useful question is not "what is the right ratio." It is "for this specific game, which players should see ads, which should see purchase offers, and which should see both." That reframes the ratio as an outcome rather than a target. You decide how to treat each kind of player, and the overall mix falls out of those decisions. If your game skews toward committed payers, the mix will land IAP-heavy on its own. If it skews toward broad casual play, ads will carry more weight on their own. The number is a result, not a goal.

This also means the ratio is allowed to be different for different players inside the same game. A small group of committed payers might generate almost all their value through purchases, while a large casual majority generates theirs through ads. The blended ratio across the whole game is just an average of those two populations — and managing each population well matters far more than hitting any particular blended figure.

You can read more about routing each player toward the channel that fits them in how it works.

What to tell the board

When the question comes up, the answer that holds is this: we do not target an industry ratio, because the right mix is set by our genre and our players, and copying another company's number would point us at a balance our game cannot support. What we manage instead is whether each player sees the channel that fits them, and we measure whether changes to that actually grew durable revenue rather than just shifting it between buckets. The ratio that results is the right one for this game, even when — especially when — it does not match the benchmark someone read in a report.

Share this post

See what this looks like for your game.

SDK for Unity and Unreal. A 20-minute call to walk you through it.

Book a demo