Why App Store Connect's latest days keep changing
Apple's analytics reports are generated daily, and each new one restates the days before it. A day you read on Monday can read differently on Tuesday and differently again on Wednesday, and none of those readings is an error — the later one replaces the earlier one. The figure to trust is the one from the report with the most recent processing date. Adding the reports together instead of replacing is the common mistake, and it can inflate traffic several times over.
What Apple actually sends
Analytics reports arrive as a series of daily instances. Each instance covers a window that overlaps the one before it:
| Report family | Days each instance restates | What that means |
|---|---|---|
| App Downloads | the 2 days before the processing date | A day is revised twice after you first see it |
| App Store Discovery and Engagement | the 3 days before the processing date | A day is revised three times after you first see it |
So a single calendar day appears in several instances, with a different total each time. On an account we tested this against, one day's downloads were restated twice — three readings across three instances, each a little higher than the last, before the day settled. The day did not gain downloads overnight; Apple finished counting it.
The mistake that inflates your numbers
If you collect every instance and add up every row for that day, you count the day three times over — once per reading, each one a full total rather than a top-up. Done across a whole reporting window on the account we tested, that inflated traffic by two to three times.
The rule is replace, don't add: for each app, report family and data date, keep only the value from the instance with the latest processing date. Apple documents this behaviour under Data Completeness and Corrections.
Which days are still moving
| Age of the day | Downloads | Discovery and Engagement |
|---|---|---|
| Processing date −1 | still being revised | still being revised |
| −2 | still being revised | still being revised |
| −3 | settled | still being revised |
| −4 and older | settled | settled |
A day with no rows in a report that covered it is a genuine zero. A day no report has covered yet is missing, which is a different thing, and counting it as zero is what produces a fake cliff at the end of a chart.
One more thing that moves a day: time zones
Analytics days are in UTC. Sales and Trends days are in Pacific Time. The same calendar date therefore starts and ends at different hours depending on which report you are reading, so a download and the proceeds from it can land on different dates. Neither report is wrong; they are measuring different days.
What this means in practice
- Don't compare a figure you wrote down three days ago against today's reading of the same day and conclude something broke.
- Don't sum report instances.
- Treat the newest two or three days as provisional in any chart you show anyone.
Next: first-time downloads, units and total downloads, and why API impressions read lower than App Store Connect.
AppStato keeps only the latest instance per day, labels the newest days “Latest days may change”, and names a day Apple has not reported as missing rather than drawing it as zero. See AppStato.