SDK Events
The SDK events encompass basic authentication data, as well as performance and troubleshooting related events, which are automatically collected and reported once the Player Network SDK is integrated.
These events are reported for the purpose of account analysis related to login authentication.
| Level 1 event name l1_event_name | Level 2 event name l2_event_name | Description | Remark |
|---|---|---|---|
| start | app_launch | Player Network SDK initialization | For PC devices, the Launcher is usually launched before entering the game. If Player Network SDK is integrated with the Launcher and also within the game, the app_launch event will be reported twice. |
| auth | confirm_login_channel | Selecting a login channel (such as LI PASS email verification, Facebook channel, etc.) includes events like automatic login, cached login, and registration events. | Reported when calling the following interfaces in the Player Network SDK Auth module: AutoLogin, Login, Register, LoginUsePluginCache, AutoLoginForLI, LoginForLI |
| auth | channel_auth_success | Channel login success, preparing to initiate a login request to the backend, includes login and automatic login events. | Reported before Player Network SDK initiates network requests to the backend (auth/login, auth/auto_login).Problems with missed reporting have been fixed in Player Network SDK V1.18.01 and later. |
| auth | login_auth_success | Successful receipt of a backend callback, includes login and automatic login events. | Reported when Player Network SDK receives a backend callback, where the outcome can be confirmed through error_code, error_code = 0 indicates success. |
| auth | register_success | Registration process, successful receipt of a backend callback. | When reporting login_auth_success, check the first_login field in the local login state, and if confirmed to be logging in for the first time, additionally report register_success.This parameter is supported in Player Network SDK V1.18.01 and later. |
Data tables
As each event is reported to different tables, the attributes of each event align with the structure of the data table to which they are reported.SDK events, for example, are reported to the following data tables.
insight_1000_funnel
This table is mainly used for funnel analysis, primarily refers to game funnel events.
| Name | Type | Description |
|---|---|---|
| intl_common_info | intl_comm_info | Common fields |
| l1_event_name | string | Level 1 event |
| l2_event_name | string | Level 2 event |
| stage_time | bigint | Stage duration |
| error_code | bigint | Stage error code (as defined by the game) |
insight_1000_http
This table is mainly used for network request events, which records all HTTP request events related to the Player Network SDK, used for troubleshooting network issues.
| Name | Type | Description |
|---|---|---|
| intl_common_info | intl_comm_info | Common fields |
| seq_id | string | Log tracking ID |
| url | string | Request URL |
| response_body | string | Return Package Meaningful only when stage=end. |
| ret_code | string | Player Network SDK error code See intl_error.h for more details, only meaningful when stage=end. |
| third_code | string | Third-party Return Error Code Meaningful only when stage=end. |
| issue_time | string | Request Duration Statistics by Network Library Meaningful only when stage=end. |
| stage | string | Interface Call Status begin: indicates start request end: indicates request end |
insight_1000_plugin
This report is primarily used to log plugin events and report plugin information for the Player Network SDK, such as the plugin version of Facebook, X, Adjust, WebView, and other plugins.
| Name | Type | Description |
|---|---|---|
| intl_common_info | intl_comm_info | Common fields |
| intl_plugin_name | string | Player Network SDK plugin name |
| intl_plugin_version | string | Player Network SDK plugin version |
| intl_thirdsdk_name | string | Third-party SDK name |
| intl_thirdsdk_version | string | Third-party SDK version |
