Connecting analytics services
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:
- Google Analytics (automatic integration)
- Another analytics service (requires setting up Google Tag Manager)
All events that can be tracked on your site are listed in the Events section.
Glossary
Description
A description of the user action upon completion of which the event is sent to the Google Analytics system.
Category
Part of the event structure in the Google Analytics system. Represents a site block or modal window the user interacts with. One category can contain multiple actions.
Action
Part of the event structure in the Google Analytics system. Represents an action performed by the user. One action can have multiple labels.
Label
Part of the event structure in the Google Analytics system. Represents an optional value that specifies the event. For example, an event with a
change-status action, can have label done (successful transaction) and error (transaction error).Virtual page
The name of the virtual page that corresponds to the event. Required to build funnels in Google Analytics.
Google Analytics connection
Notice
Site Builder does not currently support automatic integration with Google Analytics 4. You can connect Google Analytics 4 by setting up Google Tag Manager.
- In your Publisher Account, go to Site Builder.
- In the Sites section, select your site and click Configure.
- Go to the Apps section, and in the Google Analytics block, click Connect.
- In the modal window, specify the analytics service ID and click Connect. To find the service ID, use the instruction in the How to get your ID identifier entry window.
- Click Connect.
- In the modal window, click Publish.
Connecting other analytics services
- Create an account with your chosen analytics service.
- Create a Google Tag Manager account (GTM account).
- Set up a GTM account for your analytics system:
- Set up tags.
- Set up events and settings.
- Publish changes to GTM.
- In your Publisher Account, go to Site Builder.
- In the Sites section, select your site and click Configure.
- Go to the Apps section and in the Google Tag Manager block, click Connect.
- 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.
- Click Connect.
- In the modal window, click Publish.
Events
Payment UI events
Note
Category for all payment UI events is
Paystation_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| open | Opening the payment UI page. The name of the page is passed as the Label parameter. | state | /landing_paystation_open |
| close | Closing the payment UI page. The name of the page is passed as the Label parameter. | state | /landing_paystation_close |
| share | Clicking the button to share. The name of the social network is passed as the Label parameter. | name | /landing_paystation_click-btn-share |
| payment_method_name | Pressing the Pay Now button on the payment data entry form. The name of the selected payment method is passed as the Label parameter. | payment_method_name | /landing_paystation_click-btn-pay |
| choose-widget | Clicking on the payment method widget. The name of the widget is passed as the Label parameter. | payment_widget_name | /landing_paystation_choose-payment-widget |
| choose-method | Choice of payment method.The name of the payment method is passed as the Label parameter. | payment_method_name | /landing_paystation_choose-method |
| change-status | Change 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.). | status | /landing_paystation_change-status |
| purchase-success | Successful payment. Similar to the event Change of payment status, but only sent if the status is done. | done | /landing_success_purchase |
Header block events
Note
Category for all Header block events is
Header_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| click-login | Clicking on the login button. | – | /landing_header_click-login-open |
| open-login | Opening the authorization widget when the authorization button is clicked. | – | /landing_open-login |
| open-uid-widget | Opening the ID input widget when clicking on the authorization button. | – | /landing_open-uid-widget |
| click-buy | Clicking on the buy button. The product SKU is passed as the Label parameter. | sku | /landing_click-buy |
| click-googleplay | Clicking on a button with a Google Play link. | – | /landing_click-googleplay |
| click-appstore | Clicking on a button with an App Store link. | – | /landing_click-appstore |
User ID input widget events
Note
Category for all User ID input widget events is
UID_widget_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| close | Closing the modal ID input window. | – | /landing_uid-widget_close |
| input | Start entering a value in the ID input field. | – | /landing_uid-widget_input-userid-start |
| confirm | Pressing the ID confirmation button. | – | /landing_uid-widget_input-userid-confirm |
| click-instruction | Clicking on a collapsed instruction. | – | /landing_uid-widget_click-instruction |
| error | Identification error (invalid ID). | – | /landing_uid-widget_error |
| success_id | Successful identification. | – | /landing_uid-widget_success |
Packs block events
Note
Category for all Packs block events is
Packs_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| click-buy | Clicking on the buy button. In the Label parameter, the product SKU is passed. | sku | /landing_click-buy |
| open-login | Opening the authorization widget when the buy button is clicked. | – | /landing_open-login |
| open-uid-widget | Opening the ID input widget when the buy button is clicked. | – | /landing_open-uid-widget |
| click-googleplay | Clicking on a button with a Google Play link. | – | /landing_click-googleplay |
| click-appstore | Clicking on a button with an App Store link. | – | /landing_click-appstore |
Promo slider block events
Note
Category for all Promo slider block events is
Promo_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| click-buy | Clicking on the buy button on the slide. In the Label parameter, the product SKU is passed. | sku | /landing_click-buy |
| open-login | Opening the authorization widget when the buy button on the slide is clicked. | – | /landing_open-login |
| open-uid-widget | Opening the ID input widget when clicking on the buy button on the slide. | – | /landing_open-uid-widget |
| click-googleplay | Clicking on a button with a Google Play link on a slide. | – | /landing_click-googleplay |
| click-appstore | Clicking on a button with an App Store link on a slide. | – | /landing_click-appstore |
| enter-email | Clicking on the confirmation email button to subscribe to the newsletter. | – | /landing_input-subscribe-confirm (ex Subscribe) |
Store block events
Buy button events
Note
Category for all Store block events that connect with the buy button is
Store_landing_buy_button.| Action | Description | Label | Virtual page |
|---|---|---|---|
| auth | Opening the authorization modal window after a user clicks the buy button. | - | /store_landing_buy_button_auth |
| open-ps | Initializing the payment interface after a user clicks the buy button in an item card. The product SKU is passed in the Label parameter. | sku | /store_landing_buy_button_open-ps |
Modal window events
Note
Category for all Store block events that connect with the modal window is
Store_landing_pop-up.| Action | Description | Label | Virtual page |
|---|---|---|---|
| auth | Opening the authorization modal window after an unauthorized user clicks the buy button in an item modal window. | - | /store_landing_pop-up_auth |
| open | Opening the item card modal window after the user clicks the card. | sku | /store_landing_pop-up_open |
| open-ps | Initializing the payment interface after an unauthorized user clicks the buy button in an item modal window. | sku | /store_landing_pop-up_open-ps |
Call-to-action block events
Note
Category for all Call-to-action block events is
CTA_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| click-buy | Clicking on the buy button. In the Label parameter, the product SKU is passed. | sku | /landing_click-buy |
| open-login | Opening the authorization widget when the buy button is clicked. | – | /landing_open-login |
| open-uid-widget | Opening the ID input widget when clicking on the buy button. | – | /landing_open-uid-widget |
| enter-email | Clicking on the confirmation email button to subscribe to the newsletter. | – | /landing_input-subscribe-confirm (ex Subscribe) |
Footer block events
Note
Category for all Footer block events is
Footer_landing.| Action | Description | Label | Virtual page |
|---|---|---|---|
| social | Clicking on the social network button. The name of the social network is passed as the Label parameter. | name | /landing_footer_click-social |
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.
