What is an app unit?
Table of Content:
An app unit is an App Store Connect metric that counts a first-time app purchase or download when a user taps the Get or Buy button for an app or bundle. Apple does not count app updates, redownloads, or downloads to another device under the same Apple Account as new app units.
In plain language: an app unit is Apple’s way of counting a new acquisition event for your app.
If someone downloads your free iOS app for the first time, that can count as one app unit. If the same person later installs the app on another iPhone or iPad using the same Apple Account, that does not create another app unit.
App unit definition
An app unit is the number of first-time app purchases or downloads recorded in App Store Connect.
Apple defines app and bundle units as “the number of first-time purchases of your app or bundle.” An app unit is counted when a customer taps Get or Buy for the first time. (Source: developer.apple.com)
The metric is used by app developers, publishers, and marketers to understand how many new users acquired the app from the App Store during a selected period.
App unit at a glance
Attribute | Details |
Metric type | App Store acquisition metric |
Platform | App Store Connect |
Counts | First-time app downloads or purchases |
Does not count | Updates, redownloads, installs on another device under the same Apple Account |
Used by | App developers, publishers, ASO managers, mobile marketers |
Best for | Measuring first-time acquisition from the App Store |
Often compared with | Product page views, impressions, installs, downloads, conversion rate |
Why app units matter
App units matter because they sit close to the moment where App Store discovery turns into acquisition.
Impressions show that users saw your app. Product page views show that users opened the listing. App units show that users took the next step and tapped Get or Buy.
That makes app units useful for ASO analysis, especially when you are trying to understand whether visibility is translating into real acquisition.
Apple says App Analytics helps teams understand how people discover and interact with apps on the App Store. (Source: developer.apple.com)
For practitioners, the metric becomes useful when it is read with the rest of the funnel:
- If impressions rise but app units stay flat, the app may be visible but not convincing enough.
- If product page views rise but app units do not, screenshots, ratings, reviews, pricing, or messaging may be hurting conversion.
- If app units rise after a metadata or creative update, the change may have improved store performance.
- If app units fall in one country but not others, localization or market-level competition may be the issue.
- If paid traffic increases but app units do not move enough, the campaign may be sending low-intent users or the product page may not match the ad promise.
The main mistake is treating app units as “total installs.”
They are not the same thing.
An app unit is tied to a first-time App Store acquisition event. Installs can include usage across devices, redownloads, or other device-level behavior depending on the reporting source. Apple’s own WWDC explanation says one app unit can generate multiple installations when a customer purchases an app once and installs it on more than one device.
That difference matters when the team is reporting growth.
If you tell a stakeholder “downloads are up,” they may assume more devices have the app installed. If you say “app units are up,” you are talking about first-time acquisition from the App Store.
App unit vs install vs download vs product page view
Metric | What it means | What it tells you | Common mistake |
App unit | First-time app purchase or download in App Store Connect | New acquisition from the App Store | Treating it as total installs |
Install | App installed on a device | Device-level installation or usage context | Assuming every install is a new user |
Download | General term for getting the app | Can mean different things depending on platform or report | Using it without defining the source |
Product page view | User opened the app’s product page | Interest after discovery | Treating views as acquisition |
Impression | User saw the app in App Store surfaces | Visibility | Assuming visibility means conversion |
A clean ASO report should not mix these terms.
Use app units when you are talking about first-time App Store acquisition in Apple reporting. Use installs only when your source actually measures installs.
How app units work in App Store Connect
App units are reported in App Store Connect and can be analyzed by date range, territory, source type, device, product page, and other dimensions depending on the report.
Apple notes that App Units, In-App Purchases, and Sales are based on the platform where the app is downloaded from the App Store. (Source: developer.apple.com)
A practical ASO workflow usually looks like this:
- Check impressions to understand visibility.
- Check product page views to understand listing interest.
- Check app units to measure first-time acquisition.
- Compare app units with conversion rate.
- Segment the data by country, source type, product page, and campaign where possible.
- Match changes against ASO updates, ratings, reviews, localization, featuring, or paid traffic.
That is where the metric becomes useful.
Not as a standalone number. As part of the App Store acquisition funnel.
App unit example
Let’s say a productivity app updates its App Store screenshots in Spain.
Before the update:
Metric | Value |
Impressions | 50,000 |
Product page views | 5,000 |
App units | 750 |
Product page conversion | 15% |
After the update:
Metric | Value |
Impressions | 52,000 |
Product page views | 5,400 |
App units | 1,080 |
Product page conversion | 20% |
The app did not suddenly become much more visible. Impressions only moved slightly.
The bigger change happened after users reached the product page. More visitors tapped Get.
That is the kind of situation where app units can help the team understand whether creative work is improving acquisition.
How app units connect to ASO
App units are one of the clearest acquisition-side metrics for ASO on the App Store.
ASO teams usually work on two jobs:
- Get more qualified users to see the app.
- Convert more of those users into installs or purchases.
App units help measure the second part.
If keyword rankings improve but app units do not, visibility may be attracting the wrong audience. If product page views rise but app units stay flat, the listing may not be converting. If app units increase after localized screenshots go live, the creative update may have made the app easier to understand in that market.
For example, a finance app may rank better for “budget planner” after a metadata update. That looks promising. But if app units do not increase, the team should check whether the screenshots, reviews, rating score, pricing, or value proposition match what users expected from that search.
Rankings explain where users can find the app.
App units help show whether users actually choose it.
What affects app units?
- App Store visibility. Higher visibility can bring more chances to earn app units. Keyword rankings, browse placement, featuring, category position, and paid Apple Search Ads campaigns can all affect how often users discover the app.
- Product page conversion. The product page has to finish the job. Screenshots, app preview video, icon, subtitle, ratings, reviews, and pricing can all influence whether a user taps Get or Buy.
- Ratings and reviews. A weak rating or negative recent reviews can reduce trust before installation. Strong ratings and relevant review proof can support conversion, especially in competitive categories.
- Localization. App units can behave very differently by country. A direct translation may not be enough. Screenshots, messaging, benefits, and social proof often need to match local expectations.
- Pricing. Paid apps naturally create more friction than free apps. For paid apps, the app unit still counts when the user taps Buy for the first time, but price sensitivity can strongly affect conversion.
- Seasonality. Some categories move with demand. Fitness apps often rise around New Year. Education apps may see changes around school cycles. Travel apps can shift before holiday periods.
- Source quality. Not every visitor has the same intent. Search traffic, browse traffic, paid traffic, featuring, and referral traffic can all produce different app unit patterns.
How to use app units in reporting
App units are useful when the report answers a business question.
Use app units to understand:
- whether App Store acquisition is growing
- whether ASO updates improved first-time downloads
- whether conversion changed after a creative refresh
- which countries generate stronger acquisition
- whether paid or organic traffic is producing real app store actions
- whether product page variants or custom product pages influence acquisition
- whether app visibility is translating into app units
Avoid reporting app units without context.
A better report sounds like this: “App units in Germany increased 18% after localized screenshots went live. Impressions were stable, so the lift likely came from better product page conversion rather than broader visibility.”
A weak report sounds like this: “App units increased this week.”
The first one helps the team decide what to do next. The second one only describes a number.
Related terms
- Keyword Effectiveness Index (KEI)
- App Store Visibility
- App Visibility
- What is App Store Browse?
- Mobile App Analytics
- What Are Top Charts?
- What is ranking history?
- What is cost per install (CPI)?
FAQ
What is an app unit?
An app unit is an App Store Connect metric that counts a first-time app purchase or download when a user taps Get or Buy for an app. Updates, redownloads, and downloads to another device under the same Apple Account do not count as new app units.
What is an app unit in App Store Connect?
In App Store Connect, an app unit represents a first-time acquisition of an app or bundle. Apple counts an app unit when a customer taps Get or Buy for the first time. App units help teams measure new App Store acquisition during a selected period.
Is an app unit the same as an install?
No. An app unit is not always the same as an install. An app unit counts a first-time App Store acquisition. Installs can refer to device-level installation behavior. One app unit can lead to multiple installations if the same user installs the app on more than one device.
What is the difference between app units and product page views?
Product page views show how many times users opened the app’s App Store listing. App units show how many first-time purchases or downloads were recorded. Product page views measure interest. App units measure acquisition action.
Why did app units increase?
App units can increase because of stronger keyword visibility, better product page conversion, paid campaigns, featuring, improved ratings, stronger reviews, seasonal demand, or localization. To understand the cause, compare app units with impressions, product page views, conversion rate, source type, and recent ASO changes.
Why did app units decrease?
App units can decrease when rankings drop, competitors gain visibility, product page conversion weakens, ratings decline, paid traffic slows, seasonality changes, or localized messaging stops matching user intent. The fastest diagnosis usually starts with country, source type, keyword movement, ratings, and recent listing changes.
How should ASO teams use app units?
ASO teams should use app units to measure whether visibility and product page work turn into first-time acquisition. App units are most useful when compared with impressions, product page views, conversion rate, keyword rankings, ratings, reviews, and competitor movement.
How can AppFollow help with app unit analysis?
AppFollow helps teams monitor the ASO signals that often explain app unit changes, including keyword rankings, category movement, ratings, reviews, competitors, and app store performance. This helps app teams understand whether acquisition changes are connected to visibility, conversion, reputation, or market pressure.
