Event attribute transmission¶

Overview¶

Game event logs consist of required attributes and user-defined attributes. If you link Hive SDK v4, automatically collected attributes will be added without separate transmission.

Required-attribute¶

This attribute must be included when transmitting game event logs.

eventName naming convention¶

It is recommended that the event name used for eventName be written according to the rules below.

• Recommended characters: English letters (a–z, A–Z, case sensitive), numbers (0–9), underscore (_)
• Separator: Words are separated by underscores (_) rather than spaces.
• Format: noun_verb format is recommended as it clearly describes the event.
• Example: item_purchase, level_up, tutorial_complete, stage_start

eventTime format rule (RFC 3339)¶

eventTime follows the format RFC 3339 and must include time zone information.

form:

YYYY-MM-DDTHH:MM:SS[.sss]+HH:MM or YYYY-MM-DDTHH:MM:SSZ

Acceptable examples:

2026-07-20T14:01:01+09:00 (KST, Korea Standard Time)
2026-07-20T05:01:01Z            (UTC)
2026-07-20T14:01:01.123+09:00 (including milliseconds)
2026-07-20T23:01:01-05:00 (US Eastern Time)

Examples not allowed:

2026-07-20 14:01:01 (No time zone → quarantine)
2026-07-20 (No time → Quarantine)
1719835261 (Unix timestamp → quarantine)
14:01:01 (no date → quarantine)

eventTime¶

• eventTime is converted to UTC in the pipeline and stored in the table's dateTime column. The original value is preserved in attributes.eventAttributes.eventTime.

user-defined attribute¶

The information you want to transmit in the game consists of attribute names and attribute values ​​and is transmitted directly along with the required attributes.

Attribute name rules¶

Attribute names that cannot be used (reserved words)¶

Attribute value rules¶

If the attribute value is in the form of an object JSON, an array JSON, or a string in the form of JSON, it is isolated into a table rescue.

// JSON object (not allowed)
"info": {"key": "value"}

// JSON array (not allowed)
"items": [1, 2, 3]

// String of the form JSON (not allowed)
"data": "{\"key\": \"value\"}"

Duplicate transmission of the same attribute name¶

If two or more identical attribute names are transmitted, the attribute value is randomly selected and only one attribute value is stored.

Hive SDK v4 Auto-collected attributes¶

Automatically collected only when a client sends event logs to Hive SDK v4.

• If the user directly sends a value with the same attribute name, the value sent by the user is stored instead of the value automatically collected by SDK.
• The attributes below are stored in attributes.eventAttributes in the table.

If you use the Hive SDK v4 event log transmission feature, these are attributes that the SDK collects and transmits directly from the client device.

Required attributes¶

Among Required attributes, these are attributes that Hive SDK v4 automatically collects. (Excluding eventName)

User/Account Identification Information¶

Time/Identification Information¶

Attribute name	Description	domain	Example
dateTime	This is the date and time of the event generated when transmitting the event log. (yyyy-MM-dd HHss format)	Hive SDK (core)	2026-01-01 00:00:00
guid	UUID (hyphen removed) generated each time an event log is transmitted. Used for unique identification and deduplication of event logs.	Hive SDK (core)	ecbfbd7fcdc340e1b8a433999c5290c1
is_hive_time	Flag whether the timestamp in the event log is Hive synchronized with the server time. (Y/N)	Hive SDK (core)	Y
timezone	dateTime Time zone offset information on which the value is based.	Hive SDK (core)	GMT+09:00
is_url_encode	Flag indicating whether to apply URL encoding when transmitting event logs. (Y fixed)	Hive SDK (core)	Y

Device information¶

SDK/App build information¶

SDK Setting information¶

Receiving server information¶

Precautions & Tips¶

• Required attribute names must be sent in camel case or lowercase, and if sent in snake case (user_id), they will be isolated into the rescue table.
• Must contain either appId or appIdGroup, otherwise it is isolated.
• eventTime is only allowed in the RFC 3339 format (including time zone), and will be quarantined if it exceeds 31 days past or future based on the current time.
• attributes, eventAttributes, and hiveAttributes cannot be used as user-defined attribute names (case is irrelevant).
• Only numeric and character types are allowed as attribute values, and strings in the form of JSON objects, arrays, and JSON are isolated.
• For information on how to check and resend quarantined logs, see Data Isolation.

Related menu¶

• Event transmission — Guide to event/attribute concepts
• Event Template — List of default automatically collected events by category
• Event log transmission — Transmission method via Hive SDK v4, Hive Axyl, Fluentd, HTTP
• Event storage structure — table structure, attributes detailed attributes, data isolation