How to match App Store Connect UI for “Installations” & “First-time downloads” from Analytics Reports (dedupe/versioning guidance?)

Question

Created 3w

Replies 1

Boosts 3

Participants 2

We fetch the App Store Analytics – App Installs & Deletions (Daily) report via the Analytics Reports API and land each delivery into S3. The rows we ingest contain fields like Date, Event, Download Type, Counts, and Unique Devices. We’re trying to compute for example Installations and First-time downloads so our warehouse totals match the App Store Connect UI exactly, but our counts are consistently higher when we aggregate (with filter conditions being the same).

Questions:

(1) Official dedupe/versioning approach: What's the recommended approach to avoid double counting across API deliveries and to match the UI exactly? If later deliveries can revise past dates, what field(s) or process should we rely on to decide which records to keep for a given Date?

(2) Completeness window: For daily data, is the recommended approach to publish rolling values that may change for a few days, or waiting until dates are considered “complete” before reporting? Any best-practice guidance would be helpful.

Thanks!

Boost

Answer 1

layayu OP

1w

Hi, we are having the same problem here. I’m using the API to get "App Store Installations and Deletions (Standard)" report.

By reading the documentation, I understand that daily reports reach completeness approximately five days after the target date and that you should only consider valid the latest report that contains your target date.

However, what I don't know how to handle are the discrepancies between the API report: "App Store Installations and Deletions (Standard)", the "First Time Downloads" results, and the data from App Store Connect website Analytics > Usage > Installations.

I understand both are subject to only "opt-in" users.

However, in the results I get from the API I see lower numbers than the results from the App Store Connect UI. Which ones should I consider as valid?

0