Meta Ads for Mobile Apps in 2026

---
title: "SKAdNetwork 4.0 and the ROAS Math That Justifies Your Mobile UA Budget"
published: true
description: "A technical walkthrough of configuring SKAdNetwork 4.0 postback windows, mapping coarse conversion values to LTV tiers, structuring Advantage+ App Campaigns against MMP attribution, and building unit economics that separate profitable UA from burning cash."
tags: mobile, ios, architecture, performance
canonical_url: https://blog.mvpfactory.co/skadnetwork-4-roas-math-mobile-ua
---

## What We Are Building

By the end of this guide you will have a working mental model — and concrete configuration — for three things:

1. SKAdNetwork 4.0 postback windows and why treating them identically breaks your measurement
2. A production-ready coarse conversion value mapping calibrated to LTV tiers
3. The unit economics spreadsheet that tells you whether to press scale or fix your funnel first

Let me show you a pattern I use in every project: anchor your MMP as the source of truth before you touch campaign structure. Everything downstream depends on it.

---

## Prerequisites

- An iOS app live on the App Store with SKAdNetwork integrated
- An MMP account (Adjust, AppsFlyer, or equivalent) with postback forwarding configured
- A Meta Ads account running or planning Advantage+ App Campaigns
- At least 60 days of cohort revenue data (you will need this for LTV calibration)
- Basic familiarity with mobile attribution concepts (postbacks, conversion values, cohort ROAS)

---

## Step 1 — Understand the Three Postback Windows

SKAdNetwork 4.0 introduced three distinct measurement windows. Most teams misconfigure these by treating them identically, which is the single most common cause of MMP-to-Meta reporting discrepancies above 20%.

| Window | Lookback | Conversion Value Type | Typical Signal |
|--------|----------|-----------------------|----------------|
| 1 | Day 0–2 | Fine (0–63) + Coarse | Early engagement, tutorial completion |
| 2 | Day 3–7 | Coarse only (low/medium/high) | First purchase, subscription trial |
| 3 | Day 8–35 | Coarse only (low/medium/high) | Repeat purchase, D30 LTV proxy |

The docs do not emphasize this enough, but fine-grained values in window 1 are only returned when your campaign clears Apple's crowd anonymity threshold. Plan for coarse values as your **baseline**, not your fallback. If you architect around fine values and drop below threshold, your window 2 and 3 data becomes uninterpretable.

---

## Step 2 — Map Coarse Conversion Values to LTV Tiers

Coarse values are not arbitrary. They are LTV bucketing tools — if you configure them intentionally. Here is the minimal setup to get this working for a subscription app:

Calibrate these thresholds against your actual cohort LTV data, not industry benchmarks. Run a 60-day cohort analysis, identify the natural breakpoints in your revenue distribution, and set bucket edges accordingly. Revisit every quarter — LTV curves shift with product changes.

---

## Step 3 — Structure Your Advantage+ App Campaigns

One clarification worth making explicit before you touch campaign structure: **Advantage+ Shopping Campaigns are an e-commerce product**. For app install campaigns, you want **Advantage+ App Campaigns**, which are purpose-built for mobile UA and optimized against SKAdNetwork signals.

These campaigns operate on Meta's aggregated signal layer — they do not consume raw SKAdNetwork postbacks directly. Your MMP sits in between, normalizing postback data and feeding modeled conversions back to Meta via the Conversions API.

A conflict-minimizing structure that works in production:

Avoid fragmented campaign structures with overlapping audiences. Consolidation gives Meta's algorithm more signal per campaign, which matters when SKAdNetwork postbacks are delayed by up to 35 days.

---

## Step 4 — Build the Unit Economics Model

Most growth teams have a spreadsheet that looks rigorous but is structurally broken. Here is the framework that holds up in production:

| Metric | Formula | Target (Example) |
|--------|---------|-----------------|
| CPI | Spend ÷ Installs | Benchmark against category |
| D7 ROAS | D7 Revenue ÷ Spend | ≥40% of D365 ROAS target |
| Payback Period | CAC ÷ (ARPU × Margin) | <180 days for venture-backed |
| Blended CAC | Total Spend ÷ Paid Installs | Must clear LTV:CAC ≥ 3:1 |

The D7/D365 ROAS ratio is your early warning system. A healthy subscription app sees D7 ROAS at roughly 35–45% of its eventual D365 ROAS. If you are scaling before this ratio is established from real cohort data, you are extrapolating on noise.

---

## Gotchas

**Treating all three postback windows identically.** Window 2 and 3 return coarse values only. If your MMP mapping does not account for this, you will misclassify high-LTV users as low signal and under-bid on your best cohorts.

**Confusing Advantage+ Shopping with Advantage+ App Campaigns.** They are different products optimized for different objectives. Using ASC for app installs means your campaign is optimizing against the wrong event type entirely.

**Setting coarse value thresholds from benchmarks instead of your own data.** An LTV threshold that works for a gaming app will be wrong for a productivity subscription. Use your 60-day cohort breakpoints.

**Accepting a >15% MMP-to-Meta discrepancy as normal.** That gap is a configuration problem, not a platform disagreement. Reconcile discrepancies weekly and treat anything above 15% as a bug to fix.

**Scaling before D7/D365 ROAS ratio is established.** D7 ROAS ÷ your historical D7/D365 ratio gives you a projected D365 ROAS on current cohorts. If that number does not clear your LTV:CAC target at current CPI, optimize creatives and conversion flow before increasing budget.

---

## Conclusion

Here is the pre-scale checklist that matters: audit your coarse value mapping against real LTV cohort breakpoints, designate your MMP as the single source of attribution truth and pipe it into Meta via Conversions API, and build your payback period model before touching budget.

If your D7 ROAS does not clear 40% of your target D365 ROAS, you are funding growth on borrowed time. Fix the measurement architecture first — the scale will follow.

For deeper reading: [SKAdNetwork 4.0 documentation](https://developer.apple.com/documentation/storekit/skadnetwork) and your MMP's SKAdNetwork integration guide are the two references worth bookmarking before you touch any of this configuration.