Understanding Universal Retention Analytics
Overview
The report type ‘Universal Retention Analytics’ supported by adbrix help clients analyze the retention rates between the ‘Standard Event’ and ‘Target Event’.
(Visit Analytics > Data Explorer > Universal Retention report type)
[[인용:정보:작게]] Please check more regarding the basic structure and concept of the ‘Data Explorer’ at Data Explorer. In this article, you will learn on the Metrics, definition of reports in ‘Universal Retention Analytics’
Retention vs. Universal Retention
Generally speaking, ‘retention analysis’ is a simple method of checking remaining users based on ‘New Install’ and daily ‘App Open’. This means that the ‘Standard Event’ and ‘Target Event’ is stuck as ‘New Install’ and ‘App Open’.
Old Retention Analysis : Standard Event - New Install Target Event - App Open
The ‘Universal Retention Analytics’ of adbrix expanded the old concept of retention analytics, and granted clients the freedom to change and adjust the ‘Standard Event’ and ‘Target Event’. You can use ALL the events integrated in the application for the retention analytics now.
Universal Retention Analytics of adbrix : Any and all integrated events in the application
Example of Universal Retention Analytics of adbrix : Analyze daily purchase retention rate for the daily ‘Log-in Completed’ users.
Answers to Questions
With ‘Universal Retention Analytics’, you can answer the following questions.
- How is the +1~3 day ‘Purchase’ retention status of ‘Signed-up Users’?
- How is the +1~14 day‘App Open’ retention status of ‘Logged-in Users’?
- How much is the +1~7 day ‘Purchase Amount’ of ‘Added to Cart Users’?
Universal Retention Setting
Retention Options
Set the options needed for the analysis.
|
Option |
Definition |
|
Standard Event |
Select the event to make as ‘Standard(start point)’ for the analysis. If you choose more than two events, the ‘or’ condition will be applied. |
|
Target Event |
Select the event to make as ‘Target(finish point)’ for the analysis. If you choose more than two events, the ‘or’ condition will be applied. |
|
Method Type |
Select the method of showing the analyzed values.
|
|
Value Type |
Select the method for the calculation of the analyzed values.
|
Metrics
Select the ‘Metrics’ needed for analysis.
|
Metrics |
Definition |
|
Standard User |
Number of users who generated selected events in ‘Retention Options’ > ‘Standards Event’ |
|
n day |
Number of result from the events in ‘Retention Options’ > ‘Standards Event’ You can select by ‘n day’, and the method of showing and calculation of the value follows the option of ‘Method Type’ and ‘Value Type’. |
[[인용:정보:작게]] Please check more regarding the basic structure and concept of the ‘Data Explorer’ at Data Explorer. In this article, you will learn on the Metrics, definition of reports in ‘Universal Retention Analytics’
Report Details
Example 1: Retention Analysis with standard of ‘New Install’ and target of daily ‘App Open’
Report Setting
|
Retention Option |
Select |
|
Standard Event |
abx:new_install |
|
Target Event |
abx:start_session |
|
Method Type |
Generic |
|
Value Type |
Unique |
|
Metrics |
Standard User, 1 day ,3 day, 5 day ,7 day ,15 day |
[[인용:안내:작게]] Meaning of 'abx:'
The event names starting 'abx:' means that the event is ‘Pre-defined Event’ of adbrix. If the event is not readily defined, the event name starts with ‘custom:’. Please refer to the document Data Analysis and Reports: Understanding the Event in adbrix for your information.
Explanation
In this report, you can analyze the ‘App Open’ retention of the users on certain period of time who have completed ‘New Install’ events. For example, if the value of ‘Standard User’ of April 1st is ‘500’, and value of Day 3 is ‘250’, it means that ‘250’ users out of ‘500’ users who installed the application on April 1st opened the application on April 4th.
Example 2: Retention Analysis with standard of ‘Login’ and target of daily ‘App Open’
Report Setting
|
Retention Option |
Select |
|
Standard Event |
abx:login |
|
Target Event |
abx:start_session |
|
Method Type |
Generic |
|
Value Type |
Unique |
|
Metrics |
Standard User, 1 day ,3 day, 5 day ,7 day ,15 day |
Explanation
In this report, you can analyze the ‘App Open’ retention of the ‘Logged-in’ users on certain period of time. For example, if the value of ‘Standard User’ of April 1st is ‘500’, and value of Day 3 is ‘250’, it means that ‘250’ users out of ‘500’ users who ‘Logged-in’ on April 1st opened the application on April 4th.
Example 3: Retention Analysis with standard of ‘Add to Cart’ and target of daily ‘Purchase’
Report Setting
|
Retention Option |
Select |
|
Standard Event |
abx:add_to_cart |
|
Target Event |
abx:purchase |
|
Method Type |
Generic |
|
Value Type |
Select from: Total, Unique, Price x Quantity |
|
Metrics |
Standard User, 1 day ,3 day, 5 day ,7 day ,15 day |
Explanation
In this report, you can analyze the ‘Purchase’ retention of the ‘Add to Cart’ users on certain period of time.
Case 1. Value Type = Unique
If the number of ‘Standard User’ on April 1st is ‘500’, and the number of Day 3 is ‘250’, it means that ‘250’ users out of ‘500’ users who ‘Added to Cart’ on April 1st ‘Purchased’ the product on April 4th.
Case 2. Value Type = Total
If the number of ‘Standard User’ on April 1st is ‘500’, and the number of Day 3 is ‘300’, it means that ‘500’ users who ‘Added to Cart’ on April 1st made ‘300’ purchases on April 4th.
Case 3. Value Type = Price x Quantity
If the number of ‘Standard User’ on April 1st is ‘500’, and the number of Day 3 is ‘30,000,000’, it means that ‘500’ users who ‘Added to Cart’ on April 1st generated total purchase amount of ‘30,000,000’.