Skip to content

mailbox_attachment_receive

An event that occurs when currency and items attached to mail are claimed for the first time. You can use it to create metrics such as the number of claims, the number of users who claimed, and the amount granted by goods.


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)
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)
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)
mailCategory STRING Indicates the mailbox type. Recorded based on the mailbox type value under which the mail is classified, and can be used to compare mail metrics by type. (Example: DEFAULT)
mailId STRING Indicates the unique ID of the mail. Recorded based on the identifier value issued for each mail item sent, and can be used to build a funnel by linking the mail send, open, and claim events.
senderType STRING Indicates the type of the mail sender. Recorded based on the value that distinguishes the sender type, and can be used to compare metrics for operator sends and system sends separately. (Example: ADMIN, SYSTEM, USER)
senderUserId STRING Indicates the identifier of the sender of the mail. Recorded based on the identifier value of the operator, the system, or the user, depending on senderType, and can be used to compare send and open metrics by sender.
attachmentType STRING Indicates the type of the attachment in the mail. Recorded based on the attachment type value defined by the app, and can be used to compare metrics by type of goods. (Example: ITEM, COUPON, CURRENCY)
attachmentId STRING Indicates the unique ID of the attachment in the mail. Recorded based on the ID value that identifies the actual goods data, such as items and coupons, and can be used to analyze the status of individual goods.
attachmentName STRING Indicates the name of the claimed attachment. Recorded based on the currency or item name value passed by the app, and can be used to compare the amount granted by goods name. (Example: Diamond, Gold)
attachmentQuantity INT(INTEGER) Indicates the quantity of the attachment in the mail. Recorded based on the quantity value of each attachment, and can be used to calculate the total quantity by goods with a sum aggregation.