Retention¶
Overview¶
Retention is a feature that analyzes whether users who triggered a specific event at a specific point in time later trigger subsequent events, based on events created in Analytics.
You can analyze user revisit/retention rates and, through cohort-based analysis, identify which cohorts have higher retention.
What Can You Do?¶
Business/Marketing Users¶
- Set D+1 to D+30 retention as a key KPI and add it to a dashboard to monitor daily/weekly/monthly user retention status.
- Compare cohort retention before and after a campaign to quantitatively measure whether the campaign contributed to revisits.
- Identify retention differences by country to build content strategies suited to specific regions.
Data Analysts¶
- Compare cohorts at the time of a new feature release with earlier cohorts to analyze the feature's impact on retention.
- Use dimension-based cohort segmentation to identify which user groups have higher retention.
- Analyze the retention curve (the decrease pattern of N-day retention) to discover critical drop-off points for users.
Developers¶
- Verify whether event data is being sent correctly using the D+0 value.
- After adding a new event, set it as the reference event to confirm data reception.
Quick Start¶
If you are creating retention for the first time, follow the steps below to create your first retention.
- Click the Create button at the top, then select Retention.
- Select the workspace where you want to save the retention at the top.
- In the [Settings] tab, set the project, period (daily/weekly/monthly), and date range to analyze.
- In the [Data] tab, select the reference event and return event.
- Select the identifier (userId / deviceId).
- Check the retention values in the preview on the right.
- Click the Save button at the bottom and enter the retention title and description.
Note
For detailed settings such as dimensions, filters, and visualization options, refer to Full Features.
Full Features¶
Key Concepts¶
| Concept | Description |
|---|---|
| Cohort | A group of users who triggered the reference event during the same period |
| Reference Event | The event that defines the cohort. Users who triggered this event are grouped into the cohort |
| Return Event | The event used to measure retention. Tracks whether cohort users triggered this event later |
| Identifier | User identification key (userId for account-based, deviceId for device-based) |
[Settings] Tab¶
Enter the basic retention information. 
| Item | Required | Description |
|---|---|---|
| Project | Required | Select the project to analyze (single selection) |
| Period | Required | Select the aggregation unit for daily / weekly / monthly cohorts |
| Date Range | Required | Select the period for reference and return events |
When selecting a date range, you can use the quick select buttons or choose dates directly through the calendar button.
The Recent and Last quick select buttons use different reference dates.
| Type | Reference Date | Example |
|---|---|---|
| Recent N days | Calculated from today | Recent 7 days -> 7 days including today |
| Last N days | Calculated from yesterday | Last 7 days -> 7 days including yesterday |
[Data] Tab¶
Set the cohort definition and retention measurement criteria.
Reference Event¶
Select the event that forms the cohort. 
- Example:
hive_app_login-> group users who logged in during the period into the cohort - Example:
hive_character_level_change-> group users who leveled up a character into the cohort
Return Event¶
Select the event used to measure cohort user revisit/reaction.
- Can be set the same as the reference event (for example, login -> re-login tracking)
- Can be set to a different event (for example, login -> in-app purchase completion)
Identifier¶
Select the identifier used as the basis for user tracking.
| Identifier | Description |
|---|---|
| userId | Tracks users based on account. |
| deviceId | Tracks users based on device. |
Dimension Value¶
Analyze cohorts defined by the reference event by subdividing them using specific attributes. 
- Example: Split cohorts by country and compare retention differences by country
- Example: Split cohorts by OS and compare retention by platform
Note
The items displayed in the dimension value are shown based on reference event attributes. In retention analysis, dimensions are the basis for subdividing cohorts (user groups that triggered the reference event), so return event attributes cannot be used as dimensions.
[Filter] Tab¶
Set filter conditions that apply to both the reference event and return event added in the [Data] tab.
If you want to apply a condition only to a specific event, use the individual event filter in the [Data] tab.
Select the filter target from Attribute and Segment.
- Reference Event Filter: Include only reference events with specific attributes in the cohort
- Return Event Filter: Aggregate only return events with specific attributes as retention
Note
The items displayed in the filter dimension expose the attributes of both the reference event and the return event. If a specific event does not have that attribute, the filter does not apply to that event.
Filter Condition Operators¶
| Operator | Description |
|---|---|
| Equals | Includes only data that exactly matches the entered value. Example: view only users whose country is "Korea" |
| Not Equals | Includes only data that does not match the entered value. Example: view only users whose OS is not "Android" |
| Less Than or Equal | Includes data that is less than or equal to the entered value. Example: view only cases where the payment amount is 10,000 KRW or less |
| Greater Than or Equal | Includes data that is greater than or equal to the entered value. Example: view only users whose level is 50 or higher |
| Range | Includes data that falls between the two entered values. Example: view only cases where the payment amount is between 1,000 KRW and 10,000 KRW |
| No Value | Includes data where no value is recorded for that attribute. Example: view only users with no country information |
| Has Value | Includes data where at least one value is recorded for that attribute. Example: view only users with country information |
Note
The Greater Than or Equal, Less Than or Equal, and Range operators are not shown when the attribute data type is text.
- You can combine multiple filter conditions with AND / OR operators.
- AND: Includes only data that satisfies both conditions.
- OR: Includes data that satisfies either condition.
Segment Filter¶
If you choose a segment as a filter, only data for users belonging to that segment will be reflected in retention. Depending on how you combine segment conditions, you can use it in two ways: dynamic cohort and static cohort.
| Method | Condition Combination | Meaning |
|---|---|---|
| Dynamic Cohort | Select segment only | Recalculates the segment conditions each time retention is viewed and reflects users that match the current conditions. |
| Static Cohort | Select both segment and segment snapshot | Freezes the user list to the point in time when the segment snapshot was created. Even if user status changes later, the set of users reflected does not change. |
Tip
- If you want to see users who currently satisfy the condition in real time -> Dynamic Cohort (select segment only)
- If you want to analyze users based on a specific point in time such as a campaign start date -> Static Cohort (select segment + snapshot)
For how to create segments and segment snapshots, refer to the Segment document.
[Chart] Tab¶
Set how retention results are displayed.
Chart Type¶
| Type | Main Use |
|---|---|
| Table | Displays cohort-specific D+0 to D+N retention values in a table. Suitable for comparing exact values by cohort. |
| Line Chart | Shows the retention decline trend of a specific cohort as a line. Suitable for identifying the retention change pattern by N-day. |
Visualization Details¶
| Item | Description |
|---|---|
| Display Unit | Select user ratio (%) or user count |
Add Summary Statistics¶
When the chart type is 'Table', this feature displays aggregate statistics for the full selected period. You can check statistical values while viewing the retention trend.
| Statistic | Description |
|---|---|
| Total | The sum of all values during the selected period |
| Average | The average value during the selected period |
| Min | The lowest value during the selected period |
| Max | The highest value during the selected period |
Edit Retention¶
- In All Content, click the title of the retention you want to edit to open the edit page.
- Change the settings in the desired tab.
- Click the Save button at the bottom.
Notes & Tips¶
- Period selection matters: Daily cohorts are suitable for detailed analysis, while weekly/monthly cohorts are better for long-term trend analysis.
- If the date range is too short, long-term retention for recent cohorts (such as D+30) may not be calculated.
- D+0 is always 100%. If later values are shown as 0%, it may mean there is no data for that period or the event name is configured incorrectly.
- Retention values are not continuous retention rates. Because the percentage of users who triggered the return event on that specific day is calculated independently, D+3 can be higher than D+1.
- If you set the reference event and return event to the same event, you can measure revisit rate (re-access rate).



