Budget iOS and Android separately because they are measured under different rules. Android still gives you near user-level attribution you can broadly trust. iOS gives you delayed, aggregated, modelled signals that two tools will read two different ways. One shared budget forces every decision to mix a number you can trust with one you cannot.
I run paid user acquisition for a GCC fintech app across both operating systems, and the most expensive assumption I see in the region is that iOS and Android are two rows of the same report. They are not. They are two different countries with different disclosure laws, and your budget should be split at the border.
Why are iOS and Android different measurement regimes?
Since Apple's App Tracking Transparency prompt arrived, iOS attribution runs through SKAdNetwork and its successor AdAttributionKit (AAK): aggregated, delayed and deliberately limited. Android still runs largely on device identifiers, because Google shelved its Privacy Sandbox plans and the GAID lives on. Same app, same ads, two entirely different measurement systems.
ATT opt-in sits around a quarter to a third globally, and lower in some categories, so most iOS users are invisible to the old person-level attribution. Android has no equivalent prompt. The practical rule I hold on the account I run: treat iOS and Android as separate measurement problems, and never extrapolate results on one OS from the other.
| Android | iOS | |
|---|---|---|
| Attribution basis | Device identifiers, near user-level | SKAdNetwork / AdAttributionKit: aggregated, delayed |
| Source agreement | MMP and ad platform land in the same range | Trusted sources can sit 3-5x apart |
| Where paid hides | Rarely hides | Inside "organic" after ATT |
| Cost readings | Usually face value | Inflated by "Limited" delivery states |
| Scaling rule | Scale where MMP and platform agree | Hold until sources converge; consolidate volume |
Why do my iOS sources disagree when my Android sources agree?
Because Android sources count the same events, while iOS sources each model a different guess. On the GCC fintech app I run, two trusted sources sat as much as 3-5x apart on iOS cost per registration. The same two sources on Android landed in the same range. That gap is structural. No amount of dashboard staring closes it.
The decision rule that falls out of this is the most useful sentence in this article: scale where your sources agree, hold where they disagree. Android earned its budget increases because two independent reads confirmed each other. iOS held steady until measurement cleared, because pouring budget into a number you cannot verify is not scaling, it is gambling.
One calibration note: even where sources "agree", expect daylight. A platform's self-report and your MMP disagreed by roughly 30% on the same registrations on the account I run. Agreement means a stable, bounded gap, not identical numbers. Disagreement means multiples.
Where did my paid iOS installs go?
Into organic. When an iOS user declines the ATT prompt, the link between the ad and the install breaks, and the install rolls into the organic line. On the app I run, the single biggest reported source of registrations reads as organic, and a real share of that is paid iOS activity that attribution can no longer label.
The consequence: if you judge iOS purely on what the ad platform claims it drove, you will under-credit it and then over-cut it. The honest read is total iOS registrations against total iOS spend, watched over time. If the total moves when spend moves, iOS is working, whatever the labels say. The full mechanics are in SKAdNetwork explained for GCC app marketers.
Why does a creative winner on Android fail on iOS?
Because the failure lives in a different layer on each OS. On Android, a failing ad usually means the creative or the audience intent is wrong, and the data to confirm that is reliable. On iOS, the same concept can fail for reasons the creative never touches: suppressed measurement, throttled delivery, a different funnel experience, a different language and intent mix.
On the account I run, concept families have died on one OS and earned their slot on the other, in both directions. iOS also skews more English-language in the GCC, so the same message can land differently before measurement even enters the picture. The discipline that survived all of this: judge every execution on its own data, per platform and per OS, never on the concept's reputation elsewhere.
And before you rule an iOS ad a creative failure, rule out a measurement failure first. Check the delivery state and check whether the campaign is even clearing Apple's signal thresholds. Half of "iOS creative problems" are neither.
What does a "Limited" delivery state do to iOS cost readings?
It inflates them. On Meta, a "Limited" state tied to the tracking setup throttles delivery, and the cost per result you see is artificially high while it lasts. Judge that ad at face value and you will kill something that is actually working. Acknowledge the state first, then decide what the reading is worth.
There is a structural version of the same trap. SKAdNetwork and AAK only return usable data once a campaign clears Apple's crowd-anonymity thresholds, and a common working minimum is roughly 100 installs per campaign per day. Split your iOS budget across many small campaigns and every one of them reads as noise. Consolidation is not a preference on iOS, it is a measurement requirement.
Why does the GCC make separate budgeting non-optional?
Because the GCC skews iOS-heavy and high-value, the OS that is hardest to measure is often where your most valuable users live. Blend the two budgets and iOS looks systematically worse than it is: its paid wins hide in organic, its costs read inflated, and the reallocation maths quietly starves your best audience.
I see two failure modes in the region, and both are artifacts of shared budgeting. The first is over-cutting iOS because the dashboard undercounts it. The second is over-funding Android because it flatters, measurement is easy and the numbers agree, so the money drifts there by default.
Easy to measure is not the same thing as worth buying.
Budget each OS on its own evidence and both failure modes disappear.
How to budget iOS and Android separately
- Split campaigns, budget lines and reports by OS everywhere the platforms allow it. No shared pots.
- Set a separate target cost per OS, derived from each OS's own history. Never hold iOS to Android's number.
- On Android, make the MMP the referee and scale where the MMP and the platform broadly agree.
- On iOS, consolidate into fewer campaigns, each clearing roughly 100 installs per day, so SKAN/AAK returns signal you can read.
- Read iOS with organic in view. Track total iOS registrations against iOS spend, not just the attributed slice.
- Check delivery states before any iOS kill call. A "Limited" flag means the cost reading is inflated, not that the ad failed.
- Rebalance between the two OS on evidence, monthly or quarterly. Weekly rebalancing on iOS data is reacting to noise.
FAQ
Should iOS and Android have different CPA targets?
Yes, always. iOS systematically under-reports: paid installs hide in organic and postbacks arrive aggregated and late, so an attributed iOS registration usually carries invisible extras. Set each OS target from that OS's own history and downstream quality, not from a shared benchmark or from each other.
Why is my Android CPA lower than my iOS CPA?
Partly reality, partly artifact. Android auctions and audiences genuinely differ, but Android also counts nearly everything while iOS misses much of what it drives. Before concluding that Android "wins", check what total iOS registrations do when iOS spend moves. The unlabelled lift often changes the answer.
Can I copy a winning Android campaign to iOS?
The concept is worth testing, the structure rarely transfers. iOS needs consolidated campaigns clearing roughly 100 installs per day for usable SKAN/AAK signal, its own target costs and its own creative read. On the account I run, concepts have failed to travel in both directions. Test, never assume.
How should GCC apps split budget between iOS and Android?
There is no universal ratio. The GCC skews iOS-heavy and high-value, so a naive even split usually under-serves iOS. Decide from your own by-OS evidence: total registrations per OS against spend per OS, plus downstream quality per OS. The mistake is letting one blended budget decide by default.
Does ATT affect Android at all?
No. ATT, SKAdNetwork and AdAttributionKit are Apple-only. Google shelved its Privacy Sandbox plans in late 2025, so third-party identifiers still function on Android. That asymmetry is precisely why one measurement approach cannot serve both operating systems, and why one budget should not either.
What is AdAttributionKit?
AdAttributionKit (AAK) is Apple's successor to SKAdNetwork: the same aggregated, delayed, privacy-first attribution model with more capability, including re-engagement support. There was never a "SKAN 5.0". If your reporting language still says SKAN only, update it, because your setup is shifting underneath you.
Not sure whether your iOS budget is being judged on numbers you can trust? I run a free App Growth Review: a short, no-pitch look at your live campaigns, your attribution setup, and where the budget is leaking.
Get a free App Growth Review →
Related reading: SKAdNetwork explained for GCC app marketers, LTV by channel: why blended CAC lies to you and why GCC apps waste paid media budget.