This PvX Partners guide lays out a 100+ item mobile UA audit, run top-down from a statistical validity gate through account-level, dimensional, delivery, and creative checks to final prioritization, each with a formula and cadence. It argues the biggest wins hide in the checks teams usually skip, and pitches PvX Delta as the tool that runs them all nightly.
Oct 02, 2026 - 15 min

A good UA manager runs maybe 20 checks on a good morning. The account in front of them supports more than a hundred distinct ones — each metric family crossed with each dimension it can be sliced by, plus the delivery, creative and prioritization checks that sit on top. This mobile user acquisition audit checklist lists all of them, grouped in the order you should run them, with the formula for each and a link to the guide that explains how to diagnose it. Nobody runs all of it by hand. The point of writing it down is to decide which ones you'll run daily, which weekly, which you'll automate, and which you'll consciously skip.
The checklist mirrors the structure of the PvX Delta audit specification, which is organized the way an experienced UA lead reads an account: from the top down, gated for noise, and deduplicated at the end.

Three rules apply to every item.
Each check below gives the formula to compute, how often to run it, and the guide that explains how to diagnose it.

The coverage matrix. Most cells are a change-in-trend check; ROAS and retention also get a vs-norm check at OS, geo, network and campaign level.
Run this before anything else, on every slice. It's the check that makes all the others trustworthy.
What the gate looks like on a real run, using the spec's illustrative sample: 412 slices evaluated, 37 suppressed. One ad network's tier-2 Android campaign spent $38 a day — 1.7% of its parent — so it failed materiality despite having valid volume. A UK broad ad set had 6,900 impressions and 8 installs a day, failing validity at daily grain until pooled.
Aggregate first — but remember to agree what "aggregate" means. Paid-only and paid-plus-organic (eCPI, eROAS) give different answers.
Clicks trend is deliberately missing. Clicks alone don't diagnose anything that CTR and CVR don't already cover, so the spec deleted those checks.
Two readings from the spec's illustrative samples show why Stage 1 is only a starting point:
Run the same metric families down each dimension. The dimension that isolates the move usually names the cause.
Never judge iOS against Android. Their auctions, attribution (ATT, SKAN, AdAttributionKit modeling) and user economics are structurally different. A synchronized iOS-only cliff across every campaign on one date is usually measurement.
Countries carry their own holidays, sales events, FX effects and localization problems. In one spec sample, Japan's CPI rose 13% entirely through CVR because a seasonal store update had shipped English-only screenshots.
A move on every network is the market or your store. A move on one network is that network.
Blended campaign metrics hide ad set failures, especially with campaign-level budget optimization. The ad set is often where the actual problem lives.
This only works if names are machine-readable. If your naming is inconsistent, fix that first: campaign naming convention.
Placement mix (Reels, Stories, Feed, Audience Network; Google's channels) matters, but Meta's API doesn't currently expose placement cleanly enough to run this at the same depth as the rest. Treat it as a manual review for now: placement performance for app campaigns.
These don't fit the "metric × dimension" grid. They look for specific delivery conditions.
The last row is a manual review item rather than something to automate blindly: the right call depends on the bid strategy and recent edits. Background is in cost cap vs bid cap vs lowest cost.
A worked example of the capped-winner check, from the spec's illustrative sample: a US iOS campaign at 99.5% utilization over three days, D30 ROAS 1.66× the account norm, frequency up only 5% and new reach still growing. The last budget raise moved CPI just 4.8%. The call was one +25% step, then watch.
Creative checks run at ad level, mostly weekly, and are the checks humans skip most often because they're the most tedious.
Two cautions from the spec. First, per-creative ROAS is the noisiest ranking you can build: in one illustrative sample, the raw #1 creative at 88% D7 ROAS turned out to have one $4.2k payer carrying 71% of its cohort's revenue. Second, rank on efficiency (IPM) and outcome (D7 ROAS), not spend — the two lists disagree, and the disagreement is where the insight is. Format data is currently unavailable on Meta and only partly available on Google, which is why row 10 is a manual review. The upstream process is in a creative testing framework for mobile apps.
Without this step, the checks above will drown you. One root cause fires at many depths at once: a single network's CPM spike trips aggregate, OS, geo and campaign CPM checks simultaneously.
The first four steps are covered in spend at risk prioritization.
In the spec's illustrative prioritization run, 41 open flags collapsed to 14 findings. Two data-integrity issues went to the top by rule, and five were surfaced by score. The remaining nine went to a watchlist.
Run daily:
Run weekly:
The logic: delivery metrics move and can be fixed daily. Cohort metrics need time to mature and are noisy at daily grain, so their norms are judged weekly. Why that split matters is in which UA checks to run daily and which weekly. How to tell a genuine shift from noise is in detecting trend changes in UA metrics.

Run the math on a mid-size account: a dozen metric families across five countries plus a rest-of-world cluster, four networks, 30 campaigns and 80 ad sets, re-read every day against a baseline. Add the weekly creative pass over a few hundred ads. No one reads all of that before stand-up. What gets skipped follows a pattern:
The 25 checks with the most spend at risk when skipped — and the one-line formula for each — are in 25 mobile UA checks every team should automate. How to set up the daily review itself is in how to automate your daily UA campaign review.
The checks are the same for every mobile app; what changes is which day you judge on and which dimension carries the most risk.

For games, the store page and the first session carry most of the CVR and D1 retention risk. For subscription apps, the equivalent is the paywall: a trial-start drop that hits every network on the same day is a product change, not a media one. Either way, pair the gaming example with the non-gaming one when you set thresholds — the mechanics differ even where the checks don't.
How often should I run a full UA audit? Split it. Delivery and cost checks daily, cohort and vs-norm checks weekly, and a full top-to-bottom review (including naming hygiene and attribution settings) monthly or after any major account restructure.
Which checks should a small team run first? The validity gate, the account-level CPI decomposition, ROAS trend on matured cohorts, creative fatigue on your top five creatives by spend, and the budget-capped winners check. That set catches most of the money at stake.
Do I need an MMP to run this checklist? For the delivery and cost checks, no — the ad networks report those. For ROAS, retention and cross-network comparisons, yes. Network-reported conversions can't be compared across networks on the same basis.
What about SKAN and AdAttributionKit? Treat iOS cohort metrics as partly modeled. Read iOS against its own history, and treat synchronized iOS-only step changes as a measurement question first.
PvX Delta is built on this checklist. It runs 100+ deterministic checks from these families across your MMP (AppsFlyer, Adjust or Singular) and your Meta Ads and Google Ads accounts: daily checks every night, weekly checks on their weekly cadence. The validity gate and prioritization run on every pass, and results arrive each morning as a decision brief. There are no prompts to write and no dashboards to build; setup is a data connection. Delta is advisory — it tells you what to change and why, and you make the change. The family-by-family reference is in the PvX Delta check library; how the stages fit together is in how PvX Delta works. If you're comparing approaches, deterministic checks vs anomaly detection covers the trade-off.
.png-j99mmp.png)
Oct 22, 2026 - 7 minutes

Oct 19, 2026 - 6 minutes

Oct 19, 2026 - 8 minutes
Some of the fastest growing businesses in the industry