Mobile UA analytics:
why most studios are flying blind

Most mobile game studios spending $100,000 to $300,000 a month on user acquisition run their mobile UA analytics the same way: one person, a spreadsheet, an MMP export, and not enough time to do it properly. That gap has a cost. It just doesn't show up on a line item.

How mobile UA analytics actually works at most studios

The UA manager runs the campaigns. When they need numbers, they pull an export from AppsFlyer or Adjust, open a spreadsheet someone built six months ago, paste the data in, and wait for the formulas to break. Then they fix the formulas, manually reconcile the store revenue, and 90 minutes later have a number they're not fully confident in.

Or, more often, they use the dashboard in the MMP, which shows raw ROAS, doesn't account for whale distortions, and doesn't align with App Store or Google Play revenue. They make the decision anyway because there's a standup in 20 minutes.

This isn't a failure of the UA manager. They're doing their actual job: running campaigns, managing creatives, talking to networks. Cleaning and analysing cohort data is a separate discipline and it's being squeezed into the margins of someone else's role.

What weak user acquisition analytics actually costs

The cost isn't a salary line. It's decision quality and it compounds over every week of UA spend.

Each of these creates a specific, measurable failure mode.

The 3-day lag problem

UA campaigns have momentum windows. A campaign performing well at $500/day on Meta, Google UAC, TikTok, or ASA can often scale to $2,000/day before the audience saturates, but only if you act within 48-72 hours of the signal appearing. After that, CPIs rise, performance regresses to mean, and the window closes.

If your D7 ROAS data takes three days to clean and review, you're systematically late to every scaling decision. You're not making bad calls; you're making correct calls on stale data, which has the same outcome.

The whale distortion problem

A single high-value spender in a cohort of 3,000 users can inflate that cohort's D7 ROAS by 40-100%. Without someone specifically looking for this in your cohort analysis, you'll scale a campaign that looked like a 1.3x ROAS winner and watch the D30 number come in at 0.6x.

This isn't rare. In any game with meaningful IAP revenue, it happens regularly. And it almost always goes undetected when nobody owns the mobile UA analytics function.

The revenue alignment problem

Your MMP, your ad networks, and your app stores report three different versions of the same revenue number. Without someone whose job is to reconcile them daily, you're making budget decisions on whichever number was easiest to pull, usually the MMP number, which tends to be the least accurate.

Why a dedicated analyst isn't always the right fix for mobile game UA analytics

The obvious solution sounds simple: hire a marketing data analyst. Assign them to UA. Problem solved.

In practice, it's more complicated.

For a studio spending EUR500K/month on UA, a dedicated analyst at EUR88-152K total annual cost is potentially worth it if they're fully productive from day one, focused exclusively on UA analytics, and not pulled into other data projects. That last condition is rarely met.

For a studio spending EUR50-200K/month on UA, the math is harder. The analyst is a significant fixed cost against a budget where every percentage point of efficiency matters and you're unlikely to get their full attention on UA alone.

There's also a hiring problem. A good marketing data analyst who understands mobile attribution, MMP data, cohort methodology, and UA decision-making is a rare profile. Most data analysts are generalists. Training them on the specifics of mobile UA analytics takes months, and the moment they're genuinely useful, they're also employable elsewhere.

What good UA analytics actually needs to do, daily

Strip it down to the core, and a functioning UA analytics system does four things, not weekly, daily:

• Align revenue across MMP, ad networks, and app stores into one clean number
• Detect and remove distortions such as whale users, attribution anomalies, and test traffic
• Calculate clean cohort ROAS at D1, D7, D14, D30 for every active campaign
• Surface decisions about which campaigns to scale, which to hold, and which to cut

Everything else, decks, presentations, ad-hoc queries, is secondary. These four functions are what protect your UA budget. They're also exactly what most studios do inconsistently, too slowly, or not at all.

The difference between these two standups isn't analytical sophistication. It's whether the work got done consistently, on time, before the decisions needed to be made.

How to automate mobile UA analytics without a full-time hire

The studios getting this right aren't all running large analytics teams. Some of them have solved the problem differently: by automating the four core functions entirely, so the UA team has clean, aligned, distortion-free cohort data every morning without anyone spending 20+ hours a week preparing it.

That's the model Cohortful is built on. Upload your exports from AppsFlyer, Adjust, Meta, Google, App Store, or Google Play, or connect via API, and your team gets clean D7 ROAS, automated cohort analysis, and clear scale/pause recommendations every day. No analyst required. No ticket queue. No Monday morning spreadsheet.

It doesn't replace strategic thinking. It replaces the 20+ hours a week of data plumbing that gets in the way of it.