user_block¶
This is an event that occurs when a suspension is applied to a user, and can be used to create metrics such as the number of suspensions applied, the number of suspended users, the reason for suspension, and the number of suspensions by period.
| Attribute name | Data type | Description |
|---|---|---|
| dateTime | TIMESTAMP | Indicates the date and time when the event occurred. It is recorded based on the time of event occurrence, and can be used as a basis for period unit (day/week/month/hour/minute) aggregation and date range searches. (Example: 2023-05-09 19:30:35) |
| eventName | STRING | Indicates a name that identifies the event. Since all events are loaded together in one source log, this value identifies which event it is and can be used as a standard for searching data on an event-by-event basis. (Example: app_login) |
| userId | STRING | Indicates the user identifier based on the account that triggered the event. It is recorded based on the unique user ID in the game, and can be used to count the number of unique users such as AU by deduplicating the number. |
| identifierProvider | STRING | Indicates the user identifier issuance system, and "hive" is fixed. |
| deviceId | STRING | Indicates the user identifier based on the terminal that generated the event. Each time an app is installed, it is recorded based on the instance value issued for each device, and can be used to count the number of unique devices (the number of terms and conditions agreed, etc.) by deduplicating the number. (Example: 33333333) |
| appIdGroup | STRING | Indicates the project where the event occurred. Hive is recorded based on the GAMEID value registered in the console app center, and can be used to compare indicators by dividing them by project when viewing multiple projects together. (Example: com.sample.analytics) |
| blockStart | TIMESTAMP | Indicates the start date and time of suspension. It is recorded based on the sanction start date and time, and can be used for sanction period analysis and time series inquiry. (Example: 2026-07-15 15:00:00) |
| blockEnd | TIMESTAMP | Indicates the end date and time of suspension. It is recorded based on the date and time the sanctions are scheduled to end, and can be used to analyze the sanctions period. (Example: 2026-07-21 16:00:00) |
| blockPeriod | STRING | Indicates the number of days of suspension. It is recorded based on the number of sanction days, and can be used to compare indicators by sanction period. (Example: 1 (block for 1 day), -1 (block permanently)) |
| blockType | STRING | Indicates the blocking method of suspension. It is recorded based on the blocking method description value, and can be used to compare sanction indicators by blocking method. (Example: 3-day block, permanent block) |
| csType | STRING | Indicates the CS request path for suspension. CS is recorded based on the request region classification value, and can be used to compare sanctions indicators by request route. (Example: KR(Korea), GB(global), JP(Japan)) |
| blockCategory | STRING | Indicates the blocking reason category for suspension of use. It is recorded based on the blocking reason explanation value, and can be used to compare sanction indicators for each reason. (Example: use of illegal programs, cash transactions) |
| blockCategoryType | INT(INTEGER) | Indicates the reason for suspension as a numeric code. It is recorded based on the reason code value defined for each blocking entity (membership, login center), and can be used to analyze sanctions indicators by reason code. |