How to send data to Google Analytics
How it works
When you receive data about users’ activity and the launcher’s behavior from Google Analytics as events, the data is sent in the payload as listed in the table below.
| Field | Description |
|---|---|
| cid | Hash of a device MAC-address. |
| uid | User ID from JWT. |
| Custom Dimension 1 | The platform that was used to open the launcher. |
| Custom Dimension 5 | Session ID. |
| ul | Launcher language. |
| Custom Dimension | Launcher screen. Possible values: Starting screen, Login screen, Game screen, Game store screen, Game news screen, Opened content screen, Settings screen, Custom tab screen. |
| Custom Dimension 8 | Game identifier:
|
| an | Launcher name. |
| Custom Dimension 3 | Launcher project ID. |
| Custom Dimension 9 | Login project ID. |
| av | Launcher version. |
| Custom Dimension 4 | Launcher build version. |
| vp | Launcher window size. |
| sr | Screen resolution. |
| ua | User agent for detection of user’s operating system. |
| Custom Dimension 12 | ID from Publisher Account of the game to which the content is related. The field will be empty if the content is not game-related. |
The tables below show information about additional fields for certain events. All outgoing events are grouped based on their type.
General events
| Event action | Event category | Trigger |
|---|---|---|
| Successful launch | Launch event | Launcher starts. This is not sent when the launcher is started after an update. |
| Successful launcher uninstall | Launcher uninstall | Launcher uninstallation. |
| Close App | Close event | Launcher closing. This is not sent when the launcher is closed before an update. |
UI events
| Event action | ec (GA) | Trigger |
|---|---|---|
| Open screen | UI Event | A user opened a launcher screen. Additional fields:
|
| Push Logout | UI Event | A user clicked Log out. |
| Push Buy | UI Event | A user clicked one of the following buttons in a standalone launcher:
Event Label — an item’s SKU. |
Launcher update events
| Event action | Event category | Trigger |
|---|---|---|
| Checking update start | Launcher Update Event | Launcher starts to check for updates. |
| Checking update finish | Launcher Update Event | Launcher finished checking for updates. The additional ev field has the update_found value if there is a newer version found on CDN. Otherwise, the value is no_updates. |
| Skipping launcher update | Launcher Update Event | A user skipped the launcher update. |
| Downloading update start | Launcher Update Event | Launcher started downloading the update. |
| Downloading update finish | Launcher Update Event | Launcher finished downloading the update. |
| Launcher update ready | Launcher Update Event | Launcher finished the update. |
| Launcher update success | Launcher Update Event | Launcher is updated successfully. |
Game ownership events
| Event action | Event category | Trigger |
|---|---|---|
| Game Ownership | Ownership | A change of a game ownership status. Additional field: Event Label — a game ID on a platform. |
Content events
| Event action | Event category | Trigger |
|---|---|---|
| Article View | UI Event | More than 75% of a content was displayed. For the content that has the group status the event is not sent. Additional fields:
|
| Article Click | UI Event | A user clicked a content element. |
Authorization events
| Event action | Event category | Trigger |
|---|---|---|
| social | Authorization | A user was successfully authenticated in the launcher via a social network. |
| phone | Authorization | A user was successfully authenticated in the launcher via phone (passwordless). |
| Authorization | A user was successfully authenticated in the launcher via email (passwordless). | |
| xsolla_login | Authorization | A user was successfully authenticated in the launcher via email and password when the user data storage is Xsolla. |
| firebase | Authorization | A user successfully authenticated in the launcher via email and password when the user data storage is Firebase. |
| playfab | Authorization | A user was successfully authenticated in the launcher via email and password when the user data storage is Playfab. |
| proxy | Authorization | A user was successfully authenticated in the launcher via email and password when the user data storage is custom. |
| device | Authorization | A user successfully authenticated in the launcher via a device ID. |
| server_custom_id | Authorization | A user was successfully authenticated in the launcher via a custom ID ( (a user ID generated on your server). |
| cross | Authorization | A user was successfully authenticated in the launcher via cross-authentication. The event is sent with every launcher start. |
How to get it
- Sign up for Google Analytics and log in to your account.
- Create and edit custom dimensions in Google Analytics as shown in the table below.
| Index | Name | Scope |
|---|---|---|
| 1 | Platform | Session |
| 2 | Is_test. This field is for Xsolla internal use only. | Session |
| 3 | Launcher_id | Session |
| 4 | Launcher build number | Session |
| 5 | Session | Session |
| 6 | Article id | Session |
| 7 | Article type | Session |
| 8 | Active game id | Session |
| 9 | Login project id | Session |
| 10 | Target analytic game | Session |
| 11 | PAv4 label ID. This field is for Xsolla internal use only. | Session |
| 12 | Game publisher project id | Session |
| 13 | Target game id | Session |
- Click Admin in the side menu.
- In the Property section, choose Tracking info > Tracking code and copy your tracking ID.
- Open your project in Publisher Account.
- Click Launcher in the side menu.
- Find the launcher on the dashboard and click Edit launcher.
- Go to the Settings > General information > Analytics.
- Paste the Tracking ID in the Google Analytics Tracking ID field.
- Click Save changes.
Was this article helpful?
Thank you for your feedback!
We’ll review your message and use it to help us improve your experience.Rate this page
Rate this page
Don’t want to answer
Thank you for your feedback!
Found a typo or other text error? Select the text and press Ctrl+Enter.
