Checkout Analytics
Analytics Feature for Glopal Checkout allows merchants to observe and optimize the sales funnel and the ads performance. This setup extends on the existing tracking code Glopal inherits from your source site content and propagates to all localized sites.
Glopal offers pre-made integration for well known platforms such as Google Analytics (Universal and GA4), Google Ads, and Facebook Pixel, and custom analytics integration to collect detailed analytics of the checkout flow.
It is your responsibility to collect buyer's consent when setting up analytics in Glopal Checkout. Glopal can propagate consent (or absence of consent) collected on your localized site by your existing Consent Management Platform to the Glopal Checkout (cross-domain consent). In order to properly collect and apply consent across the checkout funnel, you may need to list Glopal Checkout domain (https://<store>.glopal.com) in your Privacy Policy and cosent prompt.
Pre-made integrations
Google Analytics (Universal Analytics and Google Analytics 4)
Google Ads
Facebook Pixel
To set up analytics contact your Glopal account manager. You will be asked about ID and tracking preferences. Read more on Google Analytics setup and available options to adjust data collection.
Custom integration
For those who require additional customization, we offer the option to include your own Google Tag Manager container or any other custom JavaScript inside Glopal Checkout. Please be aware that this advanced setup will demand more effort on your part.
Note: Google Tag Manager (GTM) and custom JavaScript will run in an isolated sandbox, which means code will not have access to the checkout page and page elements (DOM).
Code will however, have access to the current page path, cookies as set on the localized site, selected local storage entries, and analytics events pushed via Data Layer, including the recommended GA4 events: begin_checkout, add_shipping_info, add_payment_info, and purchase.
Note: Glopal’s GTM container is using a separate GTM data layer “glDataLayer”, and Glopal's cookies are prefixed with “glopal_ga”.
So, once we set up your Tag Manager ID, your container will be able to send data to your properties. Also, our data layer contains additional details on the localized sites, so you could read it and set up specific variables and triggers to enrich your analytics on the localized sites.
Glopal will include your container or custom JavaScript code next to all checkout pages and will push Data Layer events with data as described in the Event Reference section.
While these instructions are described for a custom GA4 configuration and they are also valid for custom tracking with a third-party tool.
In the case of the latter, set up triggers and variables and use them according to your needs with the third-party tool.
If your tool has an integration with GTM, it may be even easier, you’ll have to follow the tool’s instructions.
Custom Google Tag Manager setup
Define variables from Data Layer
Define one or more event triggers for Glopal Checkout events
Define tags using variables and triggers
Event Reference
All Glopal Checkout Events are based on Google Analytics 4 recommended events. Where required, events are extended with additional localization-specific parameters, like language or country. Every event is building up on previous events, extending available data as buyer is moving through the checkout funnel.
begin_checkout
On entry to the checkout, on page refresh, on discount code entry in the checkout, on switching country / language / currency, on return from external payment.
Page location:/<country>/glopal-checkout/shipping
gl_store_id
Your unique store ID
gl_store_platform
Your store platform (eg. "BigCommerce")
gl_country
ISO Alpha-2 destination country code, "FR"
gl_currency
ISO three-letter currency code, like "EUR"
gl_language
BCP47 language tag, like "fr-FR"
ecommerce
Checkout information (nested object)
ecommerce.currency
ISO three-letter currency code, like "EUR"
ecommerce.value
Cart subtotal after discount, presented in the Checkout (display price). Depending on store settings it can include or not include duties and taxes.
ecommerce.coupon
Last applied discount code (if applicable)
ecommerce.items[]
Product information (list of objects)
ecommerce.items[].item_id
By default "<store_id>-<product_id>"
ecommerce.items[].item_name
Product name
ecommerce.items[].item_brand
Product brand name
ecommerce.items[].price
Unit total before discount, presented in the Checkout (display price). Depending on store settings it can include or not include duties and taxes.
ecommerce.items[].quantity
Quantity in the cart
ecommerce.items[].gl_product_id
Product identifier (parent product ID)
ecommerce.items[].gl_variant_id
Product identifier (child/variant ID)
ecommerce.items[].gl_sku
Product identifier (variant SKU)
add_shipping_info
On selecting shipping option, before moving to the next page with payment info.
Page location:/<country>/glopal-checkout/shipping
(same as above)
ecommerce.value
Grand Total
ecommerce.shipping_tier
Shipping service grade type and incoterms (eg. "STANDARD DDU", "EXPRESS PF DDP")
add_payment_info
On initating payment with the selected payment option
Page location:/<country>/glopal-checkout/payment
(same as above)
ecommerce.value
Grand Total
ecommerce.payment_tier
Payment method type and brand (eg. "SCHEME VISA", "applepay mc" etc.)
purchase
On completed purchase, before presenting confirmation page.
Page location: (varies - based on the payment method)
(same as above)
ecommerce.value
Grand Total
ecommerce.transaction_id
Glopal Order ID (starting with "GL-")
Last updated
