App Store Downloads API: In-app Events hugely mismatching console

Question

Tetleysteabags OP

Created 1w

Replies 1

Boosts 0

Participants 1

I am using the API to fetch the following report: asc_api_report_commerce_app_downloads_detailed

The reason I am using the detailed version is that I want to breakdown downloads by in-app event names.

Here are the issues I'm facing:

When comparing the detailed to the standard report, for specific date ranges and markets (comparing apples to apples), the numbers are slightly off - usually by around 1-2k. I can get around this, since I can use the standard report for most of my reporting.
The second, and main issue, is when I try to use the detailed report to see how different IAEs are performing. The data discrepancies here are huge, and don't make any sense to me.

For example, when I check a specific IAE (called Blanked), I can see dates in the console which are not showing up in the ASC API. These dates do exist in the broader dataset, they just don't exist for this specific IAE.

Am I looking at this wrong? Do I need to pull the data differently? Has anyone else found this issue?

ASC API Downloads vs Console Downloads - Sheet1.csv

Boost

Answer 1

Tetleysteabags OP

1d

I got this reply from Apple help.. what might this mean? I am little confused why I should use Transporter to help me resolve my issue?

From what I understand, Transporter is used for submitting content to the iTunes Store, App Store, and iBooks Store. But my problem is that the data I see on App Store Connect console does not match the results in my API call?

Thank you for providing additional information.

After conducting further research, I recommend referring to the following two comprehensive guides to assist you in addressing the API data discrepancies. Please thoroughly review the articles to identify the root cause of the issue.

Transporter for macOS Help Transporter User Guide If you still need assistance with the API, please respond to this email and reference Case Number 102483201751 in your response.

0