Event¶
Overview¶
Events are the foundation of all Analytics analysis, and this feature lets you view and manage events and attributes created under events.
By integrating the SDK alone, more than 50 events such as login, purchase, and install are automatically collected without additional development. You can also define and add the events you need for more precise analysis.
For sending custom events directly, refer to the Event Design and Transmission Guide.
What Can You Do?¶
Business/Marketing Users¶
- If you define the events and attributes needed for analysis on this screen, you can use it directly as a planning document to hand off to the development team.
- By reviewing the list of currently collected events at a glance, you can immediately see what data is available for analysis.
Data Analysts¶
- Reviewing the full set of analyzable events and attributes in the event list helps you quickly design your analysis scope.
- You can verify data quality before analysis by checking the actual values in the data preview.
Developers¶
- You can efficiently proceed with SDK integration by checking the event names and attribute lists directly on this screen.
- After sending events, you can immediately verify the transmission result by checking the received attribute values in Data Preview.
- The ETL Simulation feature lets you preview event transmission results before actual deployment.
Quick Start¶
If you are registering an event for the first time, follow the steps below to create your first event.
- Click Data > Event in the left sidebar.
- Click the Register button in the top right.
- Enter the event name and event description.
- Go to the Attribute tab and add the attributes to send with the event.
- Set the attribute name, description, and data type.
- Click the Save button.
- Send the event name and attribute list to the development team and request event data transmission.
Note
For detailed settings such as event attributes, data preview, and ETL simulation, refer to Full Features.
Full Features¶
Key Concepts¶
| Concept | Description |
|---|---|
| Event | A unit of recorded data for a specific action performed by a user in the game (for example, login, purchase, level up) |
| Platform Event | An event collected by Hive by default through SDK integration only |
| MMP Event | Events sent through MMPs such as Airbridge, AppsFlyer, and Adjust |
| Custom Event | A custom event defined and sent directly |
| Attribute | A detailed data item attached to an event in the event taxonomy structure. Divided into platform attributes and event attributes |
| Platform Attribute | An attribute collected by Hive by default through SDK integration only (for example, country, market, server ID, OS) |
| Event Attribute | An attribute sent together with the event (for example, item ID, amount, or currency unit for a purchase event) |
View Event List¶
View all events registered in Analytics. 
Filters and Search¶
| Option | Description |
|---|---|
| Event Type | Filter the list by event type (custom event, AppsFlyer, Airbridge, etc.) |
| Search Event Name/Creator | Select the search criterion (event name or creator) and enter a search term to search events |
| Show Only In Use Events | When toggled ON, shows only events marked as in use |
List Columns¶
| Column | Description |
|---|---|
| No. | Event registration order |
| Event Type | Source of the event, such as custom event / AppsFlyer / Airbridge |
| Event Name | Event name. Click to open the detail page |
| Description | Description entered when the event was registered |
| Created At | The date and time when the event was first registered |
| Creator | Account that registered the event. System-generated events are displayed as system |
| Last Data Ingested At | The last date and time when data for the event was collected. Synchronized every 10 minutes, and shown as - if there is no collection history |
| In Use | Toggle to enable/disable the event. When OFF, the event is hidden from the selection list in charts/funnels/retention |
Register Event¶
Click the Register button in the top right of the event list screen to move to the event registration page. 
| Item | Required | Description |
|---|---|---|
| Event Name | Required | Unique code used when actually sending data |
| Description | Optional | Description of the event's occurrence conditions and purpose |
Note
For Analytics' recommended event name naming rules, refer to the Event Design and Transmission Guide.
View Event Details¶
[Basic Info] Tab¶
View and edit the registered event name and description. 
[Attribute] Tab¶
Define the attributes sent together with each event. 
| Item | Description |
|---|---|
| Attribute Name | Code used during actual transmission |
| Description | Meaning and example of the attribute value |
| Data Type | Choose one of text / number / date |
Data Type Description¶
| Type | Description | Example |
|---|---|---|
| Text | String value | Country code(KR), item name(sword) |
| Number | Integer or decimal value | Level(50), payment amount(9.99) |
| Date | Date/time value | Event occurrence time(2026-03-29T10:00:00) |
Currency Attribute / Money Attribute¶
Among the attributes registered for an event, you can designate the attribute that contains the currency value and the revenue amount. You must configure this setting to view revenue values in Chart using the desired currency basis.
| Item | Description |
|---|---|
| Currency Attribute | Specify the attribute containing currency code values (for example, an attribute with currency units such as KRW or USD) |
| Money Attribute | Specify the attribute containing the numeric value used for revenue calculation (for example, an attribute containing the payment amount) |
Note
Currency attributes and money attributes can be set in the [Attribute] tab of the event detail page. Select the attribute from the list and assign each item.
Warning
If a currency attribute or money attribute is not specified, revenue-related metrics cannot be viewed in charts using a currency basis. To use purchase events in analysis, you must specify both attributes.
[Data Preview] Tab¶
View sample event data actually collected in Analytics. Use this to verify whether events are being sent correctly and whether attribute values are being collected as intended.
Query Conditions¶
| Item | Description |
|---|---|
| Query Period | Select the date range for the data query. The range between the start and end dates is limited to a maximum of 1 month. |
| Field Name | Select the attribute(field) to apply the filter to. |
| Condition | Select the comparison condition to apply to the chosen field. |
| Search | Enter the value to use for the condition. |
| Reset | Reset all configured filter conditions. |
Warning
If the query period exceeds 1 month, the data cannot be retrieved. Reduce the period and query again.
[Source Generation] Tab¶
Automatically generates source code for sending the event to Analytics. Developers can send data using the source generated in this tab without writing code separately. 
| Tab | Description |
|---|---|
| Client Developer | Provides source code for sending events from the game client |
| Server Developer | Provides source code for sending events from the game server |
| Documentation | Provides reference documentation for the event collection table schema |
[ETL Simulation] Tab¶
A simulation feature for testing event transmission.
- Enter appropriate data into each event collection table field.
- Click the Send button.
- In the [Data Preview] tab, check whether the event was received and whether attributes were parsed correctly.
Warning
You must enter an app ID registered in Hive Console > App Center in the appId field. If you enter an incorrect value, data may not be collected.
Control Event Display¶
- Use the In Use toggle in the event list to control whether each event is visible. - If set to OFF, the event will be hidden from the selection list in analysis screens such as charts, funnels, and retention. - Data continues to be collected, but it will not be visible in the analysis UI.
Copy and Delete Events¶
- Copy: Quickly create a similar event based on an existing event
- Delete: Delete events that are no longer used
Warning
If there are charts or metrics using a deleted event, those contents may be affected.
Notes & Tips¶
- If you change an event name after release, it will no longer match past data. Choose event names carefully.
- Incorrectly configured attribute types can cause aggregation errors.
- To use MMP events, you must first configure the corresponding MMP integration in the Data > Integration menu.
- Mark unused events as Display OFF to keep the analysis UI clean.
- As the number of events increases, clearly written names and descriptions improve analysis efficiency for the entire team.
Related Menu¶
- Event Design and Transmission Guide - Detailed guide to event collection structure and schema
- Metric - Save frequently used event aggregation settings as metrics
- Chart - Create charts based on events
- Funnel - Configure funnel stages based on events
- Retention - Set up cohorts and retention measurement based on events
- Integration - Configure third-party integrations for using MMP events