Skip to content

push_send

An event that occurs when the Hive push server requests a push send from a push platform (such as APNs or FCM) and receives a response. You can use it to create metrics such as the number of send requests by push type and campaign, the send request success rate, and the distribution by failure reason.

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)
appId STRING Indicates the unique ID of the app where the event occurred. Recorded based on the APPID registered in Hive Console > Project Settings > App ID, and can be used to distinguish metrics by app. (Example: com.sample.analytics.google.global.android.common)
serverId STRING Indicates the app server the user was connected to when the event occurred. Recorded based on the server identifier sent by the app, and can be used to compare the number of users, revenue, and retention by server. (Example: KR, GLOBAL)
market STRING Indicates the market where the user installed the app when the event occurred. Recorded based on the market where the app is installed or serviced, and can be used to compare metrics by market. (Example: GO (Google Play), AP (Apple App Store), HS (direct distribution))
os STRING Indicates the operating system of the user's device when the event occurred. Recorded based on the platform value sent by the client, and can be used to compare metrics by OS. (Example: A (Android), I (iOS))
appVer STRING Indicates the app version when the event occurred. Recorded based on the app version information, and can be used with the os attribute to compare users by app version. (Example: 4.3.3, 1.6.5)
sdkVer STRING Indicates the Hive Axyl SDK version when the event occurred. Recorded based on the Hive Axyl SDK version applied to the client, and can be used to compare data collection status by SDK version. (Example: 1.0.0)
model STRING Indicates the model name of the user's device when the event occurred. Recorded based on the device model value sent by the client, and can be used to compare metrics by device model. (Example: iPhone 12 Pro, SHW-M250S)
country STRING Indicates the user's country identified when the event occurred. Recorded in ISO 3166-1 alpha-2 uppercase format, and can be used to compare the number of users, revenue, retention, and so on by country. (Example: KR, US)
lang STRING Indicates the language value when the event occurred. Recorded based on the app or device language (ISO 639 alpha-2, lowercase), and can be used to compare metrics by language. (Example: ko, en)
pushSendPlatform STRING Indicates the remote push platform used to send the push. Recorded based on the platform value called by the Hive Notification server, and can be used to compare send success rates and failure reasons by platform. (Example: APNs, FCM, ADM)
messageId STRING Indicates the unique identifier of a push send attempt. Recorded based on the value the push server issues for each send attempt, and can be used to link send and open events to analyze the number of sends, the send success rate, and open conversion.
pushType STRING Indicates the type of push. Recorded based on the value that distinguishes single, bulk, and targeting pushes, and can be used to compare send and open metrics by push type. (Example: A (single), B (bulk), T (targeting))
campaignId STRING Indicates the unique ID of the push campaign. Recorded based on the identifier issued for each campaign, and can be used to compare send and open metrics by campaign. (Example: 36851)
campaignTimezone STRING Indicates the target time zone of the push campaign. Recorded based on the time zone the push campaign targeted, and can be used to compare push metrics by time zone. (Example: Asia/Seoul)
isSendSuccess STRING Indicates whether the send request to the push platform succeeded. Recorded based on whether the response code is 200, and can be used to calculate the send request success rate. (Example: Y (send request succeeded), N (failed), U (no response received))
sendResultCode INT(INTEGER) Indicates the response code of the push platform. Recorded based on the status code returned by the push platform (such as APNs, FCM, or ADM), and can be used to calculate the success and failure rates of push send requests. (Example: 200 (send request succeeded))
sendFailMessage STRING Indicates the failure reason of the push send. Recorded based on the failure message returned by the push platform, and can be used to analyze the number of sends by failure reason.
sendLatencyMs INT(INTEGER) Indicates the time (in milliseconds) from the push platform call to the receipt of the response. Recorded based on the response receipt time minus the call time, and can be used to analyze send latency with average and maximum aggregations.