How do you measure iOS app campaigns after ATT?
Gulf iOS users are the region's most valuable: iPhone penetration among high-income Saudis and UAE residents is among the highest anywhere, and their in-app spend shows it. That is exactly why ATT hurt here — the users you most want to measure are the ones Apple made hardest to track. The consolation: ATT opt-in rates in the Gulf trend above global averages, so a well-designed prompt buys you more real data here than it would in the US or Europe.
This guide explains what ATT actually changed, how SKAN 4 works in plain language, how to design conversion values that tell you something useful within Apple's limits, how to raise your opt-in rate, and how to combine it all into one iOS ROAS view your team can make decisions on.
What did ATT actually change for app advertisers?
Before 2021, ad networks matched an ad tap to an install using the IDFA — a device identifier available by default. App Tracking Transparency flipped the default: no cross-app identifier unless the user explicitly taps Allow on Apple's prompt, in your app and in the app that showed the ad.
The practical fallout: device-level attribution now only exists for the consented minority, retargeting pools on iOS shrank drastically, and the numbers in Meta, Snap, TikTok and Google dashboards became part-measured, part-modeled estimates. Campaigns still work — you just can no longer read them the old way. Note the useful exception: Apple Search Ads attributes through Apple's own AdServices framework, so its reporting does not depend on the ATT prompt at all.
How does SKAN 4 work, explained simply?
SKAdNetwork is Apple acting as a neutral scorekeeper. The ad network never learns who installed; instead, Apple sends anonymous postbacks saying 'this campaign produced an install, and the user's early behavior scored X'. That score is the conversion value — a number from 0 to 63 that you define the meaning of.
SKAN 4 sends up to three postbacks per install: one covering roughly the first two days, one for days 3–7, and one for days 8–35 — each randomly delayed so nobody can be identified by timing. If a campaign has too few installs, Apple blurs the data further: you get a coarse value (low/medium/high) or nothing at all. That is the crowd-anonymity system, and it is why fragmenting iOS spend across many small campaigns destroys your own measurement. Fewer, bigger campaigns literally see more.
How should you set SKAN conversion values for a Gulf app?
The conversion value is your only detailed signal, so spend it on what predicts revenue. Map the 0–63 fine values to the funnel steps and revenue bands that matter in your first 24–48 hours — for example: registration completed, trial started, first purchase, and rising revenue buckets for bigger baskets. Your MMP's conversion-value tooling (Adjust, AppsFlyer) manages the encoding; your job is choosing the events.
Two rules keep the data readable. First, measure what predicts long-term value, not everything — a subscription app cares about trial starts in the first day far more than tutorial completions. Second, keep the schema stable for at least a few weeks at a time: every change resets your ability to compare campaigns, and iOS optimization is slow enough already.
How do you raise ATT opt-in — and why the Gulf is an advantage?
You cannot change Apple's prompt, but you control everything around it. Show a pre-prompt screen first — one sentence, in the user's language, explaining what they get: fewer irrelevant ads, better recommendations, support for a free app. Then trigger the real prompt at a moment of goodwill — after the first successful action or aha moment — never as the first thing a cold install sees. Apps that prime the prompt this way commonly see opt-in rates far above those that fire it at launch.
The Gulf gives you a tailwind: regional opt-in rates trend above global averages, and an Arabic-language pre-prompt written naturally — not machine-translated — widens that gap further. Every extra point of opt-in enlarges the deterministic sample your MMP uses to calibrate its modeling, so the payoff compounds: better consented data makes your modeled numbers more accurate too.
How do you combine SKAN, MMP data and cohorts into one trustworthy view?
Triangulate three sources with clear jobs. SKAN postbacks are the baseline truth for paid iOS volume and early quality — incomplete but unbiased. Your MMP's consented device-level data provides the detailed funnel and LTV curves — biased toward users who trust you, but rich. And your backend revenue against total iOS spend is the referee: blended iOS ROAS that no attribution model can argue with.
Then set decision rules that respect the medium: judge iOS campaigns weekly, not daily, because postbacks arrive late by design; compare campaigns within SKAN rather than SKAN-to-Android; and when a network's dashboard disagrees with your MMP's SKAN report, trust the MMP — the network is grading its own homework. One more thing worth knowing: Apple is migrating SKAN into AdAttributionKit. Your MMP handles the plumbing — what carries over is exactly the discipline above: clean conversion values and consolidated campaigns.
How Ashayrah measures iOS for your app
Post-ATT iOS measurement is where most Gulf app teams quietly lose money, and it is one of the first things we fix.
-
The audit
We review your SKAN conversion values, ATT prompt flow, campaign structure and the gap between network dashboards and real revenue — and show you which iOS numbers you can actually trust. Free, 20 minutes, and the findings are yours.
-
The launch
Within 14 days: a conversion-value schema mapped to your revenue signals, a primed ATT flow in Arabic and English, campaigns consolidated so SKAN thresholds are met, and one iOS reporting view your team reads weekly.
-
The scale
Weekly optimization on SKAN cohorts and blended iOS ROAS: budget moves between campaigns on evidence, the schema stays stable long enough to compare, and modeling is re-checked against backend revenue every month.
Questions people also ask
Do I still need an MMP now that SKAN exists?
Yes. SKAN only covers paid iOS installs with coarse, delayed signals. An MMP decodes SKAN postbacks into readable reports, measures Android and consented iOS users at device level, ingests cost from every network, and models the gaps — without one, you are reading four ad dashboards that each grade their own homework.
What is a good ATT opt-in rate?
Rates vary widely by category and execution, but a primed prompt — pre-prompt screen, right timing, user's language — commonly doubles what a cold launch prompt achieves. Gulf audiences trend above global averages, so a well-executed Arabic flow reaching a third or more of users is a realistic ambition for consumer apps.
Why do my iOS campaign numbers arrive days late?
By design: SKAN postbacks are randomly delayed and batched into up to three windows covering 35 days, so no one can identify users by timing. Treat iOS as a weekly decision cycle. If you demand day-by-day iOS numbers, you will be reading modeled estimates, not measurements.
Can I still retarget iOS users after ATT?
Only the consented slice, which makes iOS retargeting pools small and expensive. Most Gulf apps get better returns shifting re-engagement to owned channels — push notifications, email, and WhatsApp — and reserving paid retargeting for Android, where device-level audiences still work.
Does Apple Search Ads need ATT consent to attribute installs?
No. Apple Search Ads uses Apple's own AdServices attribution, which works regardless of the ATT prompt. That makes ASA one of the most accurately measured iOS channels available — worth exploiting in a market as iPhone-heavy as the Gulf.