Keep App Store Connect. Erdi pulls the sales reports Apple already generates and plots downloads, updates and proceeds under your releases.
Downloads, updates and proceeds as daily series from Apple's sales reports. Apple's reports lag by two days; Erdi sets that lag on the series so the chart hatches the incomplete edge instead of drawing a zero. The first Analytics report can take up to 48 hours to appear after you create the key — nothing shows before then.
Two Apple paths, two windows. Sales reports (totals for downloads, updates, proceeds) go back about ninety days on the first pull. The Analytics breakdown — downloads by source: search, browse, app referrer, web referrer, other — only covers days from when you connect. Apple keeps only a few recent Analytics instances per app; older source days are not available to pull. A short source chart after connect is expected, not a failed sync.
An App Store Connect API key (.p8), issuer ID, key ID, vendor number and the app's Apple ID. The private key is stored encrypted. Erdi signs requests with ES256. This is a pull, not a webhook from Apple.
The downloads here and the source breakdown in Analytics are two different counts, and neither is the same as the installs Apple Ads reports. Apple Ads attributes installs to a tap on your ad, Analytics counts downloads by how someone found the app, and Sales counts download totals on its own basis and its own delay.
Subtracting one from another does not give you organic installs. The difference between any two of them is a definition gap, not a number about your app. Erdi shows each series as its source reports it and does not combine them.
Ratings, crashes, TestFlight, and customer reviews. Those stay in App Store Connect. In-app purchases that you already send through RevenueCat should not be pulled twice.
Set it up under Settings → Sources in your project.