You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Adapty Analytics are a powerful suite of tools for data visualization and analysis. You can use the data to gain valuable insights into your user base, make data-driven decisions, and optimize your app's performance.
11
+
Adapty Analytics is a powerful suite of tools for data visualization and analysis. Built for application development teams, it focuses on your app's financial performance and user behavior.
12
+
13
+
In addition to standard metrics available in your store analytics (such as revenue or installations), Adapty calculates compound metrics: user lifetime value, cohort analysis, and more. Dedicated sections analyze user behavior that leads to revenue loss: retention graphs, billing issue resolution data. Browse the charts to gain insight into user behavior, and optimize your application with data-driven decisions.
14
+
15
+
Read the [How Adapty Analytics Works](how-adapty-analytics-works) guide to learn more about how data is sourced and processed.
13
16
14
17
:::tip
15
-
Read the [How Adapty Analytics Works](how-adapty-analytics-works) guide to learn more about data sources and processing.
18
+
Enable [Adapty User Acquisition](adapty-user-acquisition)to upgrade the analytics capabilities of Adapty. UA uses marketing data to analyze the relationship between ad campaigns and user behavior. Its charts display a complete picture of your application's economy, with ROI calculations and precise attribution data.
16
19
:::
17
20
18
21
## Overview
19
22
:::link
20
23
Main article: [Analytics Overview page](overview)
21
24
:::
22
25
23
-
The Overview page presents an at-a-glance summary of your applications' key performance metrics. You can click the "Edit Metrics" button to customize which charts the page displays.
26
+
The Overview page presents an at-a-glance summary of your applications' key performance metrics. To customize the displayed charts, click **Edit Metrics**.
@@ -83,16 +86,17 @@ The Conversion tab displays graphs for conversion rates at different stages of t
83
86
Main article: [Predicted LTV and Revenue](predicted-ltv-and-revenue)
84
87
:::
85
88
86
-
Pro+ and Enterprise plan users can access cohort LTV (lifetime value) and revenue predictions. Adapty leverages historical data and advanced machine learning algorithms to predict these metrics' values.
89
+
Users of paid tiers can view predictions for cohort LTV (lifetime value) and revenue. Adapty analyzes historical data with advanced machine learning algorithms to estimate future values.
Main article: [Controls](controls-filters-grouping-compare-proceeds)
93
97
:::
94
98
95
-
You can use filters and grouping controls to view data pertaining to a specific subsection of users. For example, you can filter the retention graph by store and compare user behavior between Android and iOS.
99
+
Use filters and grouping controls to view data for specific user segments. For example, you can filter the retention graph by store and compare user behavior between Android and iOS.
Main article: [User Acquisition](adapty-user-acquisition)
120
-
:::
121
-
122
-
Enable **Adapty User Acquisition** to leverage data from third-party marketing platforms, and expand Adapty's analytics capabilities. The User Acquisition view allows you to explore the relationship between ad campaigns and user behavior.
122
+
*[Adapty User Acquisition](adapty-user-acquisition)
123
+
*[Exporting analytics with API](export-analytics-api)
@@ -13,35 +13,47 @@ Adapty users may encounter **discrepancies** when comparing similar sets of data
13
13
* Adapty charts to third-party charts
14
14
* Different charts within Adapty
15
15
16
-
Most of the time, discrepancies occur because **different sources process the same data differently**. Other times, they indicate an **issue with your Adapty configuration**.
16
+
## Troubleshooting algorithm
17
17
18
-
This article explains common issues that lead to data discrepancies, as well as common solutions.
18
+
Most discrepancies between Adapty and other platforms are expected and normal. They occur because **different sources process the same data differently**.
19
19
20
-
## Missing data
20
+
Other times, they indicate an **issue with your Adapty configuration**.
21
+
22
+
If you suspect that your data varies from platform to platform, the best course of action is to [export raw data](export-analytics-api-requests) and **compare the files**.
21
23
22
-
### Server notifications and RTDN
24
+
* Even stores can experience issues related to data processing and presentation. Access the stores' **raw transaction data** for the most accurate comparison.
25
+
* When comparing Adapty to another analytics platform, use store transaction reports as the source of truth and point of comparison.
26
+
* It's easier to identify inconsistencies with a limited data set. Compare small volumes of data — focus on a specific product and a single day.
27
+
* Identify whether your discrepancy stems from a difference in **pricing** or **event number**. Pricing issues can be fixed with a [product update](#product-pricing). Event issues may indicate [server-side problems](#issues-with-server-notifications-and-rtdn).
28
+
* View the [event feed](event-feed) to monitor incoming events — you may notice unexpected behavior.
23
29
24
-
If you didn't correctly configure server-to-server communication between Adapty and the stores, Adapty will not be able to process some events, such as subscription renewals.
30
+
After you identify where the data diverges, you can look into the following common causes:
25
31
26
-
Complete the configuration as soon as you can ([App Store](app-store-server-notifications) | [Play Store](real-time-developer-notifications-rtdn)) and [wait](#data-delays) for the stores to establish the connection.
32
+
## Issues with server notifications and RTDN
33
+
34
+
Adapty does not receive the necessary event data if you didn't correctly configure the store connections. This particularly affects events that occur without direct user involvement — subscription renewals, billing issues, etc.
35
+
36
+
Complete the server-to-server configuration as soon as you can ([App Store](app-store-server-notifications) | [Play Store](real-time-developer-notifications-rtdn)) and [wait](#data-delays) for the stores to establish the connection.
27
37
28
38
You can [manually upload](importing-historical-data-to-adapty) the missing App Store Connect data to Adapty.
29
39
40
+
## Missing data
41
+
30
42
### Users with out-of-date app versions
31
43
32
-
If a part of your install base uses an older version of the application without the Adapty SDK, Adapty won't be able to receive their data. For this reason the numbers of Adapty and other sources will diverge.
44
+
If some of your users run an older version of your app without the Adapty SDK, Adapty does not receive their data. For this reason the numbers of Adapty and other sources will diverge.
33
45
34
46
### Integration issues
35
47
36
48
Some Adapty integrations (for example, Adjust or AppsFlyer) require additional application code to work. If you configure the Adapty dashboard, but do not update your application, the necessary data won't show up in Adapty.
37
49
38
50
### Missing historical data
39
51
40
-
Adapty doesn't have access to your application's historical data, unless you [manually import](importing-historical-data-to-adapty) it. If the chart's [time range](controls-filters-grouping-compare-proceeds#time-ranges) starts before you integrated Adapty into your application, and you haven't imported historical data, the values displayed will differ from other sources.
52
+
Adapty doesn't have access to your application's historical data, unless you [manually import](importing-historical-data-to-adapty) it. If a chart's [time range](controls-filters-grouping-compare-proceeds#time-ranges) starts before you integrated Adapty, and you didn't import historical data, its values will differ from other sources.
41
53
42
54
## Data delays
43
55
44
-
Adapty aims to provide a close to real-time analysis of your application's economy. The following limitations and exceptions apply:
56
+
Adapty aims to provide near real-time analysis of your application's economy. The following limitations and exceptions apply:
45
57
46
58
* When you first integrate Adapty, the data may not appear immediately.
47
59
* When you enable an integration with a third-party platform, there may be a delay before the data is fully synchronized.
@@ -107,11 +119,7 @@ To ensure accurate reporting, Adapty [may infer](controls-filters-grouping-compa
107
119
108
120
If you need to clearly distinguish between the two, you can [create a new user segment](segments) with the `Country by store account` attribute, and [filter analytics by segment](controls-filters-grouping-compare-proceeds#filtering-and-grouping).
109
121
110
-
## Product editing
111
-
112
-
Incorrect or inconsistent product data may cause discrepancies in analytics. Do not edit the **access level** or the **store product ID** unless you accidentally make a typo in one or the other. Create a new product instead.
113
-
114
-
### Product pricing
122
+
## Product pricing
115
123
116
124
If incorrect product pricing causes a revenue discrepancy, changing the price doesn't fix it retroactively. To change existing transactions' prices, you need to forcibly override them by importing correct data.
117
125
@@ -125,30 +133,21 @@ If your setup includes multiple attribution providers that disagree with one ano
125
133
126
134
## Differences in terminology
127
135
128
-
Different platforms may have different names for the same concept. Metrics related to [revenue](#revenue-fees-and-taxes) vary in name from platform to platform:
136
+
Different platforms may have different names for the same concept. Metrics related to [revenue](#fees-and-taxes) vary in name from platform to platform:
129
137
130
-
|Metric |Adapty | App Store Connect | Google Play Console |
|**Proceeds after store commission and taxes**| Proceeds | Earnings |
143
+
|**ARPPU**| Proceeds per paying user | ARPPU |
136
144
137
-
Other metrics may be similar in name, but different in definition.
145
+
Other metrics may differ in definition, as well:
138
146
139
147
-**Subscriptions**:
140
-
- Adapty only registers a [new subscription](reactivated-subscriptions)**after** the end of a free trial.
148
+
- Adapty does not count new trials as subscriptions. A [new subscription](reactivated-subscriptions)always starts with a financial transaction.
141
149
- Other platforms, such as Google Play Console, may count **each trial as a new subscription**, even before the first payment was made.
142
150
-**Retention**:
143
151
- Adapty measures retention based on the number of subscription renewals.
144
152
- App Store Connect considers a user retained if they open the application on the specified day. A user without a subscription will count, but the subscribed user who didn't open the app on that day won't.
145
-
- Google Play Console's "Retained Installers" metric measures retention based on the number of days the application remains installed on the user's device. Users that don't open the application count towards this metric.
146
-
147
-
## General troubleshooting algorithm
148
-
149
-
If you suspect that your data varies from platform to platform, and the reasons above don't explain the discrepancies, the best course of action is to **export raw data** and **compare the files**.
150
-
151
-
* Even stores can experience issues related to data processing and presentation. Access the stores' **raw transaction data** for the most accurate comparison.
152
-
* When comparing Adapty to another analytics platform, use store transaction reports as the source of truth and point of comparison.
153
-
* It's easier to identify inconsistencies with a limited data set. Compare small volumes of data — focus on a specific product and a single day.
154
-
* Identify whether your discrepancy stems from a difference in **pricing** or **event number**. Pricing issues can be fixed with a [product update](#product-pricing). Event issues may indicate [server-side problems](#connection-issues).
153
+
- Google Play Console's "Retained Installers" metric measures retention based on the number of days the application remains installed on the user's device. Users that don't open the application count towards this metric.
0 commit comments