I'm following the flow to get my reports data: get the requests (ONGOING or ONE_TIME_SNAPSHOT) for my app (https://api.appstoreconnect.apple.com/v1/apps/{{appID}}/analyticsReportRequests?filter%5BaccessType%5D=ONGOING) get the report (App Sessions Standard, for example) (https://api.appstoreconnect.apple.com/v1/analyticsReportRequests/{{requestID}}/reports?filter%5Bname%5D={{report}}) get the daily instances of the ONGOING request (https://api.appstoreconnect.apple.com/v1/analyticsReports/{{reportID}}/instances?filter%5Bgranularity%5D=DAILY) get the segments for the selected instance (https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/{{instanceID}}/segments) This flow used to work fine, but recently I noticed that the earliest instances (mostly of processing date 2025-02-24 until 2025-02-27 return an error when I'm trying to get the instance segments usint the URL https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/{{instanceID}}/segments. The error is the following: "title": "The specified resource does not exist", "detail": "There is no resource of type 'analyticsReportInstances' with id '32f8b58b-07da-4d50-899f-34a7c0488927'" Even when the list of instances return me such object with ID when consulting the resource https://api.appstoreconnect.apple.com/v1/analyticsReports/{{reportID}}/instances?filter%5Bgranularity%5D=DAILY: { "data": [ { "type": "analyticsReportInstances", "id": "32f8b58b-07da-4d50-899f-34a7c0488927", "attributes": { "granularity": "DAILY", "processingDate": "2025-02-25" }, "relationships": { "segments": { "links": { "self": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927/relationships/segments", "related": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927/segments" } } }, "links": { "self": "https://api.appstoreconnect.apple.com/v1/analyticsReportInstances/32f8b58b-07da-4d50-899f-34a7c0488927" } }, And as for the days that I can retrieve data, there seems to be happening an Internal Server Error with frequency, but retrying the request seems to solve it.

We started a Product Page Optimization test on Apr 9, and it seems to be running fine but we still can't see the Analytics, even after all this time. It shows this error: "App Analytics is Temporarily Unavailable. Try again later. If the problem persists, contact us.". This is happening with two of our apps at the moment. We have already done tests in the past and this never happened before. This is the bug report number: FB17217419 We would appreciate if someone could take a look and let us know what is happening. Thanks!

Hi everyone, I’m new here. I’m working with the App Store Connect (ASC) Analytics API and I have some questions about how to retrieve historical data for downloads and in-app purchases. I’ve created two types of reports: 1. ONGOING: Retrieves current and recent data. 2. ONE_TIME_SNAPSHOT: Supposedly retrieves historical data. I am specifically interested in the Detailed versions: • App Store Downloads Detailed • App Store Purchases Detailed What's my problem? 1. The ONGOING report brings instances with data from the last few days, which seems correct for App Downloads. But not with Purchases, it brings just a few random days and I'm not sure about the granularity. 2. The ONE_TIME_SNAPSHOT report, however, retrieves instances with data from specific days, but the selection of these days appears to be random. I can’t figure out the criteria behind it. Does anyone know what the selection criteria are for the days that appear in the ONE_TIME_SNAPSHOT report? Is it possible to configure the date range for this type of report? Why are some historical dates available while others are not? Is there a way to ensure that the ONE_TIME_SNAPSHOT report brings data from all days within a specified range? Any advice or insights would be greatly appreciated! Thanks in advance!

I use App Store Connect for over 3 years but since about May 9 I noticed two things: the sales of my apps reported by App Store Connect/Trends are down approx. 80% (this could be a coincidence but I hope the data is not up-to-date) an update of one of my apps seems to be stuck in "Waiting for Review" for a couple of days now (in the weeks/months before the review process would be very quick: done in a couple of days). Anyone else having these/similar problems lately?

I'm looking to automate the download of the Apple Arcade Bonus Payout Report accessible via the App Store Connect "Sales and Trends Reports" page. I've been looking at the documentation for the App Store Connect API here: https://developer.apple.com/documentation/appstoreconnectapi/get-v1-salesreports This page makes it seem as though there is no API connection for the Apple Arcade Bonus Payout Report - is this the case? If so, does anyone have any good solutions for automating downloads of this data source.

Hi Guys, I tried using ChatGPT for help with this but it keeps hallucinations incorrect instructions so hoping you can help- using the App Store Connect data on things like retention, what is the best way to see: • Since the launch of my app, % of users who drop on day 2 since installing the app, % of users who drop on day 3 since installing the app, etc. • Of users who downloaded the app in May 2025, how many have used it in in October 2025 • Of users who downloaded the app in June 2025, how many have used it in in October 2025 Note also that I don’t have any other BI tools integrated to the app. The only data available to me is what comes in App Store Connect already. Thanks!

Hi! Earlier, I created a report using the appstore api, and it contained WEEKLY and HOURLY data. However, I have now created a report for a new app, and after almost a month, it does not have HOURLY granularity. How can I obtain it?

Regarding the “App Store Downloads” Analytics Report, I have submitted a report generation request with accessType: ONE_TIME_SNAPSHOT. Reference: https://developer.apple.com/documentation/analytics-reports/app-download I would like to confirm the scope of the Campaign data included in the report generated by this request. In the App Store Connect UI, I understand that there is an upper limit of 200 Campaign entries displayed. For the report output, however, could you please confirm whether it includes all Campaigns measured on the App Store Connect side? Or is there also any upper limit on the number of Campaign records included in the report itself?

I was using the Download Sales and Trends Reports API (GET https://api.appstoreconnect.apple.com/v1/salesReports), but at some point, the results started not displaying properly. (The reason for this is that all the +sales values ​​aren't showing up in the CSV file.) Below, I'll show you how to use the API in Python with a screenshot. (***** elements are hidden.) If anyone knows why, please let me know.

Logging out: The platform logs people out super quickly (e.g. within like a couple of hours), it would be great to be able to stay logged in within the same day and not have to log back in every time. Latency: In general, it can be really slow to load, and sometimes pages fully load without anything on them. The team then has to refresh the page for e.g. dashboards to be shown Submission of PPO & In-app events: PPO tests and in-app events can only be submitted on the latest version, which means that you need to wait for a period when we're not having a new version of the app reviewed. If this is regularly the case, it's difficult to submit. Sometimes you then submit e.g. an in-app event, but it takes a while and the review is removed in favour of an app update. Solution: The whole thing should follow a similar process to CPPs whereby you don't need to upload to the latest version, or you should be able to select which app version you're uploading to and be able to select the latest. Rather than having to delete and build again every time. Pricing updates: The amount of time that it takes to change pricing is insane and results in a reluctance to make price changes. There are a number of ways that this could be improved: a) Don't only allow us to select prices from a drop down list. This process adds like 3 extra clicks to every single price change. Just make the prices editable (e.g you can type) in a list, Google Play Console does this very well. b) For promotions, allow us to set e.g. "20% off the default price" and then when we make pricing updates to the default price the promotional price will update automatically. Instead currently we have to go in and manually calculate 20% off every single price based on the new price and update it ourselves, it's crazy. Reporting on promotions: Currently, there is no ability to see a time series of conversions with specific promotions with configurable date ranges, you can just see the total redemptions up to a certain date. This means we're manually having to look at the number of redemptions up to a certain date and then if we wanted to see a daily breakdown we'd need to look at ever date in isolation and calculate the increase in number of redemptions.

I am planning to build a service that automatically pulls Apple reports and stores them in my database. I was able to successfully retrieve the APP_USAGE report from the Analytics API. It initially generated daily reports for a couple of days, but then the daily report generation stopped. The weekly and monthly reports continue to generate normally. I also checked the readReportRequest response, and the StoppedDueToInactivity field is returned as false. And also, when I compared the monthly reports between the API and the web console, the data does not match. Does anyone have a solution to this issue, or is there a recommended or updated approach for handling this?

I am planning to build a service that automatically pulls Apple reports and stores them in my database. I was able to successfully retrieve the APP_USAGE report from the Analytics API; however, while it initially generated daily reports for a couple of days, the daily report generation subsequently stopped. The weekly and monthly reports are generated normally. I also checked the readReportRequest response, and the StoppedDueToInactivity field is returned as false. And also, when I compared the monthly reports between the API and the web console, the data does not match. Does anyone have a solution to this issue, or is there a recommended or updated approach for handling this?

We have changed app icon a while ago, it displayed correctly on distribution page and on other pages - with an exception of analytics - https://appstoreconnect.apple.com/analytics No matter what time range is selected it still displays old icon. Can I make something with it? It's been more then a year and it's definitely not a cache issue.

Hi everyone, We’re experiencing an issue with App Store Connect → Sales & Trends (Sales) → Last 24 Hours (hourly) reporting, specifically for In-App Purchase (IAP) sales. On January 30–31, 2026, when checking Last 24 Hours sales data, we consistently see IAP sales drop to 0 starting around 18:00 UTC, as if no purchases happened after that time. However, we can confirm that IAP transactions did occur during the same time window using other validation sources (e.g., server-side logs / analytics). In App Store Connect, those hours still show 0. I did a quick search and found reports of similar behavior affecting downloads/units for some teams, but in our case downloads/units look normal in Last 24 Hours. The problem appears to be only in the IAP sales portion. Questions: Is anyone else seeing hourly gaps / 0 values for IAP around Jan 30–31, 2026 (or today)? Is this a known Sales & Trends reporting delay that eventually backfills, or an ongoing issue? If you’ve seen this before, how long did it take to normalize/backfill, and did any specific check/filter help?

Starting on 1/30/2026, we started getting an error when using Reporter to retrieve a Subscriber/Sales report from App Store Connect. Our script was working daily perfectly for a long time before this. It normally pulls the report from 1 day prior. We have been troubleshooting and cannot seem to find any issues on our end. Is this a universal issue for other users too?

The Crashes report in App Store Connect Analytics for my app is showing unexpectedly high crash rates, well over 2,000 per day (among roughly 150k active users per day). But I'm having trouble correlating this with other sources of stability reports: Firebase Crashlytics shows about 100 crashes per day over the last 90 days In the Xcode organizer, under “On-Screen Terminations” I see “Insufficient usage data available” which I take to mean very low numbers In the Xcode organizer, under "Background Terminations" it shows a little over 2 terminations per day, and well over 95% of those are "System Pressure" In the actual crash reports section of the Organizer, I have a little over 6,000 devices in the last two weeks encountering an issue that I think is 0xdead10cc, which I think would show up under Background Terminations as File Lock. As a side note, triaging these 0xdead10cc issues in the Organizer is a pain - see FB12292887. My main question here is what is included in App Store Connect's crash numbers. Do they include background terminations, especially "System Pressure"? Is there a way for me to get more information on the distribution of termination / crash types in those numbers? My understanding of System Pressure terminations is that it's when the system has to kill my app in the background to free up resources for other things, especially an app in the foreground, and it's not a "crash" properly speaking, although I might be able to make them less frequent if I reduce my memory usage. Am I incorrect in this? Notably, "System Pressure" is conspicuously not defined in the "Reducing Terminations in Your App" documentation under "Background termination reasons". https://developer.apple.com/documentation/xcode/reduce-terminations-in-your-app

I am not seeing any sales data in the app store since 3/16/2026 but there are units sold and proceeds displayed. Anyone from Apple to give an update? Any other developers seeing the same problem?

We are observing a discrepancy in crash data between the App Store Connect UI and the App Analytics APIs for our iOS application. For example: On March 10, App Store Connect shows approximately 2,443 crashes (average ~2K/day). However, in our analytics database (fetched via App Analytics APIs), we are seeing 10,000+ crashes for the same date. APIs Used (IDs masked): /v1/apps/{app_id}/analyticsReportRequests /v1/analyticsReportRequests/{request_id}/reports?filter[category]=APP_USAGE /v1/analyticsReports/{report_id}/instances?filter[processingDate]=YYYY-MM-DD&filter[granularity]=DAILY /v1/analyticsReportInstances/{instance_id}/segments Clarifications Required: What could be the reason for the significant difference in crash counts between App Store Connect UI and Analytics API Are there differences in how crashes are counted in: UI metrics vs raw analytics reports? Deduplication, session-level vs event-level aggregation? Is there any known aggregation rule, or filtering applied in the UI that is not reflected in the API data? Which source should be considered the accurate/authoritative count for reporting purposes? Any clarification or guidance on this discrepancy would be greatly appreciated.

Hi, I am diving in App Store Connect analytics / sales and trends and I can't find an accurate way to measure / calculate lifetime value (LTV) of users based on different cohorts? I also can't find accurate retention data as there is no data populated in the retention graph. It seems that retention is only based on users that have "opted in." This is the message I see: "Installations and Active Devices only include data from users who have agreed to share their diagnostics and usage information with app developers. In the last day, 27% of all users that installed "App Name" agreed to share their data." Am I missing something? Is there a way I can calculate / see user LTV and/or all user retention? Or is there a third party tool that can provide / calculate accurate LTV / retention?

When redeeming a custom offer code, I'm not able to see the actual offer code ID in the Subscriber report - only the subscription offer name is present. I'm going off of the documentation for the Promotional Offer ID column: A code that you create for customers to enter and redeem the subscription offer. https://developer.apple.com/help/app-store-connect/reference/subscriber-report Is the documentation wrong? How are we supposed to measure the performance of our offer codes beyond the initial redemption? For example, with the offer name I can see how my "Holiday Promos" offer is doing but can't see the actual performance of "BLACKFRIDAY30" vs "MOTHERSDAY30".