Why All of the Best Mobile Games Are Doing Their Marketing in House?

A mobile player sees, on average, 977 other commercial messages in a single day, according to AppAgent. A game ad has to cut through nearly a thousand rival messages before it even registers. That is the environment studios are operating in, and it goes some way to explaining why the studios growing most consistently are the ones that have stopped outsourcing the problem entirely.

The data that tells you what is working lives inside the product, not inside an agency's reporting deck.

The shift toward in-house marketing in mobile gaming is less a trend and more a response to a structural mismatch. The agency model was built for campaigns with a clear start and end, for products that stay largely the same between launch and review. Mobile games do not work that way. They update constantly, their player behaviour shifts week to week, and the data that tells you what is and is not working lives inside the product. An external agency, however capable, is always working at a remove from that information.

What the best studios have worked out is that marketing and product development are the same discipline run at different stages. The studios that have understood this earliest have built accordingly, and the ones still treating marketing as a post-launch function are paying for it in churn rates they cannot explain.

Which Studios Have Actually Brought Marketing In-House

The clearest examples are studios that had enough scale to see the agency model failing them before most others did. Supercell moved its creative testing in-house after finding that external agencies were too slow to iterate on ad creative at the speed the algorithm required. Jam City built a dedicated internal UA team after deciding that the cost-per-install targets they needed could not be hit through third-party buying. Playtika has built internal data science teams that sit alongside its marketing function, so that player behaviour feeds into campaign decisions in near real time.

These are studios that tried the agency route, found it wanting, and rebuilt. The common thread is speed. Mobile game marketing runs on creative iteration, and creative iteration runs on fast feedback. A studio testing ten ad creatives a week and reading the results within 48 hours will outlearn a studio waiting for an agency's weekly report, regardless of how good that agency's strategy is on paper.

The studios still using external agencies tend to use them in a specific way: for specialist execution in areas where in-house capability is thin, such as influencer partnerships or connected TV, rather than as the primary growth function. That distinction matters. The agency is a tool, not the strategy.

Why the Agency Model Breaks Down for Mobile Games

Traditional agency structures were designed around campaign cycles. A brief goes in, work comes back, it runs for a defined period, and then performance is reviewed. That rhythm suits product categories where the thing being marketed stays largely constant. Mobile games are not that. A live game receiving a major content update in week three of a campaign has a different value proposition than it did when the brief was written, and an external agency is rarely close enough to the product to respond to that in real time.

The creative problem is just as acute. According to AppsFlyer's Creative Optimization Report, the top 2% of creatives drive 53% of ad spend in gaming. That means finding winners fast and scaling them before the algorithm moves on. An in-house team that can produce, test, and read five new concepts in a week will find those winners faster than a team separated from the product by a briefing process and a client services layer.

There is also a category knowledge problem. Mobile game marketing is a specialism, and the practitioners who are genuinely good at it tend not to sit in generalist agencies. They sit in studios. The best UA managers in mobile gaming have usually come from inside the industry, which means studios that invest in building those people internally end up with a capability that is genuinely hard to replicate through procurement.

Before briefing an external agency, map out which parts of your marketing function require real-time access to player data. Any function that does should be kept in-house from the start, even if it starts as a single person.

The Data Feedback Loop Problem

The fundamental problem with external marketing for mobile games is that the data sits in the wrong place. Player behaviour, session patterns, drop-off points, and feature engagement all live inside the product. An agency working on acquisition has access to the top of that funnel and very little else. They can tell you how many people installed the game and what creative drove that install. What they cannot tell you is whether those players stayed, what made the ones who stayed different from the ones who left, and what that means for who you should be targeting next.

We see this play out in how studios read their own numbers. Download figures rise, and the temptation is to call that growth. But day-three, day-five, and day-seven retention tell a different story, and those figures are almost never surfaced clearly in an agency's reporting deck. The growth looks real until the cohort data arrives and shows that a large proportion of those installs churned before they ever became habitual players.

Download numbers rising tells you nothing about health if retention at day seven is collapsing quietly underneath.

The studios that close this loop do so by putting the person responsible for acquisition in the same room, or at least the same weekly meeting, as the person reading retention and engagement data. That is not a structural innovation, but it requires the marketing function to be internal. You cannot run that meeting with a third party who has contractual access to a subset of your analytics.

Why Platform Choice Shapes Your Addressable Marketing Audience Before Launch

Platform decisions made during development have direct marketing consequences that most studios underestimate before launch. We worked on a bootstrapped social football platform where the client originally planned to launch on both iOS and Android. As scope grew and budget tightened, we paused Android development midway through the project and reallocated all remaining budget to the iOS build. The decision made sense from a delivery standpoint. The marketing consequences were more painful.

The target audience for that platform skewed younger, and younger audiences in the UK and Europe skew toward Android. Launching iOS-only meant the product was built and marketed to the more polished version of a smaller market segment. Day-one adoption was roughly half what it would have been if both platforms had been ready. The studio had to introduce advertising and abandon the subscription model because the user base was never large enough to make subscriptions viable.

This is a decision that looks like a build decision and is actually a marketing decision. The platform you launch on sets the ceiling for your addressable audience on day one, and that ceiling shapes every acquisition cost and retention target that follows. Studios that treat platform strategy as purely a development conversation, separate from whoever owns growth, tend to discover this too late.

When budget forces a platform trade-off, model the demographic split of your target audience by platform before deciding which to prioritise. The cheaper build decision and the right marketing decision are often not the same choice.

When the Growth Mechanic Is the Product

The most effective acquisition mechanisms in mobile gaming are often built into the product rather than layered on top of it. This is worth stating plainly because studios frequently think of viral growth as a marketing problem when it is actually a design problem. The mechanism needs to be there before the marketing starts.

We worked on a travel OTA product aimed at adults in their twenties and thirties, focused on group bookings. After launch, the team tried the standard post-launch acquisition toolkit: referral incentives, push notifications, social sharing prompts, and email campaigns. None of it moved the numbers in any meaningful way. What actually worked was a loop built into the booking flow itself. When one person organised a group trip, the app prompted every individual traveller in that group to download the app to handle communication and submit passport details. One person booking a trip for ten people generated nine new installs, each of whom could then trigger their own cohort.

That mechanic was not a marketing idea. It was a product design decision that happened to be the most effective acquisition tool the platform had. Studios that separate the growth function from the product function tend to miss these opportunities entirely, because the person who could see them is not in the room when the core flows are being designed.

Why Retention Data Needs to Reach the Build Team, Not Just the Marketing Team

Retention data is routinely treated as a marketing metric. It is read by the UA team, discussed in growth meetings, and used to adjust targeting and creative strategy. What it is rarely used for is changing the product. That gap is where studios lose most of their value.

We worked on a genetics wellness app where the audit revealed that the brand promise was genuinely strong. The narrative around giving users a real inside look at how their body works and how it is ageing was compelling and well-constructed. The problem was that the product had been built almost entirely by a developer team who had stripped out the storytelling in favour of functional delivery. Users were receiving their data but not connecting emotionally with it, and that disconnection was showing up directly in retention numbers. The fix was not to redesign the brand. It was to reintroduce narrative into the product itself, giving users a sense of identity and progress rather than just a data readout.

That kind of decision can only be made if the retention signal reaches the people building the product. In studios where marketing and development are separate teams with separate reporting lines, the signal rarely travels that far. An external agency certainly cannot carry it there. The person reading the churn data and the person making build decisions need to be in regular, direct conversation, which is an organisational requirement as much as a data requirement.

Set up a monthly session where retention data is presented directly to the build team, not just the growth team. The people who can change the product need to see where players are leaving and why, before the next sprint begins.

What In-House Marketing Actually Requires From a Studio

The decision to bring marketing in-house is often framed as a cost or capability question. It is also a structural question, and studios that answer it only on cost grounds tend to build something that looks like an in-house function but behaves like a slow agency.

An in-house marketing function that works requires four things at minimum.

1. A creative production capability fast enough to generate and test new concepts weekly, not monthly.
2. Direct access to product analytics, not a dashboard curated by a data team on a reporting cycle.
3. A seat in the product development process, so that growth considerations reach build decisions before features are locked.
4. A clear owner of the relationship between acquisition data and retention data, who has the authority to act on what that relationship shows.

The fourth point is the one studios most commonly skip. They hire a UA manager and a creative strategist and call it done, leaving no one responsible for the connection between what the ads promise and what the product delivers. That disconnection is where the most expensive churn originates.

When the Brand Promise and the Product Tell Different Stories

The most common retention problem in mobile games is a promise gap. The ad creative sets an expectation, and the product does not meet it. Players install, play for twenty minutes, and leave without ever expressing why. The studio reads this as a creative targeting problem and changes the ads. The real problem is that the ad was accurate about a version of the game that only exists in the creative.

On the genetics wellness app we worked on, the brand promise was sound. The marketing narrative around understanding how your body works and how you can improve it was exactly what users said they wanted. The product had been built without that narrative present. The data was there, but the story around the data had been removed in development, leaving users with a functional interface that told them things without making those things feel relevant to their lives. Retention suffered directly as a result.

The fix required reintroducing narrative into the product, not changing the brand positioning. But that decision could only be reached through an audit that connected the marketing promise to the product experience and traced the gap between them. Studios with separate marketing and product functions often never make that connection. The marketing team optimises the creative, the product team optimises the feature set, and nobody owns the space between them.

What This Means for How Studios Should Plan From Day One

The studios that handle this best do not decide to build an in-house marketing function after launch when acquisition costs turn out to be higher than expected. They design the growth function into the studio structure before a line of code is written. That means the person responsible for acquisition is contributing to decisions about onboarding, about what the first session looks like, about which platform to prioritise, and about what the core loop communicates to a player who has never heard of the game.

Platform strategy is a clear example. As we found on the social football platform, the decision to launch iOS-only was made as a budget and delivery call, without fully modelling the marketing consequences. A growth lead with a seat at that table would have mapped the Android skew in the target demographic before the decision was finalised. The build decision might still have been the same, but the launch plan would have accounted for a narrower day-one market rather than discovering it after.

Planning from day one also means building the data infrastructure before you need it. The studio that launches with proper cohort tracking, that can see day-one, day-three, and day-seven retention by acquisition source and creative type from week one, is the studio that can make fast decisions rather than retrospective ones. That infrastructure is a product tool that the marketing function depends on, and it needs to be commissioned by the people building the product, not retrofitted by the people running campaigns.

Conclusion

The move to in-house marketing in mobile gaming is a response to a genuine structural problem with how external agencies relate to live products. The data lives inside the product. The growth mechanics live inside the product. The retention signal lives inside the product. A marketing function that operates at a remove from all of that is always working with incomplete information, and incomplete information produces the wrong decisions at the wrong speed.

The studios that have built this well share a common approach. They treat marketing as a product discipline, place the growth function inside the development process, and make sure the people reading acquisition data are in regular conversation with the people making build decisions. The brand promise and the product experience are held by the same team, which is the only arrangement that prevents the promise gap from opening up.

Building this from day one costs less than rebuilding it after a launch that underperforms. The platform decisions, the onboarding design, the viral loop architecture, and the data infrastructure all need growth thinking applied before the first user arrives. Studios that plan for this from the start do not have to unpick the consequences of decisions made in its absence.

If you are planning a mobile game launch or rethinking how your studio's growth function is structured, let's talk about your product strategy.

Frequently Asked Questions