Home / Symptoms / iOS SKAN

Second and third SKAN postbacks arrive days late

Late second and third SKAN postbacks are normal, because Apple adds 24 to 144 hours after each window ends. See a timeline and how to plan reporting around it.

SymptomSKAN 4 second and third postbacks show up several days after their conversion windows end.
Most likely causeApple adds a random delay of 24 to 144 hours after the second and third windows close.
First checkCompare each postback's received date with the end of its conversion window.

Short answer: this is expected. Apple adds a random delay of 24 to 48 hours after the first window and 24 to 144 hours after the second and third. Locking a window early starts the delay sooner, but you cannot remove it.

Why later SKAN postbacks are slow

Random delay: a deliberate wait Apple adds before sending each SKAN postback so that its timing cannot be linked to a specific person's install.

The windows themselves are long, too. The second covers days 3 to 7 after first launch and the third days 8 to 35, so a third postback can arrive weeks after install.

When should I expect each postback?

Expect the first two to four days after install, the second around 8 to 13 days, and the third around 36 to 41 days, if no window is locked early.

Likely causes

  • Apple's random delay. Apple documents 24 to 48 hours for the first postback and 24 to 144 hours for the second and third.
  • Long windows. Each delay only starts when the window ends, at day 2, day 7 and day 35.
  • Windows not locked. If the value is final early but the window is not locked, the postback waits for the full window.

How to confirm it

  1. List postbacks by postback sequence and received date.
  2. Work out when each window ended for the install cohort.
  3. Check that the gap falls within Apple's documented range.
  4. Check your code for lockWindow calls.

How to fix it

  1. Accept the delay and report SKAN cohorts by install week, not received date.
  2. Lock a window early with lockWindow when the value for that window is final.
  3. Read early optimisation signals from the first postback and use later postbacks for longer-term quality.
  4. Label dashboards so that recent cohorts are clearly incomplete.
PostbackWindowDelay after window endsTypical arrival after first launch
FirstDays 0 to 224 to 48 hoursAbout days 3 to 4
SecondDays 3 to 724 to 144 hoursAbout days 8 to 13
ThirdDays 8 to 3524 to 144 hoursAbout days 36 to 41

These ranges assume no early lock. AdAttributionKit uses the same three windows and delays, according to Apple.

The SKAN 4 postbacks guide covers windows and locking in more detail. If the later postbacks never arrive, see only the first SKAN postback, and for general reporting lag see attribution data delayed. The SKAN troubleshooter helps if the postbacks are empty.

FAQ

Common questions

Why does the third SKAN postback take so long?

Its window runs to day 35 after first launch, and Apple then waits 24 to 144 hours before sending it. That puts it about five to six weeks after install.

Can lockWindow make postbacks faster?

It can make them earlier, because the delay starts when you lock the window rather than when the window ends. The random delay itself still applies.

Does AdAttributionKit have the same delays?

Yes. Apple's documentation says AdAttributionKit uses the same three windows and the same delays as SKAN 4.

How should I report SKAN results with these delays?

Group results by install cohort and mark cohorts as incomplete until all their postbacks are due. Avoid judging a campaign's later-window quality in its first month.

What is mobile attribution?

Mobile attribution is the process of crediting each app install or in-app event to the ad, link or channel that drove it. A mobile measurement partner (MMP) does this across all your channels so each install is counted once.

Why do ad networks report more installs than my MMP?

Each network counts every install it touched within its own windows, including views, while an MMP gives each install to a single source. Adding the networks' numbers together therefore overstates real installs.