SKAdNetwork 5: what changed and what to ship this quarter

SKAdNetwork 5 has been generally available long enough that there's no excuse left for staying on SKAN 4. The headline changes are re-engagement attribution, coarse conversion values across three postback windows, and a richer crowd-anonymity tier. The migration is mostly mechanical — here's the checklist.

Update your conversion value schema

SKAN 5 keeps the 64-bit fine value and the three coarse buckets, but the postback windows have shifted. Re-map your event values so 'trial started' lands in the right window, and audit the crowd-anonymity tier each event is likely to receive.

OpenTrack.shared?.updateConversionValue(
  fineValue: 42,
  coarseValue: .medium,
  window: .postback2 // 2-7 days
)

Handle re-engagement postbacks

Re-engagement is the most underused SKAN 5 feature we see in audits. If your acquisition is mature and your reactivation budget is meaningful, you should be lighting this up — and you should be tagging postbacks accordingly in your warehouse.

Don't trust the deck — trust the postback

Ad networks publish their SKAN reporting in summary form, often with proprietary smoothing. Always ingest the raw postback yourself, store it indefinitely, and reconcile against the network's reports. If you're using Link Trail, the postback endpoint is one route handler — no excuse not to.