Skip to content

push_open

This is an event that occurs when a push notification is clicked and the app is entered, and can be used to create metrics such as the number of push opens, number of users who open a push, type of push, and number of opens by campaign.


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)
appId STRING Indicates the unique ID of the app where the event occurred. Hive is recorded based on APPID registered in the console app center, and can be used to distinguish indicators for each app. (Example: com.sample.analytics.google.global.android.common)
country STRING Indicates the country of the user identified at the time the event occurred. ISO 3166-1 alpha-2 It is recorded in uppercase format and can be used to compare the number of users, sales, retention, etc. by country. (Example: KR, US)
serverId STRING Indicates the game server the user connected to when the event occurred. It is recorded based on the server identifier sent by the game, and can be used to compare the number of users, sales, and retention by server. (Example: KR, GLOBAL)
model STRING Indicates the model name of the user terminal at the time the event occurred. It is recorded based on the terminal model value sent by the client, and can be used to compare indicators by device model. (Example: iPhone 12 Pro, SHW-M250S)
appVer STRING Indicates the game app version at the time the event occurred. It is recorded based on app version information, and can be used with the os attribute to compare users by app version. (e.g. 4.3.3, 1.6.5)
market STRING Indicates the market where the user installed the game when the event occurred. It is recorded based on the market value where the app is installed or serviced, and can be used to compare indicators by market. (Example: GO(Google Play), AP(Apple App Store), HS(direct distribution))
lang STRING Indicates the language value at the time the event occurred. It is recorded based on the game or device language value (ISO 639 alpha-2 lowercase), and can be used to compare indicators by language. (Example: ko, en)
os STRING Indicates the operating system of the user terminal at the time the event occurred. It is recorded based on the platform value sent by the client, and can be used to compare indicators by OS. (Example: A(Android), I(iOS))
sdkVer STRING Indicates the Hive SDK version at the time the event occurred. It is recorded based on the Hive SDK version value applied to the client, and can be used to compare the data collection status by SDK version. (Example: 4.16.2.2)
campaignTimezone STRING Indicates the target time zone for the push campaign. Push campaigns are recorded based on the targeted time zone value, and can be used to compare push indicators by time zone. (Example: Asia/Seoul)
campaignId INT(INTEGER) Represents the unique ID in the push campaign. It is recorded based on the identifier value issued on a per-campaign basis, and can be used to compare sending and open indicators for each campaign. (Example: 36851)
pushSendDateTimeKst TIMESTAMP Indicates the sending time (Korean time) of the push campaign. It is recorded based on the campaign round sending time value, and can be used to distinguish campaign rounds or compare open times compared to sending. (Example: 2026-07-21 05:00:00)
pushType STRING Indicates the type of push. It is recorded based on single, large volume, and targeting values, and can be used to compare sending and open indicators by push type. (Example: A(single), B(bulk), T(targeting))
messageId STRING Indicates the unique identifier of the push sending attempt. It is recorded based on the value issued by the push server for each sending attempt, and can be used to analyze the number of sends, send success rate, and open conversion by linking send and open events.