Diversified monetisation: when each channel earns its place

A few years ago, mobile game monetisation strategy meant deciding between two options: in-app purchases or advertising. Most studios picked one as primary and treated the other as a small supplement. The decision was usually based on genre — strategy and RPG leaned IAP, hyper-casual leaned ads, casual sat somewhere between.

In 2026 that binary is gone. Leading mobile studios run four monetisation channels at the same time: in-app purchases, rewarded advertising, direct-to-consumer web shops, and subscriptions. The competitive question is no longer which one to use. It's which channel each player should see at each moment, and how to keep the four from cannibalising each other.

Most studios that add channels reactively — bolting on rewarded ads when revenue dips, launching a web shop because competitors did — end up with overlapping monetisation that produces less total revenue than a thoughtfully designed mix would. The discipline that produces real lift is deciding which channel earns its place where, and refusing to let any one channel reach into another's territory.

What each channel actually does well

The four channels have genuine comparative advantages, and they're not interchangeable.

In-app purchases capture the high-intent buying moment. A player who hit friction, sees an offer relevant to that friction, and converts in-context is the highest-margin monetisation event in mobile. IAP is the only channel that operates at the speed of the moment — by the time a player has switched apps or opened a browser, the buying intent has decayed.

Rewarded advertising monetises the free base. The players who would never spend on an IAP, who declined every offer in the catalog, still produce value if they're willing to trade attention for a small in-game reward. Rewarded ads are the only channel that monetises this segment in a way that scales.

Web shops capture the deliberate, repeated, and large transactions where the margin difference justifies the friction. A player buying a $49.99 bundle or renewing a subscription benefits the studio more on the web (where the platform fee is bypassed) than in-game, and the player tolerates the friction at that transaction size.

Subscriptions convert the engagement-rich relationship into recurring revenue. A player who plays daily and consumes content faster than they earn it is a strong subscription candidate. The single transaction becomes a series of small ones, with predictability that one-off purchases don't deliver.

What makes a stack work is that each of these channels serves a different combination of player intent, transaction size, and engagement depth. Where they overlap is where the trouble starts.

Where channels cannibalise

The most common cannibalisation pattern is rewarded ads competing with IAP at the same moment. A player who hit a friction point and sees both options — buy the resource for $0.99 or watch a video for it free — will often pick the free path, even when they would have bought without the ad option. The ad revenue is real, but it came at the cost of a purchase that would have produced more total margin.

A second pattern is web shops competing with the in-game store on impulse purchases. A web shop is great for the deliberate $49.99 transaction. It's terrible for the $0.99 in-the-moment purchase, because the friction of switching contexts kills the conversion. Studios that route every offer to the web (in pursuit of margin) lose more in lost conversion than they gain in fee savings.

A third pattern is subscriptions and one-off purchases pricing against each other. A subscription that bundles content a player previously bought as one-offs can reduce their total annual spend if it's priced too aggressively. The subscriber count goes up; the per-player revenue goes down. The net can be lower than the previous arrangement.

The pattern across all three is the same: cannibalisation happens when channels are offered at moments where they substitute for each other rather than complement each other. The fix is positioning, not pricing.

The decision the offer system has to make

The right way to think about a diversified stack is that the offer system has to make a decision at every monetisation moment: which channel is this player most likely to engage with right now, and which channel produces the highest total value if they do?

For a friction moment (out of resource, level fail, missing item), the answer is usually IAP if the player has shown spending behaviour, or rewarded ads if they haven't. The two should not be presented side by side at the same moment — let one channel own each moment.

For a deliberate browsing moment (player opens the store, browses bundles, considers a purchase), the answer depends on transaction size. Small-to-medium purchases stay in-game where the conversion is fast. Larger purchases can route to the web if the player is a known previous buyer with a linked account; otherwise stay in-game to avoid the friction of first-time web shop setup.

For a recurring engagement pattern (player plays daily, consumes content steadily), the answer is the subscription pitch — and that pitch should be presented in a low-friction in-game moment, not in a hard sell. Subscription conversions are easier when the player has already shown the daily behaviour the subscription is sized for.

For the free-base player (no purchase history, declines IAP offers consistently), the answer is rewarded ads, and the rewards should be small enough to keep the IAP path appealing if the player ever does convert.

This is per-player, per-moment routing — not a global rule. A player who behaves like a deliberate buyer one week may be in a different state the next. The signal that drives the routing has to be live, not a one-time segmentation.

Measuring whether the stack is working

The metric that tells you whether a diversified stack is producing real lift isn't total revenue. It's revenue per active player, compared to a baseline.

If you added rewarded ads and revenue per active player went up, the channel added value. If revenue per active player held steady while ad revenue grew, the channel substituted for IAP. If revenue per active player went down, the channel cost more than it earned.

The same comparison applies to each addition. A web shop that increases revenue per spender is additive. A web shop that holds total spend constant while shifting transactions to the web is margin-positive but volume-neutral — useful, but smaller than the gross revenue figure suggests. A web shop that loses impulse purchases without recouping them on the web is net negative.

Tracking by segment matters more than tracking the aggregate. A diversified stack typically helps some segments and hurts others — and the aggregate can mask both. Free-base players almost always benefit from rewarded ads (they had no monetisation before). Paying-base players can be hurt by rewarded ads (they had IAP behaviour the ads now substitute for). Aggregate numbers average these two outcomes; segmented numbers reveal them.

What this means for the catalog

The implication for offer catalog design is that offers need to know what channel they're meant for. An offer designed for the in-game friction moment is a different product than the same items priced for the web shop's deliberate-buyer audience or for a subscription's recurring-value pitch.

A catalog that doesn't distinguish channels ends up with offers that perform well in one channel and badly in another. A catalog that tags each offer with its intended channel can route them appropriately and avoid showing the wrong product in the wrong moment.

The discipline is uncomfortable for studios used to running a single offer list. It's also where the difference between a diversified stack that compounds and one that cannibalises gets decided. Channels don't earn their place by existing. They earn it by being positioned where they produce more total value than they take from the channels around them.

See how we route offers across monetisation channels →

The 2026 mobile market increasingly rewards studios who run a real stack — not because more channels is automatically better, but because each channel serves a player segment or moment that the others can't reach. The studios who design their stack channel by channel, with explicit routing logic between them, capture the lift. The studios who add channels and let them compete for the same player at the same moment usually find that their total revenue doesn't move the way the channel-by-channel numbers suggested it would.

Talk to us about monetisation stack design →