How to Read App Store Connect Acquisition

A podcast app can look “up” on impressions and flat on installs, and the team will redesign the whole page because the biggest number moved. That number includes people who only saw the icon in a list. Product page views are the people who opened the show notes. Unique impressions are the devices, so a fan who scrolls past you four times is not four strangers. If you treat those three lines as one line, you will edit the wrong pixels.

Definitions are on Apple’s metric definitions . Source types, including App Store search versus App Store browse, are on the acquisition page . The rate those inputs feed is explained in App Store conversion rate. The page work itself is in product page optimization.

Three counts, one podcast, one day

Apply the definitions to a single device. The podcast app appears in search and stays visible for more than one second. That is an impression. The person taps through and the product page loads. Impressions include product page views, so the page is a second impression, and it is one product page view. Unique device impressions count the device, so that day is still one unique impression. Two impressions, one product page view, one unique impression. If they never tap, you have one impression, one unique impression, and zero page views.

This is a reading of the published definitions, not a dump of the podcast app’s real analytics. Do not multiply it into a “typical ratio.” It exists so the columns stop feeling interchangeable. StoreKit loads count too: if another app presents your product page, Apple includes that in product page views and in impressions. A spike that does not match your search terms might be a referral, not a ranking jump.

What each column is allowed to tell you

Impressions can rise while page views stay flat, because a search row counts. Conversion uses unique device impressions, so repeat views on one phone do not multiply the denominator.

Unique impressions on the acquisition overview are devices for a given day, week, or month. A weekly unique is not seven daily uniques added together. If you sum the daily unique line and compare it to the weekly unique line, the weekly number should be smaller or equal, because a device that returned on three days is one device that week. The gap is repeat attention, which is nice, and it is not three new listeners.

Search is not browse

Apple’s acquisition sources split the path. App Store search is people who viewed or downloaded from search, including ads that appear in search results. App Store browse is people who viewed the app or tapped download while browsing, and Apple’s examples are the Today, Games, and Apps sections. A podcast that wins a narrow show-name query and also gets a Today placement is living two lives. Averaging them hides which life broke.

The other sources are worth naming so you do not file them under search. An app referrer is a tap from another app, including StoreKit product page loads, and including Apple apps such as Messages, except Safari. A web referrer is a link from a website. If the chain of redirects runs through Safari, the last URL is the referrer. Taps from non-Safari browsers on iOS are attributed as that browser under app referrers, not as web. Unavailable covers older downloads from before source tracking, plus gift cards, promo codes, and MDM. None of that is “search got worse.”

High impressions, low page views

Devices are seeing the podcast app and not opening it. The row is the work: icon, name, subtitle, and the stars sitting next to them. A name that is a clever station brand and a subtitle that says “Listen now” gives a searcher nothing to recognize. The icon at row size has to read as audio, not as a portrait that turns into a blob. If the average is low because last month’s crash deleted downloads, that star is part of the row too. Apple does not publish a rank weight for it. It still changes the tap.

Do not answer this pattern by rewriting the long description. Those people have not opened the page. Keywords can change which queries produce the impression, and a mismatch between the query and the subtitle will look exactly like this chart. Fix the words in the row so they match the query you are willing to be seen for. “True crime” in the keyword field and a subtitle about morning news will manufacture impressions you cannot convert.

High page views, low downloads

They opened the page and did not press Get. The page is the work: the first screenshots, the preview’s first seconds, the opening lines of the description, and the rating text. For a podcast app, screenshot one should be a show in progress, not a marketing gradient. If reviews say episodes vanish offline, the screenshots cannot promise downloads you do not keep. That objection is conversion, which is downloads and pre-orders over unique device impressions, not a separate vanity rate.

Pre-orders count in that rate once, and not again when the episode app finally downloads. If you are pre-ordering a new show companion, a healthy pre-order week is real conversion, and the install week later is not a second win in the same metric. Product page views can include people who loaded the page from another app through StoreKit and left. Check the app-referrer source before you blame the screenshot test.

When the chart is allowed to exist

App Store metrics, including these, are available once you have at least five first-time downloads or pre-orders. Before that, the absence of a chart is not a bug. After that, a week with a handful of devices will whip the percentages around. Read counts beside rates. A conversion move on 40 unique impressions is a story about 40 phones, not about the category.