Connecting analytics services

Glossary

Event
User action that sends information to Google Analytics 4.
Event category
Special parameter event_category, the value of which is passed when sending events from sites created with Site Builder. Parameter values are names of the site blocks.
Event label
Special parameter event_label, the value of which is passed when sending events from sites created with Site Builder. The parameter values ​​are additional information that refines the events.
Description
A description of the user action upon completion of which the event is sent to the Google Analytics system.

How it works

Connect analytics to track events related to user actions on your site and payment UI events. The Site Builder supports automatic integration with the Google Analytics service, with the ability to receive advanced analytics of site events and payment interface. In addition, you can connect any other analytics service using Google Tag Manager and receive an extended list of events for your website and payment interface. You can set up analytics with:

All events that can be tracked on your site are listed in the Events section.

Google Analytics connection

Note
Events that can be tracked on your site using Google Analytics are listed in the Extended List of Events section.

  1. Create a Google Analytics account with the Google Analytics 4 resource type.

  1. Get service ID:
    1. In the sidebar, choose Admin.
    2. On the Admin tab, choose the account and resource.
    3. Go to the Data Streams tab.
    4. Click the data stream.
    5. Copy Measurement ID.
  1. Open your project in Publisher Account.
  2. In the side bar click Site Builder.
  3. Select your site and click Configure.
  1. Go to the Apps section, and in the Google Analytics block, click Connect.
  1. In the modal window, specify the analytics service ID and click Connect.
  2. In the modal window, click Publish.
Note
If site publication is not available, make sure all the required conditions are met:
  • There are no empty sections in Builder (marked with a red dot).
  • The Licensing Agreement with Xsolla has been signed.
  • A section for user authorization has been added to the site.

Registration of event parameters

Register event parameters to see them in your analytics.
You can specify events in analytics using parameters:

  • The event_category parameter allows you to determine from which block the event was sent.
  • The event_label parameter contains the value of the event, such as the product SKU, payment method, and others.

To registrate event parameters:

  1. In the sidebar, choose Admin.
  2. On the Admin tab, go to Custom definition.
  3. Click Create custom definition.
  4. In the Definition name field, enter the name of the parameter you want to see when setting up the event funnel.
    Example: Category.
  5. In the drop-down Scope list, choose Event.
  6. In the Description field, enter a description (optional).
  7. In Event parameter field, enter the parameter name:
    • event_category — when registering the Category parameter;
    • event_label — when registering the Label parameter.
  8. Click Save.

Connecting other analytics services

  1. Create an account with your chosen analytics service.
  2. Create a Google Tag Manager account (GTM account).

  1. Set up a GTM account for your analytics system:
    1. Set up tags.
    2. Set up events and settings.
    3. Publish changes to GTM.
  2. In your Publisher Account, go to Site Builder.
  3. In the Sites section, select your site and click Configure.
  4. Go to the Apps section and in the Google Tag Manager block, click Connect.
  1. Specify the GTM container ID and click Connect. To find the container ID, use the instruction in the How to get your ID input box.
  1. Click Connect.
  2. In the modal window, click Publish.

Events

Payment UI events

Event nameEvent categoryEvent labelDescription
openPaystation_landingstateOpening the payment UI page. The name of the page is passed as the Label parameter.
closePaystation_landingstateClosing the payment UI page. The name of the page is passed as the Label parameter.
sharePaystation_landingnameClicking the button to share. The name of the social network is passed as the Label parameter.
payment_method&shy_namePaystation_landingpayment_method_namePressing the Pay Now button on the payment data entry form. The name of the selected payment method is passed as the Label parameter.
choose-widgetPaystation_landingpayment_widget_nameClicking on the payment method widget. The name of the widget is passed as the Label parameter.
choose-methodPaystation_landingpayment_method_nameChoice of payment method.The name of the payment method is passed as the Label parameter.
change-statusPaystation_landingstatusChange of payment status. If the user closes the page or payment UI and the status changes after it is closed, no event message is sent. The payment status is passed as the Label parameter (created, error, successful, etc.).
purchase-successPaystation_landingdoneSuccessful payment. Similar to the event Change of payment status, but only sent if the status is done.

Header block events

Event nameEvent categoryEvent labelDescription
click-loginHeader_landing–Clicking on the login button.
open-loginHeader_landing–Opening the authorization widget when the authorization button is clicked.
open-uid-widgetHeader_landing–Opening the ID input widget when clicking on the authorization button.
click-buyHeader_landingskuClicking on the buy button. The product SKU is passed as the Label parameter.
click-googleplayHeader_landing–Clicking on a button with a Google Play link.
click-appstoreHeader_landing–Clicking on a button with an App Store link.

User ID input widget events

Event nameEvent categoryEvent labelDescription
closeUID_widget_landing–Closing the modal ID input window.
inputUID_widget_landing–Start entering a value in the ID input field.
confirmUID_widget_landing–Pressing the ID confirmation button.
click-instructionUID_widget_landing–Clicking on a collapsed instruction.
errorUID_widget_landing–Identification error (invalid ID).
success_idUID_widget_landing–Successful identification.

Packs block events

Event nameEvent categoryEvent labelDescription
click-buyPacks_landingskuClicking on the buy button. In the Label parameter, the product SKU is passed.
open-loginPacks_landing–Opening the authorization widget when the buy button is clicked.
open-uid-widgetPacks_landing–Opening the ID input widget when the buy button is clicked.
click-googleplayPacks_landing–Clicking on a button with a Google Play link.
click-appstorePacks_landing–Clicking on a button with an App Store link.

Promo slider ​block events

Event nameEvent categoryEvent labelDescription
click-buyPromo_landingskuClicking on the buy button on the slide. In the Label parameter, the product SKU is passed.
open-loginPromo_landing–Opening the authorization widget when the buy button on the slide is clicked.
open-uid-widgetPromo_landing–Opening the ID input widget when clicking on the buy button on the slide.
click-googleplayPromo_landing–Clicking on a button with a Google Play link on a slide.
click-appstorePromo_landing–/landing_click-appstore
enter-emailPromo_landing–Clicking on the confirmation email button to subscribe to the newsletter.

Store block events

Event nameEvent categoryEvent labelDescription
authStore_landing_buy&shy_button-Opening the authorization modal window after a user clicks the buy button.
open-psStore_landing_buy&shy_buttonskuInitializing the payment interface after a user clicks the buy button in an item card. The product SKU is passed in the Label parameter.
authStore_landing_pop-up-Opening the authorization modal window after an unauthorized user clicks the buy button in an item modal window.
openStore_landing_pop-upskuOpening the item card modal window after the user clicks the card.
open-psStore_landing_pop-upskuInitializing the payment interface after an unauthorized user clicks the buy button in an item modal window.

Call-to-action block events

Event nameEvent categoryEvent labelDescription
click-buyCTA_landingskuClicking on the buy button. In the Label parameter, the product SKU is passed.
open-loginCTA_landing–Opening the authorization widget when the buy button is clicked.
open-uid-widgetCTA_landing–Opening the ID input widget when clicking on the buy button.
enter-emailCTA_landing–Clicking on the confirmation email button to subscribe to the newsletter.
Event nameEvent categoryEvent labelDescription
socialFooter_landingnameClicking on the social network button. The name of the social network is passed as the Label parameter.
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: March 4, 2024

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!