What's in Apple's 100+ metric update to App Store Connect Analytics?

Apple's App Store Connect Analytics just got its largest overhaul since the dashboard launched, adding more than 100 new metrics for developers to track, according to The Mac Observer. We read the report the morning it posted, pulled up our own dashboard, and started guessing which numbers we'd finally stop estimating by hand.

We've shipped apps long enough to know App Store Connect Analytics has always been useful but incomplete. It gives us impressions, product page views, conversion rate, sessions, and crash counts, but the gaps between those categories are where the real questions live — why a spike in impressions didn't turn into installs, or why retention dipped the same week we pushed an update. A jump of more than a hundred metrics in one pass reads less like a patch and more like a rebuild of what the tool is meant to answer.

What did Apple change in App Store Connect Analytics?

The Mac Observer's report frames this as the biggest update the analytics dashboard has seen, built around adding over 100 new metrics on top of the reporting developers already rely on. The piece doesn't list every new field, so we're not going to guess at specifics that weren't in it. What we can say is that the scale of the change signals Apple wants App Store Connect to answer more of the "why" behind the numbers, not just the "what."

Why does a hundred-metric expansion matter for small teams?

Small studios don't have a data science team translating exports into decisions. We are the data team, usually squeezed between a support queue and a release checklist. Every metric Apple adds natively is one we don't have to approximate with a third-party SDK, a spreadsheet, or a guess based on App Store reviews. Fewer tools in the pipeline means fewer places for numbers to drift apart from each other, and fewer subscriptions we have to justify at renewal time.

Where do these new numbers show up in our workflow?

Right now, nowhere yet — the rollout is just starting, and the new fields haven't landed in our own account. When they do, the first place we'll check is anything tied to the product page: how visitors move from a screenshot to a tap to an install, broken into steps instead of a single conversion rate. The second is crash and performance data close enough to real time that we can tie a bad release to a specific group of users instead of waiting for review complaints to tell us something broke. Reports that arrive a day late are still better than none, but a studio our size lives or dies on catching problems inside the first few hours.

Which existing terms are worth knowing before the dashboard changes?

A few terms already built into App Store Connect are worth having straight before anything new gets layered on top of them:

• Impressions — how many times your app's icon appeared in search results or a browse listing.
• Product page views — how many people actually opened the page, whether or not they installed.
• Conversion rate — the share of product page views that turned into a download.
• Sessions — how many times the app was opened after install.
• Crashes — reported failures, usually broken out by device and OS version.

These categories aren't new, but they appear to be the baseline Apple is building on, which makes it easier to tell which of the 100+ additions are genuinely new ground versus a finer cut of something that already existed.

How are we watching the rollout from here?

We're not changing our release process off a headline. What we're doing is checking our own dashboard for new sections and treating anything that shows up as provisional until we've watched it track against a release we understand well — a small update, not a major one, so we can isolate what the new figures are actually measuring. If they hold steady over a couple of cycles, we'll fold them into how we decide what ships next. Until then, the Mac Observer account is the clearest description of the scope of the change we've seen, and we'd rather confirm it against our own numbers than repeat figures we haven't verified ourselves.