Jul 27, 2026 · 4 min read · GameMantra Team
Live ops is where the revenue actually concentrates
The overwhelming majority of in-app purchase revenue now comes from games running active operations. That reframes live ops from a nice-to-have to the product.
Industry analysis of the 2026 mobile market puts around 84% of all in-app purchase revenue in games running active live operations, with structured live-ops programmes reporting roughly two to three times the lifetime value per player of games without them. (PocketGamer.biz)
Numbers like that get quoted as encouragement to "do more live ops". The more useful reading is about where they leave a game that does not.
What the concentration actually says
A figure that high is not describing a competitive advantage. It is describing a precondition. If nearly all purchase revenue flows through games under active operation, then a game that ships and moves on is not competing for a smaller share of the market — it is largely outside the part of the market where money changes hands.
That is a different strategic statement than "live ops improves results". Improvement is optional. A precondition is not.
The reason is straightforward once you look at when purchases happen. Very little revenue arrives in the first days after install. It accumulates over months, from players who stayed, at moments when the game gave them a specific reason to buy. A game with no operating calendar has a short window in which anything can happen and then a long tail of players quietly leaving. The revenue was never in the launch. It was in the year afterwards, and only games that showed up for that year collected it.
The part that is not "more events"
The instinctive response to this is to add events. That is a partial reading and it produces the wrong kind of work.
What separates games capturing this revenue is not event count. It is that the game keeps changing in response to what players do — new reasons to play, adjusted difficulty and pacing, offers that match where a player actually is. Events are one delivery mechanism for that. They are not the thing itself.
You can see the difference in games that run a heavy event calendar and still plateau. The calendar is full, the events are well produced, and the underlying loop has not changed in a year. Players who exhausted the loop are not brought back by another event in the same shape. The calendar is activity, not operation.
The same industry analysis notes that revenue is concentrating specifically in mid-core and strategy titles with deep economies and long player lifecycles. That is consistent with the above: those games have enough underneath them that continued operation has something to operate on. A game with a thin economy runs out of levers quickly no matter how many events it schedules. (PocketGamer.biz)
Why small studios read this as bad news, and shouldn't entirely
The obvious objection is resourcing. Live operations at the scale the big titles run it needs a dedicated team, and most studios do not have one. If the price of admission is a live-ops department, a lot of games are excluded by budget.
That framing overstates the requirement, though not to zero.
What actually drives the outcome is that something in the game responds to the player rather than staying fixed. A game where offers, difficulty, and content pacing adapt to what a player is doing is operating, whether that adaptation is produced by a team making weekly decisions or by systems making them continuously. The second is available to studios who cannot staff the first.
What is genuinely not available on a small budget is bespoke, hand-produced content every week. That is the part of large-studio live ops that does not scale down, and trying to imitate it is how small teams burn out. The reusable, repeatable parts — a recurring event structure whose contents change, offers that select themselves based on player state, pacing that adjusts — carry most of the benefit at a fraction of the operational cost.
See how we handle continuous operation without a dedicated team →
What to check in your own game
The question worth asking is not "do we do live ops". It is whether anything about the experience differs for a player based on where they are in the game.
If two players — one on their third day, one on their third month — see the same store, the same offers, and the same pacing, the game is not operating regardless of what the event calendar says. Both of them are being served a design that was correct for whoever it was written for and is wrong for at least one of them.
If the game's economy has one meaningful thing to buy and one way to earn, there is very little for continued operation to work with. Depth is what gives operation somewhere to go, which is why the depth and the revenue concentration show up in the same genres.
And if the last twelve months of change were all content and none of it systems, the game is being fed rather than operated. Content gets consumed. Systems keep producing reasons to return after the content runs out.
None of this argues that every game should become a mid-core strategy title. It argues that the revenue is where the operation is, that operation means responsiveness rather than volume, and that the responsive part is the part a small team can actually build.
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.