Universal Retention Analytics, Understanding and Interpreting
Understanding Universal Retention
In the Universal Retention Analytics report type provided by DFINERY,
We analyze retention between the Standard Event, which is the reference point for analysis, and the Target Event, which is the subject of analysis.
(Select Analytics > Data Explorer > Universal Retention Analytics report type)
[[Citation:Information:Small]] For the basic structure and concepts of using Data Explorer, please additionally check
the Data Explorer - Understanding and Examples of Analysis Structure
document.
This document explains metrics, report definitions, and interpretation methods for understanding the Universal Retention Analytics report type.
Retention vs. Universal Retention
In general, retention analysis was a simple method of checking the retention rate that calculated App Opens by date based on New Install.
In other words, in retention analysis, the analysis criteria and target events were fixed.
Existing Retention Analysis: In general, only App Open is analyzed based on New Install
DFINERY Universal Retention analysis expands the concept of existing retention analysis,
It allows you to change the standard event and target event of analysis as needed.
In other words, all events linked to the app can be used for retention analysis.
DFINERY Universal Retention: Analysis criteria and target events can be freely changed
DFINERYs Universal Retention example: Analyzing purchase retention by date, targeting only users who completed login by date
Answer the question
Universal Retention analysis allows you to answer the following questions:
- What is the purchase retention status for +1~3 days based on those who have completed membership registration?
- What is the app open retention status for +1~14 days based on logged in users?
- Add to Cart +1~7days based on completed users. What is the purchase amount status?
Universal Retention Settings
Retention Options
Set the options required for analysis.
| Option | Justice |
| Standard Event | Select an event that will be the 'baseline' for analysis.If more than one event is selected, it will be set to 'or' condition. |
| Target Event | Select the event that will be the ‘target’ for analysis. If more than one event is selected, it will be set to 'or' condition. |
| Method Type |
Choose how you want your analysis numbers to be expressed.
|
| Value Type |
Choose how the analysis numbers are calculated.
|
Metrics
Select the Metric needed for analysis.
| Metrics | Justice |
| Standard User | This is the number of users who triggered the event selected in Retention Options > Standards Event. |
| n day |
This is the result of Retention Options > Target Event occurring.
You can select by n day, and the expression and calculation method of the numerical value follows the options of Method type and Value Type. |
[[Quote:Information:Small]] About the basic structure and concepts of using data explorers such as Group by, Analytics Conditions, and Audience.
Data Explorer - Please check additional documentation for understanding of the analysis structure and examples
.
Report examples and interpretation
Based on New Install, app activation retention analysis by date
Report settings
| 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 |
[[Quote:Guide:Small]]
Meaning of 'abx:'
Events starting with 'abx:' mean that they are linked to pre-defined events (Pre defined) in DFINERY (Adbrix).
If it is not a predefined event, it begins with 'custom:'.
You may additionally refer to the document
Defining and Understanding DFINERY Events
.
Report interpretation
Analyze app activation retention for users who made a New Install on a specific date. For example, if the Standard User figure on April 1st is 500 and the 3 day number is 250, it means that among the 500 users who made a New Install on April 1st, the number of users who activated the app on April 4th was 250. do.
App activation retention analysis by login and date
Report settings
| 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 |
Report interpretation
Analyze app activation retention for users who logged in on a specific date. For example, if the Standard User figure on April 1st is 500 and the 3 day number is 250, it means that among the 500 users who logged in on April 1st, the number of unique users who activated the app on April 4th is 250. do.
Purchase retention analysis by date based on Add to Cart
Report settings
| Retention Option | select |
| Standard Event | abx:add_to_cart |
| Target Event | abx:purchase |
| Method Type | Generic |
| Value Type | Choose between Total, Unique, Price x Quantity |
| Metrics | Standard User, 1 day ,3 day, 5 day ,7 day ,15 day |
Report interpretation
Purchase retention is analyzed for users who completed adding to their shopping cart on a specific date.
When Value Type = Unique
If the Standard User number on April 1st is 500 and the 3 day number is 250 -
This means that out of the 500 users who completed adding to the shopping cart on April 1st, 250 users made a purchase on April 4th.
When Value Type = Total
If the Standard User number on April 1st is 500 and the 3 day number is 300 -
This means that the total number of purchases made on April 4th by 500 users who completed adding to the shopping cart on April 1st was 300.
When Value Type = Price x Quantity
If the Standard User figure on April 1st is 500 and the 3 day number is 30,000,000 -
This means that the total purchase amount generated on April 4th by 500 users who completed adding to the shopping cart on April 1st is 30,000,000.