Mobile Attribution After SKAN 4: What Marketers Actually Get to Measure
App attribution was already uncomfortable before Apple introduced SKAdNetwork. The ATT prompt killed deterministic, person-level tracking for the majority of iOS installs, and most paid acquisition teams spent 2022–2023 flying partially blind. SKAN 4 is a genuine improvement — but it doesn't return you to the world you had in 2020. Understanding exactly what you get, what you don't, and what you can reconstruct from adjacent signals is the difference between a budget you can defend and one you're quietly guessing at.
What Changed From SKAN 3 to SKAN 4
The core mechanism is the same: Apple's framework sends a postback directly to your ad network, not to your measurement partner, and strips out any device-level ID. What SKAN 4 added on top of that foundation:
Hierarchical postbacks. Instead of one postback, SKAN 4 sends up to three — each at a different privacy threshold. The first postback fires at a lower crowd anonymity threshold and can carry a fine-grained conversion value. The second and third postbacks fire later (days 3–7 and 7–35 after install) at higher thresholds, giving you coarse-grained data on downstream behavior.
Coarse conversion values. Where SKAN 3 gave you one 6-bit conversion value (0–63), SKAN 4 adds a coarse-value field (low, medium, high) for postbacks that don't meet Apple's crowd anonymity threshold for the fine-grained value. This means you get something on more installs, rather than a null return.
Web-to-app attribution. SKAN 4 extends the framework to Safari-to-app install flows, which matters if you run any web landing page traffic into an App Store conversion path.
Longer re-engagement windows. SKAN 4 supports re-engagement postbacks, not just acquisition. This is theoretically useful for retargeting — practically, adoption by networks and MMPs is still maturing.
What SKAN 4 Actually Gives You
Let's be specific. Here's what you can reasonably expect to measure post-launch:
| Signal | Available in SKAN 4 | Notes |
|---|---|---|
| Campaign-level installs | Yes | Via postback, with crowd anonymity delay |
| Ad group / creative installs | Yes, with limits | Only when threshold is met; may be null |
| Fine-grained conversion value | Yes (postback 1 only) | Delayed 24–48h minimum, up to several days |
| Coarse conversion value (L/M/H) | Yes (postbacks 2 & 3) | Categorical, not numeric |
| Revenue tied to device | No | No MMP can reconstruct individual ARPU |
| LTV curves by cohort | Partial | Cohort-level modeling only; not user-level |
| Re-engagement attribution | Yes (framework only) | Network + MMP support still inconsistent |
| ROAS at campaign level | Modeled | Requires probabilistic modeling layer |
The hard truth: you will not get clean, deterministic ROAS figures at the ad-set or creative level on iOS. Anyone selling you a dashboard that claims otherwise is either showing you Android data, a modeled estimate, or data from the small slice of users who consented via ATT.
The Three Data Sources You're Actually Working With
A practical iOS measurement stack in 2026 combines three things — SKAN postbacks alone aren't enough:
1. SKAdNetwork postbacks via your MMP
Your mobile measurement partner (AppsFlyer, Adjust, Branch, Singular — pick one) aggregates the postbacks Apple sends to each network and normalizes them into a single reporting interface. This is your most privacy-safe signal and the one that survives ATT opt-outs. The limitation is delay (up to 35 days for third-postback data) and the coarseness of late-window values.
2. ATT-consented device data
For users who tap "Allow Tracking," you still get deterministic, IDFA-based attribution the same way you did pre-iOS 14. In most consumer app categories, ATT opt-in rates run somewhere between 25% and 45% depending on how and when the prompt is presented. This cohort is small but clean — treat it as your calibration set.
3. Modeled / probabilistic attribution
Every major MMP now offers a modeling layer that uses aggregated signals — install volume, revenue events, campaign spend, geo, device type — to estimate conversion rates and ROAS for the non-consented population. This is an informed estimate, not measurement. Label it as such internally so you don't conflate it with hard data.
If you're running a 2026 mobile user acquisition strategy, all three layers need to be wired up before you scale spend. Starting a campaign without an MMP configured means you're funding a black box.
How to Set Up Your Conversion Value Schema
This is where most teams leave signal on the table. Your 6-bit fine-grained conversion value (0–63) needs to encode the most meaningful early in-app events — the ones that actually predict long-term value — within the measurement window Apple gives you (typically 24–48 hours for postback 1).
A workable schema for most apps:
- Bits 0–2: Engagement tier (no action, tutorial complete, core action taken)
- Bits 3–5: Revenue or intent signal (no purchase, soft conversion, first purchase, purchase above threshold)
For subscription apps, "trial started" often beats "purchase" as a predictive signal because it happens earlier. For marketplaces, the first listing view or first message sent is frequently more predictive of eventual transaction than any single screen. Spend a sprint analyzing your own cohort data before locking the schema — the default MMPs offer almost never matches your funnel.
The coarse values on postbacks 2 and 3 should map to revenue brackets or engagement depth milestones that you can define per campaign type. high should mean something specific: subscribed, made 2+ purchases, reached a retention-predicting event. Don't leave it as undefined.
Running paid acquisition on iOS without a tuned conversion schema is like running a paid search campaign without conversion tracking. Our mobile app marketing services include SKAN schema design as part of any growth engagement — because the schema determines what you can optimize against.
Android and the Parallel Reality
While iOS lives in SKAN's privacy sandbox, Android remains largely deterministic via Google Play's referrer API and Google's own attribution infrastructure — though Google's Privacy Sandbox for Android is shipping incrementally and will eventually create similar constraints.
For now, Android gives you cleaner signal: device-level attribution, user-level LTV, cohort analysis without modeling. That's why most teams use their Android data as a reality check on their iOS models. If iOS modeled ROAS is dramatically above or below Android ROAS for the same creative, something is off — either the model is miscalibrated or the audience composition is genuinely different (often both).
Don't assume Android = iOS for planning purposes. In our engagements, CPI and ROAS vary meaningfully between platforms, sometimes by 30–50%, depending on category and geography. Run them as separate line items in your budget, not a blended pool.
What This Means for Campaign Optimization
The operational impact of SKAN 4's measurement model on day-to-day campaign management:
Creative testing is harder. Without user-level data, statistical significance at the creative level requires larger install volumes per variant before the crowd anonymity thresholds unlock fine-grained values. Plan for longer test cycles or consolidate creative variants to hit volume faster.
Budget allocation relies more on incrementality testing. Geo holdout tests and synthetic control experiments are now more reliable than MMP-reported ROAS for validating whether a channel actually drives incremental installs. This takes planning — you can't run a holdout test retroactively.
Optimization windows extend. Bidding algorithms on Meta, Google, and Apple Search Ads consume SKAN postback data as training signal. Postback delays mean the algorithms optimize on lagged data. Set expectations with stakeholders: iOS campaigns take longer to ramp than they did pre-ATT, and early-week performance reports are systematically incomplete.
Apple Search Ads remains the cleanest signal. Because Apple runs both the OS and the ad platform, Apple Search Ads (ASA) attribution operates within a privileged data environment — you get install-level reporting that no third-party network can match on iOS. If you're not already running ASA as part of your mix, it should be on your short list. For more on channel mix, the 12 ways mobile app marketing agencies drive growth for new apps post covers the broader acquisition landscape.
FAQ
Does SKAN 4 work with all ad networks?
No — networks need to be explicitly certified by Apple to receive SKAN postbacks. The major platforms (Meta, Google, Apple Search Ads, TikTok, ironSource, Digital Turbine) are certified. Smaller or emerging DSPs may not be, which means those spend pools are effectively unattributed on iOS. Check your MMP's network compatibility list before allocating budget.
How long does it take to receive SKAN 4 postback data?
Postback 1 typically arrives 24–48 hours after install, though Apple can delay it further if the crowd anonymity threshold hasn't been met. Postbacks 2 and 3 arrive days 3–7 and 7–35 respectively. For practical reporting, plan on a 3-day lag for early signals and a 35-day lag for full third-postback data.
Can I use my MMP's modeled data for budget decisions?
Yes, but label it clearly as an estimate. Modeled attribution is better than nothing and generally directionally accurate at the channel level. The risk is over-indexing on modeled ROAS when the underlying model is trained on limited ATT-consented data. Cross-validate with incrementality tests before making large budget shifts based on modeled numbers alone.
What's the difference between fine-grained and coarse conversion values?
Fine-grained values are the 6-bit numeric value (0–63) you configure in your MMP, representing specific in-app events. Coarse values (low, medium, high) are Apple's categorical fallback when the crowd anonymity threshold for fine-grained data isn't met. Coarse values still carry signal — they tell you which revenue or engagement tier a cohort lands in — but they're less precise for optimization.
Do I still need an MMP in a SKAN 4 world?
Yes. Apple sends postbacks directly to ad networks, not to you. Your MMP pulls those postbacks from each network, normalizes them, and gives you a unified view across channels. Without an MMP, you're comparing raw postback counts from different networks with no common schema. The MMP also handles conversion value schema configuration, probabilistic modeling, and incrementality testing infrastructure.
How does SKAN 4 affect re-engagement campaigns?
SKAN 4 added re-engagement postback support, which means iOS retargeting campaigns can theoretically receive attribution credit. In practice, network and MMP support for re-engagement postbacks is still rolling out. Check with your MMP and your retargeting partner on their specific implementation status before investing heavily in iOS re-engagement as an attributed channel.
SKAN 4 is a better measurement framework than what came before it — but it still asks you to manage a business on cohort-level signals, modeling layers, and lagged data. The teams winning on iOS right now are the ones who designed their measurement stack deliberately: a tuned conversion schema, a calibrated MMP, Android as a reality check, and incrementality tests for major budget decisions. That's not more complicated than pre-ATT attribution, but it is different.
If you want to audit your current attribution setup or build a measurement strategy that holds up on both platforms, our mobile app marketing team can help — or grab 30 minutes on the calendar and we'll walk through your specific stack.
