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.

FieldDescription
cidHash of a device MAC-address.
uidUser ID from JWT.
Custom Dimension 1The platform that was used to open the launcher.
Custom Dimension 5Session ID.
ulLauncher language.
Custom DimensionLauncher 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 8Game identifier:
  • ID from Publisher Account, for a standalone launcher.
  • Steam App ID if the launcher is opened via Steam.
anLauncher name.
Custom Dimension 3Launcher project ID.
Custom Dimension 9Login project ID.
avLauncher version.
Custom Dimension 4Launcher build version.
vpLauncher window size.
srScreen resolution.
uaUser agent for detection of user’s operating system.
Custom Dimension 12ID 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 actionEvent categoryTrigger
Successful launchLaunch eventLauncher starts. This is not sent when the launcher is started after an update.
Successful launcher uninstallLauncher uninstallLauncher uninstallation.
Close AppClose eventLauncher closing. This is not sent when the launcher is closed before an update.

UI events

Event actionec (GA)Trigger
Open screenUI EventA user opened a launcher screen. Additional fields:
  • Event Label — a tab type.
  • Event Value — a tab name (for custom tabs).
Push LogoutUI EventA user clicked Log out.
Push BuyUI EventA user clicked one of the following buttons in a standalone launcher:
  • Buy a game package on a game page.
  • Buy an item for virtual currency in a store.
  • Add an item with a price in real currency to the cart in a store.
Additional field: Event Label — an item’s SKU.

Launcher update events

Event actionEvent categoryTrigger
Checking update startLauncher Update EventLauncher starts to check for updates.
Checking update finishLauncher Update EventLauncher 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 updateLauncher Update EventA user skipped the launcher update.
Downloading update startLauncher Update EventLauncher started downloading the update.
Downloading update finishLauncher Update EventLauncher finished downloading the update.
Launcher update readyLauncher Update EventLauncher finished the update.
Launcher update successLauncher Update EventLauncher is updated successfully.

Game ownership events

Event actionEvent categoryTrigger
Game OwnershipOwnershipA change of a game ownership status. Additional field: Event Label — a game ID on a platform.

Content events

Event actionEvent categoryTrigger
Article ViewUI EventMore than 75% of a content was displayed. For the content that has the group status the event is not sent. Additional fields:
  • Custom Dimension 6 — a content type.
  • Custom Dimension 7 — a banner type.
  • Custom Dimension 13 — an ID from Publisher Account or a Steam App ID of the game, the link leads to.
  • Element Label — URL address if the content type is link or video.
Article ClickUI EventA user clicked a content element.

Authorization events

Event actionEvent categoryTrigger
socialAuthorizationA user was successfully authenticated in the launcher via a social network.
phoneAuthorizationA user was successfully authenticated in the launcher via phone (passwordless).
emailAuthorizationA user was successfully authenticated in the launcher via email (passwordless).
xsolla_loginAuthorizationA user was successfully authenticated in the launcher via email and password when the user data storage is Xsolla.
firebaseAuthorizationA user successfully authenticated in the launcher via email and password when the user data storage is Firebase.
playfabAuthorizationA user was successfully authenticated in the launcher via email and password when the user data storage is Playfab.
proxyAuthorizationA user was successfully authenticated in the launcher via email and password when the user data storage is custom.
deviceAuthorizationA user successfully authenticated in the launcher via a device ID.
server_custom_idAuthorizationA user was successfully authenticated in the launcher via a custom ID ( (a user ID generated on your server).
crossAuthorizationA user was successfully authenticated in the launcher via cross-authentication. The event is sent with every launcher start.

How to get it

  1. Sign up for Google Analytics and log in to your account.
  2. Create and edit custom dimensions in Google Analytics as shown in the table below.

IndexNameScope
1PlatformSession
2Is_test. This field is for Xsolla internal use only.Session
3Launcher_idSession
4Launcher build numberSession
5SessionSession
6Article idSession
7Article typeSession
8Active game idSession
9Login project idSession
10Target analytic gameSession
11PAv4 label ID. This field is for Xsolla internal use only.Session
12Game publisher project idSession
13Target game idSession

  1. Click Admin in the side menu.
  2. In the Property section, choose Tracking info > Tracking code and copy your tracking ID.
  3. Open your project in Publisher Account.
  4. Click Launcher in the side menu.
  5. Find the launcher on the dashboard and click Edit launcher.
  6. Go to the Settings > General information > Analytics.
  7. Paste the Tracking ID in the Google Analytics Tracking ID field.
  8. Click Save changes.

Was this article helpful?
Thank you!
Is there anything we can improve? Message
We’re sorry to hear that
Please explain why this article wasn’t helpful to you. Message
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
Is there anything we can improve?

Don’t want to answer

Thank you for your feedback!
Last updated: February 4, 2021

Found a typo or other text error? Select the text and press Ctrl+Enter.

Report a problem
We always review our content. Your feedback helps us improve it.
Provide an email so we can follow up
Thank you for your feedback!