Apple is phasing out the Sales and Trends dashboards and reports in App Store Connect, folding the data into the newer Analytics surface over the course of 2026 and 2027. Subscription dashboards go first, with the rest of Sales and Trends following in stages until the legacy surface is removed entirely. Apple frames this as consolidation — one place for acquisition, engagement, monetisation, retention, and quality data instead of two overlapping systems — but for any team with an export pipeline, revenue dashboard, or finance report built against the old Sales and Trends Reports API, it’s a migration deadline with a real cutover date attached.
The risk isn’t the UI change; it’s the same failure mode every legacy-API retirement produces. Sales and Trends reports have existed since the App Store itself, long enough that scheduled exports, warehouse loaders, and finance reconciliation scripts get built once and then quietly rely on that exact report shape for years. When Apple removes a Sales and Trends report and the equivalent data now lives only in the Analytics Reports API — with different field names, different granularity, and a different auth flow in some cases — anything still pointed at the old endpoint doesn’t degrade gracefully, it just stops returning what finance expects.
Data Points to Track
- Inventory of every scheduled export or script calling Sales and Trends reports, especially subscription reports, which are first in line for removal
- Field-level mapping between old Sales and Trends columns and their Analytics Reports API equivalents, since names and granularity don’t always match one-to-one
- Data freshness and latency differences between the legacy reports and the new Analytics data, which matters if finance reconciliation depends on same-day figures
- Auth and access-scope requirements for the Analytics Reports API, since API key or App Store Connect role permissions may need updating separately from the report migration itself
- Historical data continuity, confirming whether pre-migration history remains queryable through Analytics or needs to be archived from Sales and Trends before it disappears
Setup Steps
- Audit every consumer of Sales and Trends data — BI tools, warehouse ETL jobs, finance spreadsheets, third-party MMPs — before Apple removes the first dashboard.
- Cross-reference Apple’s phased deprecation schedule against what your team actually depends on, prioritising subscription reports since those move first.
- Rebuild exports against the Analytics Reports API in parallel with the legacy reports, running both side by side until the numbers reconcile.
- Archive historical Sales and Trends exports you may need for year-over-year comparisons before that data is only available through the new surface, if at all.
- Set a monitoring alert on the old endpoints so a silent removal shows up as a pipeline failure immediately rather than a quiet gap discovered at month-end close.
Actionable Insights
Treat this the same way you’d treat any hard-cutover API retirement: the organisations that get hurt aren’t the ones without a migration plan, they’re the ones who don’t know every place the old report is still being consumed. A short audit now — matching every scheduled job against Apple’s phased removal dates — turns a potential finance-reporting gap into a planned, low-drama migration instead of a surprise when a subscription dashboard someone forgot about goes dark.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert