How to Connect App Store Connect to an ASO Dashboard (API Key Setup, What You Get, What Apple Won't Give You)

Quick answer: App Store Connect lets you generate an API key (Users and Access, then Integrations, then Team Keys) that third-party tools can use to read your analytics and manage your listing. Paste the Issuer ID, Key ID and the .p8 file into SnapMonk's Store Insights and it pulls Apple's daily analytics reports: impressions, page views, downloads, redownloads, installs and deletions, sessions, crashes and proceeds, broken down by source, market and device. The first data lands 24 to 48 hours after you connect, then updates daily. Apple requires the Admin role on the key to switch analytics reports on and to create product page tests.

We built this because I was tired of the tab dance. Screenshots in one place, App Store Connect analytics in another, a spreadsheet in a third to line up "we changed the first frame on the 4th" with the downloads graph. Now the numbers sit next to the designs. Here's how to set it up and, more usefully, what to expect from Apple's side.

Step 1: create the API key in App Store Connect

1. Sign in to App Store Connect as the Account Holder or an Admin.
2. Go to Users and Access, then the Integrations tab, then Team Keys.
3. Click the plus button. Name the key something you'll recognize later ("SnapMonk" works), and choose the Admin role.
4. Download the .p8 file. Apple shows it exactly once. If you lose it, revoke the key and make a new one.
5. Note the Issuer ID at the top of the page and the Key ID next to your new key.

On the role: I'd normally tell you to give a third-party tool the least access possible, and for pure read-only analytics App Manager or Developer would be plenty. Apple, though, requires Admin to enable the analytics report request the first time for an app, and again to create Product Page Optimization tests. That's Apple's constraint, not ours. If you only want analytics on an app that already has reports enabled, a lower role will work for reading, and the connection screen will tell you what it couldn't do.

Step 2: paste it into Store Insights

Open Store Insights, click Connect App Store, and paste the Issuer ID, the Key ID, and drop the .p8. SnapMonk verifies the key against Apple immediately. A key that fails verification is discarded, nothing is stored.

When it works, you get the list of apps on the account. Pick the ones you want tracked.

What happens to your key

It's the question I'd ask, so here's the answer. The .p8 is encrypted at rest with AES-256-GCM using a server-side key that isn't in the database. It's decrypted only to sign a 15-minute token for a request to Apple, and it's never shown back to you or anyone at SnapMonk. Every call made with it is written to an audit log you can see. You can revoke it in SnapMonk or in App Store Connect at any time, and the App Store Connect side wins: revoke it there and ours stops working within the token lifetime.

Step 3: wait for Apple

This surprises everyone. Analytics reports are not instant. When you connect, SnapMonk asks Apple to start an ongoing report request for each app. Apple generates the first daily report 24 to 48 hours later, and each subsequent day's data is complete about two days after the day itself. So on Monday you're looking at Saturday.

Apple also restates earlier days sometimes in later reports. SnapMonk replaces a day's numbers with the newest version rather than merging, so a figure can shift slightly a day or two after it first appears. That's Apple correcting itself, not a bug.

What you'll see

Store Insights is built from Apple's Analytics Reports API, so it can only show what Apple publishes there. Concretely:

• Funnel. Impressions, product page views, downloads. Where people drop off, and which stage your screenshots are responsible for.
• Daily downloads, 30 days. First-time downloads stacked with redownloads, because those are different signals (a redownload spike often means a lapsed-user campaign, not a listing change).
• Sources. App Store search, browse, referrals, and the share of downloads each brings.
• Markets. Downloads by country, with the weak ones flagged so you can decide whether a localized screenshot set is worth it.
• Devices and usage. Installs, deletions, sessions, active devices, crashes.
• Proceeds. Sales and proceeds in USD where the purchases report is available.

Every figure is Apple's number for that day. There is no modeling, no estimation, and no sample data in the dashboard. If Apple hasn't published a day yet you see an empty state, not a placeholder.

What Apple's API will not give you

Worth being blunt so you don't go looking:

• Product Page Optimization results. The API creates and starts tests but does not return per-treatment conversion. Apple's verdict is only in App Store Connect. (Our split testing post explains how we work around it with your listing's before/after.)
• Keyword rankings. Apple has no rankings API. Rank tracking comes from the public search results, which is what the ASO report does.
• Real-time anything. Two-day lag, fixed by Apple.
• Competitor data. Your account, your apps, nothing else.

Controlling the listing from the same place

Once connected, two more things become possible:

Send a render to your next version. From the composer's done screen or any gallery item, "Send to App Store Connect" replaces the screenshots of that device and language on your next editable version. Your live page is untouched until you submit that version yourself. It's the upload flow without the drag and drop.

Run a product page test. Experiments compares a render with your live page panel by panel and sends it to Apple as a PPO treatment. Covered in depth in the ASO split testing post.

Who this is for

If you check App Store Connect daily and have it memorized, you don't need this. It's for the developer who changes screenshots twice a year and never quite knows if it helped, because the change date and the analytics live in different tools. Put them side by side and the question answers itself.

FAQ

How do I create an App Store Connect API key? In App Store Connect go to Users and Access, then Integrations, then Team Keys, and click the plus button. Name the key, choose a role, and download the .p8 file once. The Issuer ID is shown at the top of the page and the Key ID next to the key. You'll need all three to connect a tool.

What role does an App Store Connect API key need for analytics? Reading analytics works with App Manager or higher once reports are enabled, but Apple requires the Admin role to enable the analytics report request for an app the first time, and to create Product Page Optimization tests. SnapMonk asks for Admin for that reason and tells you what it couldn't enable if a lower role is used.

How long until App Store Connect analytics data appears? Apple generates the first daily analytics report 24 to 48 hours after the report request is created, and each day's data is complete about two days after that day. Expect to see your first numbers the day after tomorrow, then a rolling two-day lag.

Can a third-party tool see my Product Page Optimization results? No. Apple's App Store Connect API can create and start product page tests but does not expose per-treatment conversion or the winner. Those results are only visible in App Store Connect. Tools can show your listing's overall conversion before and after a test from the analytics reports.

Is it safe to give a tool my App Store Connect API key? It depends on the tool. Check that the key is encrypted at rest, decrypted only to sign short-lived tokens, never displayed back, logged per request, and revocable. SnapMonk does all of those, and revoking the key in App Store Connect always overrides it.

Can I upload App Store screenshots from a tool instead of App Store Connect? Yes. The App Store Connect API supports replacing screenshot sets on an editable version. SnapMonk's Send to App Store Connect puts a render on your next version for a device and language; it goes live only when you submit that version.

Related reading

• Store Insights: connect and see the funnel
• ASO split testing with your screenshots: the test loop that uses this connection
• How to upload screenshots to App Store Connect: the manual route
• App Store conversion rate optimization: what to do with the funnel once you can see it
• The ASO checklist: the wider listing audit