An increasing number of ecommerce brands are using Shopify Plus to manage international stores and sell in multiple currencies.

Since there are a few setups you may have, here are my recommendations in each case to get the most versatile reporting in Google Analytics (GA). 

For a single store accepting multi-currency

Littledata’s enhanced Shopify tracking already handles multi-currencies at all stages of the shopping journey. 

We recommend you have just a single web property and single view in Google Analytics. Our audit checks will make sure the currency you have set up for this view matches your Shopify store currency.

For multiple stores, with different default currencies (GA standard)

I recommend you set up a single web property, but with different Google Analytics views for each country store.

You can create one ‘All countries’ view in the same currency as your company’s default reporting, and then each country store would need filters set up to include traffic only from that country. Here’s how to set up the filters:

• Go to the Admin section in Google Analytics, and click Filters under the View settings
• Then click to ADD Filter
• Then set up a filter to include traffic only from this store’s hostname
• Then Save the filter

This could be tricky if you use a third-party checkout, where the hostname will be shared across stores (see below).

Each country view in Google Analytics would have the same currency and timezone set as the Shopify store, so you can compare like-for-like orders.

In Littledata, you would create different accounts for each country store and be able to audit and benchmark your stores’ performances separately.

Multiple stores, with different default currencies (GA 360) 

With GA 360, you have the added flexibility of being able to setup a roll-up property, combining ecommerce events from multiple properties.

So you have two options: 

1. Go with the same solution as for GA Standard. The advantage here is that with a single web property, you can easily track visitors as they move between your country stores (i.e. if users are directed to a country after seeing a marketing campaign, you can still attribute the marketing campaign as they move to a different store).
2. Set up a separate web property for each country store, and roll-up into a group property. The advantage here: your data is clean, but you can’t track cross-country visitors.

Option 2 is going to work better if you leverage third party checkouts like ReCharge Payments or Bold Cashier, where it may be hard to filter out the traffic from only one country.

If you’re not sure what to think of this, don’t fret — Littledata’s analytics team can guide you in multi-site setup with an Enterprise plan, so please reach out if you’re feeling confused.

Multicurrency support for Shopify

If your store presents prices in multiple currencies using Shopify Payment’s multi-currency feature, then Littledata’s app is 100% compatible with multi-currency.

Here’s how it works for different parts of the data processing. We use Shopify’s definition of ‘presentment currency’ and ‘shop currency’.

Storefront data layer

All prices for products in the LittledataLayer and dataLayer variables will be in shop currency, regardless of the presentment currency. This includes the add-to-cart events handled by Littledata’s servers.

Checkout steps

Prices are sent in the presented currency and converted by Google Analytics (or Segment) to the target currency at current exchange rates.

Orders & Refunds

All orders and refunded items are sent to Google Analytics in the shop currency.

Multiple country stores sending to one web property

If you have multiple country stores, with different shop currencies, all sending data to a single web property in Google Analytics, this is also handled by our tracking script.