Segment¶

Overview¶

A segment is a feature that classifies users by setting conditions. Through the segment feature, you can classify users and use the created segment snapshot to run targeting campaigns.

You can configure more than 40 attribute conditions provided by default through game SDK integration, and if you use the client log transmission feature, you can use attributes you send yourself to create segments.

What Can You Do?¶

Business/Marketing Users¶

• Combine conditions such as payment amount and access days to define target groups such as whale users and dormant users for campaigns.
• Set snapshot schedules to automatically extract the latest user list every day and connect it to targeting campaigns.
• Create segments based on a specific country or market to easily manage promotion targets by region.

Data Analysts¶

• Use segments as filters for charts, funnels, and retention to isolate specific user cohorts for deeper analysis.
• Fix the snapshot creation time to build a static cohort based on the campaign start date and compare metrics before and after.
• Use the simulation feature to check the expected user count and share before snapshot creation to optimize conditions.

Quick Start¶

If you are creating a segment for the first time, follow the steps below to create your first segment.

1. Enter the Segment menu and click the create button.
2. Select the Project to analyze.
3. Click the Add Attribute Group button to set the attributes and conditions used to classify users.
4. In the right-side Simulation area, click the Calculate button to check the expected user count.
5. Click the Save button at the bottom, then enter the Segment Title and Segment Description to save it as a segment.

Full Features¶

Key Concepts¶

Segment List¶

• Segment deletion is possible only through the account that created that segment. If you delete a segment, targeting campaigns already running with that deleted segment will remain, but you cannot create new snapshots or targeting campaigns.
• If you select segments using the checkboxes on the left side of the list and click the copy button, you can create a new segment by adding new attributes to the conditions configured in that segment.
• Clicking each segment name moves you to the segment detail page.

Segment Details¶

On the segment detail page, you can review the conditions set when the segment was created, create segment snapshots, and use them in targeting campaigns.

Segment Snapshot¶

• A segment snapshot refers to a user list extracted according to the attribute conditions set in the segment. On the segment snapshot tab, you can check the number of users extracted from the created segment.
  • Games with 'Authentication v4' or 'Login Center' applied use the user as the default identifier, so you can view the result of matching all uids and dids based on the extracted users.
    • For games that do not support Hive Membership integration, uid is displayed as 0 across the board.
  • Games with 'Authentication v1' applied use uid as the default identifier, so you can view the result of matching all dids based on the extracted uids.
• Segment snapshot data is synchronized every hour, so the number of extracted users may change each time a snapshot is created.
  • Segment snapshot data is aggregated using data that came in up to 10 minutes past the hour and synchronized at 35 minutes past the hour.
    • When creating a snapshot after 35 minutes past the hour: based on data that came in up to 10 minutes into the creation hour
      • Example: If a snapshot is created at 19:50 on 2026-03-30 -> data that came in up to 19:10 on 2026-03-30
    • When creating a snapshot before 35 minutes past the hour: based on data that came in up to 10 minutes into the previous hour
      • Example: If a snapshot is created at 19:25 on 2026-03-30 -> data that came in up to 18:10 on 2026-03-30
• If you want to create an additional snapshot, click the Add Snapshot button, enter a title, and click the save button.
• Download options
  • Default Option: Downloads a user list consisting of the user, uid, did, and appId fields.
  • Include Additional Info Option: Downloads the user list from the default option together with the attribute values set when the segment was created.
    • When downloading with the include additional info option, the order of displayed attribute fields is the same as the order shown on the segment detail page.
    • If the attribute names of custom attributes sent using the client log transmission feature contain characters other than English letters and numbers (for example, Korean, Japanese, Chinese), they are displayed as field names in the form customInfoProperty1, customInfoProperty2.

Targeting Campaign¶

You can run targeting campaigns for the selected users using created segments and snapshots. For more details, see Targeting.

The targeting campaign feature is currently being integrated.

Create Segment¶

Click the create button on the segment list page to go to the creation page.

Select Project¶

Select User Attributes¶

User attributes refer to the characteristics users have. By selecting attributes and setting detailed conditions, you can extract users that match the configured conditions.

When you click the Add Attribute Group button, an attribute selection popup appears. One segment can have up to 5 attribute groups, and one group can have up to 5 attributes.

The following is a list of attributes that can be checked by default through game SDK integration. Depending on differences in SDK version or if there are no collected logs, some attributes may not appear on the selection screen.

Ad Information

Purchase Information

User Information

• App ID: You can select the appId value issued from App Center.
• User Classification Type: For more details about user classification types, see User > User Classification.
• Hive Ban Status: You can select one of the values below.
  • Ban active
  • Ban lifted
  • No ban history
• did: The issuance range differs by OS.
  • iOS: 100,000,000 or more and 300,000,000 or less, or 1,000,000,001 or more and 5,000,000,000 or less
  • Android: 300,000,001 or more and 700,000,000 or less, or 5,000,000,001 or more and 10,000,000,000 or less
  • Windows: 10,000,000,001 or more and 15,000,000,000 or less
  • MacOS: 15,000,000,001 or more and 20,000,000,000 or less
• uid: Available only for games with 'Authentication v4' or 'Login Center' applied and Hive Membership integration support.
  • For games with 'Authentication v1' applied, uid is set as the default identifier, so you can check it in the segment snapshot without selecting a separate attribute.
• Excluded User: You can select one of the values below.
  • Excluded from metrics: users registered in Settings > Metric Settings > Metric Excluded User Management
  • Included in metrics: all users not registered as excluded

Game Play Information

• Account Level: Available when hive_account_level_change event data has been sent.

Session Information

Access Information

• Dormant Days: Calculated based on the segment creation time. To extract dormant users for a specific past date, you must create the segment directly on that date, and retrospective lookup after that point is not possible.
  • Example: If you select dormant days as 3 or more on April 10 -> users whose last access date is before April 8 are extracted

Push Information

MMP Information

• When an MMP tool is integrated through the game SDK, aggregation is based on the transmitted logs, and attribute values can be selected in the form 'Activity - Media'.
  • Each attribute name is shown according to the MMP integrated in the game.
    • Example: When Airbridge is integrated, it appears as 'Period Airbridge Activity - Media', 'Airbridge Activity - Media'
    • For the kinds of MMP tools that can be integrated in Analytics, see Data > Integration.
  • For games with 'SDK v4' or 'SDK v1 - Login Center' applied, the MMP identifier (customerUserId) is sent by default as playerId, so it can be used together with other attributes.
    • For games using other SDKs, if the MMP identifier (customerUserId) is not set to the Hive user key (UID), linkage with other attributes is limited.
    • When Airbridge is integrated, this is available for games using SDK version v4.25.2.0 or later.
• Reflected from data after March 15, 2025.

Custom Attributes

If you send user attribute logs using the client log transmission feature, custom attributes can be used for segment creation within up to 1 hour after transmission. For more details, refer to Custom User Attribute Definition Log.

Set Attribute Conditions¶

After selecting all attributes you want to use on the attribute selection screen and clicking Confirm, all selected attributes are displayed as one group. If you want to remove or change the selected attributes, you can do so using the trash button or the Add Attribute button.

Numeric Attributes (counts, days, etc.)

If the data type is integer, enter an integer of 1 or more, and if it is float, enter a real number of 0 or more, then select one of the conditions below.

Text Attributes (country, language, etc.)

You can search, view, and select values from the attribute value dropdown. For some attribute values, the original value (for example, KR) may be displayed.

Date Attributes (first access date, etc.)

After selecting a date in the calendar, choose one of the following conditions.

Attributes Starting with "Period" (such as period session count)

You can set an additional period in the condition to use attribute values during a specific period as the condition. Select either Recent Period or Date for the period.

• Recent Period: Specify a relative period by entering the current day or 1 to 365 days. The snapshot user count may vary depending on the time of lookup.
  • Example: Setting a recent period of 1 day -> when queried on April 10, data from April 9 to April 10 is used
• Date: Retrieves attribute values during the set period. The date range is limited to a maximum of 1 year.

Link Between Attributes¶

After setting all desired attributes, select either AND or OR on the left side of the attribute group box to connect all attributes within the group.

When Multiple Values Are Queried¶

Attributes whose names do not start with "Period", such as country or language, are provided based on all attribute values since the user's first access. If multiple values are queried, select one of the options below to set the condition.

Attribute Group Link Conditions¶

If you add two or more attribute groups, you can connect all attribute groups by selecting either AND or OR.

Simulation¶

This feature checks the expected user count and the percentage (%) relative to the total user count before snapshot creation. If the result does not meet expectations, you can identify which condition caused users to be lost.

• The expected user count means the number of users matching the selected attribute conditions after duplicates are removed. Snapshot data is not deduplicated, so it may differ from the actual number of extracted snapshot records.

Simulation procedure

• Once all segment attribute conditions are configured, the Calculate button becomes active.

  • Total user count means the number of users who generated logs at least once in the selected game, after removing duplicates.

• When you click Calculate, summary data for user ratio and detailed user ratio data for each attribute are displayed.

  • Summary

    • User ratio (%) is calculated as (expected user count / total user count) × 100.

  • Details

    • If more than 5 attribute values are selected for a text attribute, only the top 5 are displayed, and the remaining attribute values can be checked using the More button.
    • If one user has multiple attribute values, the sum of user ratios (%) may exceed 100%.

• If you reset the attribute conditions and click Calculate again, you can view data for the reset conditions.

Default Snapshot¶

• Enabled: When the segment is created, a default information snapshot named "Basic Segment" is created, including the playerId, uid, did, and appId fields.
• Disabled: No segment snapshot is created, and if needed, you can create one manually from the segment snapshot page.

Set Segment Snapshot Schedule¶

You can automate segment snapshot creation. There is no limit to the number of schedules you can set.

If you select Enabled and set the period, frequency, and time (based on KST), snapshots are created at the configured time and frequency during the configured period.

The created snapshots can be viewed on the segment detail page - Segment Snapshot tab.

Recommended Segments¶

These are examples of segments often used in Analytics. Try creating custom segments by combining various attribute conditions.

All Game Users¶

• Description: Users who accessed the game at least once since launch.
• Attribute Selection

Newly Acquired Users Within the Last 7 Days¶

• Description: Users newly acquired within the last 7 days.
• Attribute Selection

Users Who Accessed at Least Once in a Specific Country Within the Last Year¶

• Description: Users who accessed at least once in a specific country during the last year.
• Attribute Selection

• Attribute Link: AND
• When multiple values are queried: All Values

Dormant Users for 3+ Days Among Users in a Specific Market¶

• Description: Users who installed the game at least once through a specific market and have not accessed for 3 consecutive days as of the query time.
• Attribute Selection

• Attribute Link: AND
• When multiple values are queried: All Values

Dormant Users for 3+ Days Among Users Who Accessed During a Specific Period¶

• Description: Users who were active during a specific period but have not accessed for 3 consecutive days as of the query time.
• Attribute Selection

• Attribute Link: AND

Notes & Tips¶

• After deleting a segment, you cannot create new snapshots or targeting campaigns with that segment. Be sure to check whether it is in use before deleting.
• Because snapshot data is not deduplicated, the expected user count in the simulation and the actual snapshot record count may differ.
• Segments configured with a "Recent Period" condition will have varying user counts depending on the query time. To analyze fixed users, create a snapshot and use that.
• Segment creation reflects custom user attribute definition logs within up to 1 hour after transmission.
• If you use segments as filters for charts, funnels, or retention, you can analyze metrics by isolating only specific user groups.

Related Menu¶

• Chart - Analyze metrics for specific user groups using segment filters
• Funnel - Analyze conversion rates for specific user groups using segment filters
• Retention - Analyze retention rates for specific cohorts using segment filters
• Dashboard - Add segment-based analysis results to a dashboard for unified management
• Targeting - Run targeting campaigns using segment snapshots