Analytics
Your App Store impressions spiked. Was it a feature?
A step change in App Store Browse impressions is the fingerprint of being featured — but Browse is a bucket, and charts, categories and In-App Events land in it too. Here is how to tell the shapes apart, how to find the country, and why the answer usually arrives a day after it would have been useful.
What Browse actually contains
App Store Connect splits acquisition by source. Apple's definition of the Browse source is broad on purpose:
“Users viewed your app or tapped to download it while browsing the App Store (for example, in the Today, Games, or Apps sections).”
So Browse is everything that is discovery but not search: editorial shelves, Top Charts, category pages, In-App Events, and the similar-app modules on other apps' product pages. Search is its counterpart, and includes Apple Search Ads results. App Referrer and Web Referrer are the two that tell you somebody sent traffic in from outside.
That means the first useful question is not “did Browse rise?” but “which source rose, and in what shape?”
Reading the shape
| What happened | Source | Shape | Geography |
|---|---|---|---|
| Editorial feature | Browse | A cliff. Impressions multiply overnight, hold while the shelf holds, then drop just as sharply | One country, or a handful — rarely all of them |
| Today tab / App of the Day | Browse | The steepest cliff of all, usually a single day wide | Usually one storefront |
| Entering a Top Chart | Browse | A ramp, not a cliff, and it sustains while the position holds | Per country, and it tracks your rank |
| In-App Event | Browse | Bounded by the event's own dates | Wherever the event is published |
| Press or a viral post | Web Referrer, then Search | Sharp, and it moves branded search terms with it | Follows the audience of whoever posted |
| ASO or keyword change | Search | A gradual drift over days, not a jump | Broad |
The tell for a feature is the combination: Browse only, overnight, and geographically concentrated.
Two ratios worth checking
Impressions versus product page views. A shelf puts your icon in front of a lot of people who scroll past it. Featuring spikes tend to move impressions far more than they move page views, so conversion rate drops during a feature even though downloads rise. That is normal, and a good reason not to panic at the conversion chart.
Product page views versus downloads. If both rose in proportion, the traffic was well-matched to your app — the mark of a shelf whose theme actually fits. If page views rose and downloads did not, you were on a shelf that flattered you into the wrong audience.
Finding the country
Break impressions down by territory and look for the ones that moved. Featuring is per-storefront, so this narrows it fast — a 40× jump in Brazil and flat everywhere else is not ambiguous.
What the territory table cannot give you is the placement: which shelf, what it was called, which slot you sat in, and which apps were beside you. None of that is in App Store Connect, in any report, ever.
The problem with all of this
App Store Connect analytics are reported daily, not live. A given day's figures settle roughly a day later — which means the sequence goes: the shelf goes up, your app has its best day of the year, the numbers arrive the next day, you work out which country, you open that storefront, and the shelf has rotated.
Analytics tell you a feature happened. They cannot tell you one is happening.
You are left with the number but not the screenshot, the country but not the shelf name, and no idea which apps were beside you. For a placement you will never get back, that is a thin souvenir.
Catching it on the day instead
Apple sends a notification for select placements on the Today tab, which covers the marquee slots and nothing else. For every other shelf, and every other country, there is no alert at all — which is the gap StoreGlance was built to close.
Add your apps once, and your competitors' too. StoreGlance pushes you on the day a tracked app lands on a shelf, in any of the 171 storefronts, and tells you the shelf name, the country, the slot and the apps either side of you. Then the analytics, when they arrive the next day, are just confirmation of something you already screenshotted.
Know before the spike shows up
Get the push on the day, with the shelf and the country attached — instead of a number you have to reverse-engineer a day later.
See what StoreGlance doesFor the fuller picture of what Apple does and does not tell you, see how to know when your app is featured on the App Store.
Frequently asked
What is App Store Browse?
An acquisition source in App Store Connect analytics: people who viewed or downloaded your app while browsing the store — Today, Games and Apps sections, charts, categories and In-App Events. Everything that is discovery but not search.
Does a Browse spike mean I was featured?
Not by itself. A feature usually looks like an overnight cliff concentrated in one or a few countries; a chart entry ramps and sustains. To be certain which shelf it was, you need something watching the storefronts — see StoreGlance.
Why did my conversion rate drop during a feature?
Because a shelf generates impressions from people scrolling past. Impressions rise faster than product page views, so the ratio falls even while downloads climb. It is expected, not a problem with your page.
How quickly do App Store Connect analytics update?
Daily, not live — a day's numbers settle roughly a day later. Good enough to measure a feature, too slow to catch one.
Dylan · Ludyem
I build small iOS apps and the tools I needed while shipping them. StoreGlance exists because a Browse spike told me something had happened, and by the time I worked out where, the shelf was gone. Now it tells me on the day.
Know before the analytics do
All 171 storefronts, yours and your competitors', with a push on the day your app lands on a shelf — shelf name, country and slot included.
Get StoreGlance