Why should you connect your Apple console?
Compare your real downloads and revenues with your competitors
Measure your app's conversion rate across countries
Analyze the impact of your ASO efforts on your Impressions and Product Page Views
Keep track of your app's financial situation by analyzing revenues, in-app purchases, and paying users
Reply to your reviews directly in AppTweak (only for Admin, Account Holder, and Customer Support roles)
1. Compare real downloads & revenues with competitors
Users that have synced their App Store Connect account with AppTweak will be able to view their real Downloads under the Analytics tab in the Store Performance section.
The first view will show you the cross competition option:
You will first have three important indicators:
Total downloads: giving you the total downloads of your app on the selected date range
Avg. Daily Downloads: indicating the daily average of downloads your app is getting each day. This average will be computed on the date range selected
Download growth: a very important indicator showing you the growth of your downloads compared to the last equivalent period (i.e. if you selected the month of August, we will show your app's download growth compared to the month of July).
Breakdown your Downloads by source
In order to understand which channel is driving the most downloads, you can switch to the 'source' option.
The option Source will hide the competitorsā data and show the breakdown by the source of the main appās downloads. As a reminder, Apple splits the traffic into five different sources:
App Store Search: Search in the App Store, including Apple Search Ads.
App Store Browse: Navigation in the App Store such as top charts, stories, features, similar appsā¦
App Referrer: Referrals from another app on the store.
Web Referrer: Referrals from a page on the web.
Unavailable: Undefined traffic source.
š”App Store Search is often the highest because the user searches on the store intending to download an app. Browse is often lower, however, featured apps in the Today tab can suddenly trigger many new installations from this channel.
2. Measure your app's conversion rate
In this section of Analytics, you will be able to monitor your app's conversion rate from Impressions to Downloads, Impressions to Page Views, and from Page Views to Downloads.
To obtain the conversion rate from Impressions (unique devices) to Downloads in a given country, you need to select the metric "Downloads", add the given country in the filter, and then select "compare to Impressions (unique devices)".
The conversion rates can be defined as follows:
Impressions to Downloads: the % of users that saw your app on the App Store and then downloaded your app on a device with iOS 8, or later.
Impressions to Page Views: the % of users who saw your app on the App Store and then viewed your app's product page on the App Store on devices running iOS 8, or later.
Page Views to Downloads: the % of users who viewed your app's product page on the App Store on devices running iOS 8, or later and then downloaded your app.
As explained above, on iOS, there are 3 conversion rates. In the conversion analysis section, you can analyze all 3 of them.
Each conversion analysis is divided into 3 sections:
The filter bar
Overall KPIs
Conversion Rate History Chart
The Filter Bar
The filter bar is where you can decide the data you wish to analyze. You can choose to analyze the overall conversion rate of your app or have it broken down by source.
Overall KPIs
The KPIs give you a quick glance of your app's performance in the given country and over the selected date range.
The Highest Conversion shows the highest conversion rate your app had during the given date range.
The Lowest Conversion shows the lowest conversion rate your app had during the given date range.
The Average Conversion shows the average conversion rate your app had during the given date range.
The Conversion Growth shows the growth between the average conversion rate over the selected date range and the equivalent previous period.
š”Checking these KPIs on a regular basis will help you rapidly know if your app's performance is higher or lower than usual. The Max and Min value can help you gauge how volatile your app's conversion rate is and identify any unusually high or low rates.
Conversion Rate History Chart
The Conversion Rate History Chart shows you the progress of your app's conversion rate on a daily or weekly basis over the selected date range. This is where you can identify any unusual peak or drop in your app's conversion rate.
ā
Compare your app's conversion across sources
If you select the breakdown by source in the filter bar, the conversion rate of your app will be broken down into four values:
Conversion rate from App Store Search traffic: "Customers who viewed your app or downloaded it for the first time from Search on the App Store. Based on devices running iOS 8 or tvOS 9, or later. Includes Search Ads in App Store search."
Conversion rate from App Store Browse traffic: "Customers who viewed your app or tapped to download it for the first time while browsing the App Store (for example, in the Featured, Categories, or Top Charts sections). Based on devices running iOS 8 or tvOS 9, or later."
Conversion rate from App Referrers: "Customers who tapped a link in an app that brought them to your App Store product page. Based on devices running iOS 8 or tvOS 9, or later. Includes apps using the StoreKit API to load your product page. Includes Apple apps, such as Messages, except Safari. See Top App Referrers in App Analytics for a list of referring apps."
Conversion rate from Web Referrers: "Customers tapped a link from a website that brought them to your App Store product page. Based on websites visited in Safari on devices running iOS 8 or later. If a chain of redirects in Safari leads to your App Store product page, the referring website will be the last URL in the chain. See Top Web Referrers in App Analytics for a list of referring websites.
āļøFor iOS apps, taps from websites in non-Safari web browsers, such as Chrome, are attributed as that web browser app in App Referrers. For macOS apps, taps from non-Safari web browsers are attributed to Web Referrers."
3. View your impressions and page views
In order to analyze the entire user traffic, you can also analyze your impressions and page views for your app.
By using the view by the source you will also understand the actions of the users before downloading the app. You will be able to identify which source allows users to see your app the most (look at impressions) and which one makes users land on your app page (look at Page Views).
4. Keep track of your financial situation
In this section, users will be able to keep track of their own app's Revenues, In-App Purchases, and Paying Users directly in AppTweak in the Analytics Tab.
Just like you can compare your downloads with the competitors' download estimates in Store Performance, in Financial Analysis you can cross your app's real revenues with AppTweak's estimation of your competitors' revenues.
What do we mean by āRevenuesā?
The metric we use as revenues for App Store apps is the āSalesā, which Apple defines as: "The total amount billed to customers for purchasing apps, app bundles, and In-App Purchases. Taxes are only included in the sales if those taxes were included in the App Store price".
Real data vs estimates in the "Cross-Competition View"
Sales are also what we use to compute the revenue estimates of your appās competitors, which makes it really easy to compare your own data with estimations.
To access your competitors' revenues make sure you are in the "Revenues" tab, that you are looking at the selected country and that you have selected the "Cross-Competiton" view.
Use the legend on the right to help you know for which apps we are showing real data and for which apps we are showing estimates.
Explore advanced metrics by traffic source
Besides Revenues, we also pull other financial metrics from your App Store Connect account such as the number of In-App Purchases and Paying Users.
As a reminder, here is how Apple defines them:
In-App Purchases: "The number of in-app purchases on devices running macOS 10.14.1, iOS 8 or tvOS 9, or later. Introductory price subscriptions and subscription renewals are included in this metric. Restored in-app purchases, whether on the same or different device, are not counted."
Paying Users: "The number of unique users, based on Apple ID, that paid for an app or an In-App Purchase."
For both these metrics and the revenues, you can use the filters to view the breakdown by traffic source :
Having this breakdown by source will help you understand better where your paying users are coming from. This way you can optimize the channels that are used the most and try to understand why the others don't get as much traffic.
5. Benchmark your In-App Events performance
If your app has In-App Events running, you can measure and compare their performance directly in the AppTweak tool.
Select the date range of your choice, AppTweak will show the In-App Events that were running for your app during the selected time period. You can then select which events you want to add to your analysis.
You can then get a summary of the overall performance of the selected events and compare their metrics one against the other and over time to measure which were most successful.
AppTweak pulls the following metrics from your console to help you carry out your Analysis:
Events:
Unique Event Impressions
Unique Event Page Views
Event Opens
Event Reminders
Event Notification Taps
Downloads & Installs:
Downloads
Redownloads
Units
Installs
Uninstalls
Users & Devices:
Paying Users
Sessions
Active Devices
Rolling Active Devices
Revenue:
In-App Purchases
Sales
Why isn't my data showing in Analytics?
There are multiple reasons why you can't see your integration data in AppTweak:
If you've recently established the integration, it might take up to 24 - 48 hours for AppTweak to fully fetch all the data and display it in the tool. If you've recently integrated your consoles, please check back within 24 hours.
Each user has their own individual dashboard. Therefore, if your colleague integrates a console, it will only show up on their dashboard. Every user has to integrate the Developer Console individually.
The verification code provided by Apple is only valid for 30 days. Therefore you need to re-verify your account every 30 days. To re-verify your account navigates to My Account > Integrations and click on the āreverifyā link that will automatically appear next to the integrations that are expired.














