How to Configure Google Analytics in Elevar Server-Side Destination

Follow the step by step guide to launching your Google Analytics server-side tracking

Please be sure to follow the steps within your Elevar Server-Side configuration.


Please note that this guide is for customers using Google Universal Analytics 360


Before you can enable your Google Analytics Server-Side Destination, you will need to:

Step 1: Determine Your Strategy

If you currently have your GA setup via native Shopify or another third party app and are testing out Elevar then we recommend creating a backup GA property to run in parallel so you can compare. Be sure to:

  • Enable ecommerce tracking
  • Copy over your referral exclusion rules from your main property
  • Copy over any other settings like filters, etc

Step 2: Add Google Analytics as a Server-Side Destination

  1. In your Elevar App, navigate to My Tracking > Select Add Destination > Find and select Google Analytics.

  1. You'll be taken to an Overview Page, select Get Started

Step 3: Select your Events

By default, we've selected recommended events for you to send & default to sending these server-side only.

If you have some non-Shopify pages where Elevar's DataLayer & DataLayer Listener code is not present, you may want to customize this step so that the events that could occur on your non-Shopify pages are sent via the web.

Step 4: If applicable, Enable Consent Mode

If consent is required, follow these steps to enable consent mode & select your consent categories.

If consent is not required, select Save & Continue.


Note: Currently if a user is opt-ed out of tracking then Elevar will block the transaction from being sent to GA.

We are investigating ways to support new ways that GA can accept anonymized data, even when a user is opted out.

Step 5: Select your Transaction Identifier

The Order Name is the most commonly used Transaction ID, so you likely won't need to adjust anything and can just select Save to continue to the next step.

Note: In order to send refund data to Google Analytics, you must use Order ID as your transaction identifier.

Step 6: Select Product Identifier

Product SKU is almost always used as the primary product ID in Google Analytics integrations, but you can override this if needed.
The native Shopify <> GA integration uses SKU so it's best to keep SKU to maintain historical consistency. Select Save to continue to the next step!


If you change this and have elected to send some ecommerce events via the web in Step 3, you'll need to customize the pre-built web tags in Step 11 to use the new product identifier.

Without this, your Shopping Behavior and product performance reports will not match up due to different IDs.

Step 7: Block Transactions

This step allows you to control exactly what purchase events are sent to Google Analytics. You can block orders based on Source Channel Names, Order Tags or Order Gateways. [How?]

What is our recommendation?

Instead of blocking orders from being sent, we'd recommend implementing Source / Medium overrides in the Google Settings Step.

This will allow your orders in GA to match Shopify better & allow you to bucket offline orders like Recurring Orders or POS orders into their own designated Source / Medium.

You can then create different Views in GA to show "Website Only (No Recurring) Orders" vs "All Orders" by using filters.

Step 8: Subscriptions

If you sell subscriptions then you have the ability to:

  • Send first time orders only
  • Send first time and recurring orders where the recurring orders use the attribution from the first order [How does this work?]
  • Send first time and recurring orders where you can send a custom source/medium/campaign for recurring orders (e.g. "recharge / recurring order")

I'm using a separate checkout & am not using Recharge or OrderGroove

If you are using another Subscription software that we don't have listed, here is how to find your Recurring Order tag applied on orders:

  1. Go to your Shopify Order grid
  2. Filter the orders by the channel that powers your subscriptions
  3. Look for orders that have the recurring order tag (this differs by app). For example ReCharge sets "Subscription" and "Subscription Recurring Order" on all recurring orders.

So if your subscription provider uses "recurring-order" as the tag set on orders your settings would look like this:


Tip: We'd recommend implementing Source / Medium overrides for recurring orders.

This will allow your orders in GA to match Shopify better & allow you to bucket offline orders like Recurring Orders or POS orders into their own designated Source / Medium.

You can then create different Views in GA to show "Website Only (No Recurring) Orders" vs "All Orders" by using filters. This will prevent conversion rate from being over-inflated.

Step 9: Google Settings

Here you can:

  • Input your property ID for universal analytics
  • Override the GA cookie to use Elevar's user ID
    • We recommend keeping the GA cookie enabled. This allows you to use GA events in your web container that will automatically use the GA cookie.
  • Override the transaction value sent to GA
  • Send custom dimensions such as customer LTV [How do I set this up?]
  • Set up custom source/medium overrides for orders created outside your online store

Step 10: Setup Source / Medium Overrides

If you decide to not block certain channels from going to Universal Analytics (draft orders, international, third party apps, etc) then you can add source / medium overrides to bucket these orders into their own group in UA.

If you do not do this then they will show up as direct/none.

Check to see what Sales Channels you currently use.

  1. In the Google Settings step, Select Advanced Options.

  2. Select Customize by Channel

  1. Find the Channel Code (a.k.a. Source_name) for your Sales Channel

  2. Input the Channel Code > And input what you'd like to appear as the Source, Medium, & Campaign in Google Analytics.

  1. You can press Add Another to add another Override or press _Save _to continue.

Step 11: Web Container Setup

Depending on your choices in your Event Selection, you can skip this step if you've selected all server-side events.

However if you've chosen some events to come from your Web Container then you'll need to download the container and import into your GTM web container. [How do I do that?]

Step 12: Going Live

It's time to go live!

  1. Select Go Live on the Overview Step

  2. [optional] If you need to publish changes in your web container, then publish these too.

  3. Remove your pre-existing GA integration

  4. Monitor your GA property via real time reports and/or your standard reports

If you have any questions please don't hesitate to reach out to ask us for help.