user_block

An event that occurs when a suspension is applied to a user. You can use it to create metrics such as the number of suspensions applied, the number of suspended users, and the number of suspensions by suspension reason and period.

---

Attribute name	Data type	Description
dateTime	TIMESTAMP	Indicates the date and time when the event occurred. Recorded based on the event time, and can be used as the basis for aggregation by period unit (day/week/month/hour/minute) and date range queries. (Example: 2023-05-09 19:30:35)
eventName	STRING	Indicates the name that identifies the event. Because all events are loaded together into a single source log, this value identifies which event it is, and it can be used as the basis for querying data by event. (Example: app_login)
userId	STRING	Indicates the account-based identifier of the user who triggered the event. Recorded based on the user's unique ID in the app, and can be used to count unique users, such as AU, with a distinct count aggregation.
identifierProvider	STRING	Indicates the system that issued the user identifier. The value is always "hive".
deviceId	STRING	Indicates the device-based identifier of the user who triggered the event. Recorded based on the instance value issued for each device every time the app is installed, and can be used to count unique devices (such as the number of terms agreements) with a distinct count aggregation. (Example: 33333333)
appIdGroup	STRING	Indicates the project where the event occurred. Recorded based on the GAMEID value registered in Hive Console > Project Settings > App ID, and can be used to compare metrics by project when you query multiple projects together. (Example: com.sample.analytics)
blockStart	TIMESTAMP	Indicates the start date and time of the suspension. Recorded based on the sanction start date and time, and can be used for sanction period analysis and time-series queries. (Example: 2026-07-15 15:00:00)
blockEnd	TIMESTAMP	Indicates the end date and time of the suspension. Recorded based on the scheduled sanction end date and time, and can be used for sanction period analysis. (Example: 2026-07-21 16:00:00)
blockPeriod	STRING	Indicates the number of days of the suspension. Recorded based on the number of sanction days, and can be used to compare metrics by sanction period. (Example: 1 (1-day block), -1 (permanent block))
blockType	STRING	Indicates the block method of the suspension. Recorded based on the block method description value, and can be used to compare sanction metrics by block method. (Example: 3-day block, permanent block)
csType	STRING	Indicates the CS request channel of the suspension. Recorded based on the CS request region value, and can be used to compare sanction metrics by request channel. (Example: KR (Korea), GB (global), JP (Japan))
blockCategory	STRING	Indicates the block reason category of the suspension. Recorded based on the block reason description value, and can be used to compare sanction metrics by reason. (Example: use of illegal programs, real-money trading)
blockCategoryType	INT(INTEGER)	Indicates the block reason of the suspension as a numeric code. Recorded based on the reason code value defined for each blocking entity (membership, login center), and can be used to analyze sanction metrics by reason code.