Seeing the localized sites’ traffic and conversions in your own Google Analytics account – Glopal Help

Tracking traffic in your Google Analytics account

Within your Google Analytics (GA) account, you’ll natively be able to see the international traffic from Glopal.

In your GA reports, the easiest way to distinguish Glopal’s traffic is to create a custom segment or audience.

In GA UA:

When creating a segment:

Name your segment in a way you can distinguish it easily
In Advanced > Conditions, include the sessions where:

Hostname contains yourhostname
OR
Hostname starts with yourhostname

In GA4:

When creating a custom audience, filter on the hostname:

Hostname contains yourhostname
OR
Hostname starts with yourhostname

For the international traffic from Glopal, the hostnames typically are

xx-storename.glopalstore.com
xx.storename.com
storename.xx

Where

storename is the name of your store or your domestic URL domain
xx is the 2-character country code such as fr, de, it, us, uk, etc.

Once you’ve created a custom segment/audience based on these hostnames, you’ll be able to see all the regular GA metrics for the traffic from Glopal.

To go more granular in your data analysis, you can segment your traffic by looking at the channels it comes from. To do so, you need to segment the data by using the UTM dimensions.

Traffic from non-paid channels

Redirected international traffic

When an international visitor lands on your domestic site, we use a geoip feature to detect its location and determine the best-localized context for that visitor. That visitor is then redirected to the corresponding localized site.

This means when the visitor is redirected to the localized site, the source of that visit was indeed your domestic site.

In this case, and assuming your domestic site domain is “https://www.mystorename.com”, the traffic will appear under the UTM “source = https://www.mystorename.com”.

Some merchants require to keep the original acquisition source (when the international visitor landed on your domestic site) of the traffic, instead of seeing the domestic site as the source.

In this case, Glopal has a feature to do so, if you wish to activate it, please contact your account manager specifying the Resume domestic GA session feature.

For more granularity on the traffic, please refer to the Glopal UTM glossary at the end of this article.

Organic / Direct

Glopal also brings non-paid international traffic that starts right from the localized sites.

You can see this traffic when using UTM “source = organic” or “source = direct”.

Traffic from paid channels (Google Ads / Facebook Ads)

If you are running international ad campaigns through Glopal on Google Ads or Facebook Ads, you can see this traffic in your GA account as well.

To do so, you’ll be using the UTM dimensions the following way:

Source
- “Source = google” if you want to get the traffic from all Google Ads (Google Shopping, Search, Display, etc.)
- “Source = facebook” if you want to get traffic from all Facebook and Instagram Ads
“Medium = cpc”
“Campaign containing glopal”

Tracking conversions in your Google Analytics account

Your international traffic will be converting on Glopal’s localized checkout. And this checkout is hosted on Glopal’s domain, glopal.com.

This means that the conversions will be recorded on the glopal.com domain, and not on the localized sites. The consequence is that it will look like you’re receiving international traffic from Glopal that is not converting at all. This is of course not true.

You can contact your account manager to request the activation of a feature allowing Glopal to send conversions to your GA account. So that, the conversions will be properly linked to the international traffic you’re getting from Glopal.

When requesting this feature, you need to indicate which option suits your needs. There are 3 of them.

Google Analytics Universal Analytics

A: Get Enhanced Ecommerce events (Recommended)

Prerequisite: You need to have Enhanced Ecommerce enabled in your GA property and view. You can follow Google Analytics instructions to do so.

You can choose this option which will give you pageviews and purchase events as enhanced ecommerce transaction events.

Your GA account will directly receive several Enhanced Ecommerce events and native metrics. This is the most comprehensive and valuable option since GA uses these events to calculate the conversion rate, the ecommerce revenue, and many other built-in reports.

The conversion data you’ll receive in your GA account

With this option, you’ll be able to see the usual information related to Enhanced Ecommerce conversions:

Transaction id: When sending transactions, Glopal transaction ids are prefixed with GL-
Currency: The currency is the one used in your account.
Transaction amount (shipping, tax, and duties included): Order amount paid by the buyer. It is automatically converted into your currency by Google (Google's currency conversion rate).

Glopal doesn’t send the details about which products were purchased because of potential product id mismatch which could shamble and confuse your Product Performance report.

For example, Glopal records a combination of product id and variant id to our Glopal GA account, but you could be using SKU instead in your GA account. So, these product ids would not match and if we send them to your GA account, you wouldn’t be able to understand your own Product Performance report as it would contain unrecognized products.

Note: Product details are available on our GA4 implementation.

B: Get conversions from events

Prerequisite: You need to provide Glopal with the view and currency used in your GA account:

Navigate to the View you use for analytics
Select Admin from the left sidebar at the bottom
Make sure the appropriate View is selected and then click View Settings
Your currency is what is configured at Currency Displayed As option

With this option, Glopal will be sending pageviews and purchase events to your GA account. However, because those are not Enhanced Ecommerce events, you’ll need to configure a goal that will retrieve the information Glopal is sending.

In Admin > Goals > New goal
Select template Place an order and click Continue
Name your goal (ex: Glopal order)
Select type Event and click Continue
In Category, select Equals to and input Glopal Checkout
In Action, select Equals to and input Purchase
In Label, select Equals to and input Glopal <countryCode>
In Value, select Greater than and input 0
Make sure the option Use the Event value as the Goal Value for the conversion is enabled
Click Save and then Done

Once done, you’ll be able to see orders from Glopal, and with the amounts converted into your GA account currency.

Note: the cents in the amounts will be cut-off.

C: Get conversions from pageviews

This is the last option when the previous ones, providing more details, are not available to you.

In this case, Glopal will be sending you only pageviews.

When a visitor makes a purchase on Glopal, we’re sending the confirmation pageviews to your GA account, which means you can set up a goal from that pageview.

In Admin > Goals > New goal
Select template Place an order and click Continue
Name your goal (ex: Glopal order)
Select type Destination and click Continue
In the Goal details section, in the Destination field, select the operator Regular expression and input .*/localized-checkout/confirmation/.*/success
Click Save and then Done

Once done, you’ll be able to see orders from Glopal.

Google Analytics 4

Tracking with GA4 is done in 2 different ways.

Simple GA4 configuration (Recommended)

This is the simplest way for you to receive details from the localized sites' activity in your GA4 account.

You need to provide Glopal with only one piece of information: the measurement ID you wish to receive the data.

The format is: G-XXXXXXXXXX

We will then configure it on our end and send you data and conversions.

We can send you details of which items are being purchased.

However, each merchant uses a different attribute to identify a given item. To make sure that you can reconcile which items are being purchased, we need to know what ID to send you.

Please let us know among the below detail which one determine an item in your GA4 account.

$PRODUCT_ID
$VARIANT_ID
$SKU

Custom tracking

This way is more complex and will require more development and/or configuration effort on your end.

The implementation relies on Google Tag Manager GTM.

You need to provide us with your Tag Manager ID and we configure it on our end. This allows you to read the variables in a specific data layer we expose.

And with the help of the technical documentation, you will be able to create the variables and triggers in your GTM to manipulate the events and data to your needs.

This can be used for custom GA4 configuration and also 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.

Glopal UTM glossary

As mentioned in the documentation, you can see the international traffic from Glopal in your own GA account.

And you can use UTMs in order to filter the data you want to look at.

Below, you’ll find a more comprehensive description of the UTMs used at Glopal and that should help you dig deeper into your international traffic analytics.

UTM	Value	Definition
Source	Your domestic domain	Non-paid international traffic (used along with medium = wi_proxy)
	google	Traffic from Google. If medium = cpc, then this is paid traffic from Google Ads.
	facebook	Traffic from Facebook. If medium = cpc, then this is paid traffic from Facebook Ads.
Medium	wi_proxy	Indicates non-paid traffic
Medium	cpc	Indicates paid traffic.
Content	xx_YY	Indicates the country. Ex: en_US, en_GB, fr_FR, etc.
Campaign	Glopal_XXX	When “source / medium” is “google / cpc” or “facebook / cpc”, this UTM indicates the name of the ad campaign.
	pr_r	Traffic originates from a product page
	hp_r	Traffic originates from the home page
	cat_r	Traffic originates from a category/listing page
	sea_r	Traffic originates from a search page
	crt_r	Traffic originates from the cart page
	oth_r	Traffic originates from another page
	cs_w	Traffic originates from the selection of a country from the country selector widget
	cs_p	Traffic originates from the selection of a country from the country selector page
	email_r	Traffic originates from an email localized link