TRACKING SPECIALIST — BARIS ASA · LONDON
Synctag
Start the check → TRACKING SPECIALIST — BARIS ASA · LONDON

READING ROOM › FIELD NOTE › NOTE-032

NOTE-032 · FIELD NOTE FILED 13 NOV 2026 · REVISED 13 NOV 2026 F-102 F-101 F-201 F-301 F-401

Elevar vs Littledata for Shopify (2026): what each one sends, and who each fits.

ABSTRACT — For GA4, Littledata sends cart, checkout and purchase from its servers with no GTM; Elevar sends the purchase from its servers and the funnel from the browser. Meta, consent defaults, and which store each fits.

Baris Asa, tracking consultant, London · Last checked: November 2026

Elevar and Littledata both send Shopify orders to GA4, Meta and other platforms from their own servers. For GA4, the difference is how much of the funnel goes that way. Littledata sends add to cart, every checkout step, purchase and refund from its servers, built from Shopify’s own data, with no Google Tag Manager. Elevar’s recommended GA4 settings send only the purchase from its servers and the rest of the funnel from the browser, through your GTM container or its own GTM-less setup.

The short verdict. You want GA4 and the ad platforms fed with nothing to maintain and no GTM: Littledata. You want your events in your own GTM container, or you send orders to affiliate networks and several email and SMS tools as well as ads: Elevar.

Check your numbers before you choose. Compare last week’s GA4 purchases with Shopify orders, leaving out the last two days. If GA4 is more than a few per cent short, or Meta shows more purchases than Shopify has orders, there is a fault to fix first, and either tool will carry it across. Switching below lists the usual four.

I have no partnership, affiliate or commission arrangement with Elevar, Littledata or any tool on this page. Prices are not listed here; both publish them, linked in Sources.

One naming note. Elevar is now part of Audiense. getelevar.com redirects to an Audiense page for “Audiense Online”, described as conversion tracking “from Elevar”. The Shopify app and docs.getelevar.com still say Elevar, so this page does too.

Which events Elevar and Littledata send server-side

“Server” here means the vendor’s servers, working from Shopify’s order and checkout data. “Browser” means a script on your store, which an ad blocker can stop.

To GA4

EventLittledataElevar (recommended settings)
Page and product viewsBrowserBrowser
Add to cartServerBrowser
Checkout stepsServerBrowser (server is an option)
PurchaseServerServer
RefundServer, on by defaultServer, if you switch it on

Sources: Littledata’s GA4 how-it-works page lists its browser and server events and says all are on by default. Elevar’s GA4 destination guide says “Use best practices” sends “just the purchase event server-side”. It lets you move checkout steps to the server but recommends keeping them in the browser for now, because it can’t guarantee their order from the server.

To Meta (pixel and Conversions API)

LittledataElevar
Browser events fromLittledata Pixel, an optional custom pixel that adds browser copiesElevar’s data layer and app pixel
Server eventsPage view to purchase, by defaultPurchase under “best practices”; another Elevar page lists more as defaults
Merge keyIts own event ID, based on the order for purchasesIts own event ID, from its data layer

Littledata’s Meta FAQ lists its default Meta events: Page View, View Content, Add To Cart, Initiate Checkout, Add Payment Info, Purchase and Post Purchase Upsell. Elevar’s docs differ by page: its Meta set-up guide says “Use best practices” sends just the purchase server-side, while its CAPI events page lists View Content, Add To Cart and Initiate Checkout among its defaults. Check the Events tab of your Elevar Meta destination to see which you have.

What the GA4 split means in practice:

  • Ad blockers. A server event can’t be stopped by the shopper’s browser. Littledata’s GA4 funnel is less exposed there. Elevar’s GA4 purchase is protected from ad blockers (consent still applies); its cart and checkout events behave like any browser tag (F-401 ).
  • Littledata’s checkout steps are worked out from Shopify’s checkout updates. Its own page says this can occasionally show a step the shopper didn’t take, and one-click checkouts such as Shop Pay skip some steps (Littledata: Shopify checkout).
  • Elevar’s checkout steps record what the page saw. Its event list notes some checkout events are missing on express checkouts (Elevar: events).
  • Timing. Littledata waits about 60 seconds after an order is created before it processes it, so other apps can update the order first (GA4 how-it-works).

How to choose

The usual order on Shopify, for any store: start with Shopify’s own Google & YouTube and Facebook & Instagram apps. Add a server-side app such as Littledata or Elevar when you need a reliable GA4 funnel or several platforms fed from one place. Build server-side GTM on your own server only when you need rules no app offers. That order, with the native apps and Stape, is set out in Elevar vs Stape vs Littledata vs native. Between these two:

  • Nobody on your team maintains GTM: Littledata, or Elevar’s GTM-less set-up.
  • Your tracking lives in GTM and should stay there: Elevar’s GTM set-up.
  • Orders must reach affiliate networks (Impact, Awin, CJ) or several email and SMS tools (Klaviyo, Postscript, Omnisend and others): Elevar has the longer list.
  • GA4, the main ad platforms and Klaviyo: both cover these; Littledata also lists Segment, and Attentive is live at Littledata and in beta at Elevar; check the current lists (Littledata, Elevar).
  • Google Ads from the server: Littledata lists it as a destination; Elevar’s docs list Google Ads as beta.

Elevar’s entry plan caps you at two destinations; its other plans list all of them (Shopify App Store).

Neither fits? The other Shopify options people compare are Shopify’s native apps, Stape (you build server-side GTM) and Analyzify (GTM set up for you), all in the sibling comparison.

Littledata on Shopify: how it works and who it fits

A Shopify app. Browsing events come from a script Shopify loads through an app embed (an app switched on in your theme settings). Cart, checkout, purchase, refund and post-purchase upsell events come from Littledata’s servers, which receive Shopify’s order and checkout updates (how server-side tracking works).

  • Best for: a store that wants a full GA4 checkout funnel and ad-platform purchases with no GTM to look after.
  • Not for: a team whose tracking lives in GTM and should stay the one place every tag is defined.
  • One minus: less to inspect. With no container of your own, you see what was sent through Littledata’s app and its live event feed (a beta tool for debugging events in real time), not your own GTM Preview.

Two defaults to check on day one:

  1. Consent mode is off on new connections. Until you switch it on for each destination, Littledata “tracks every visitor as if they had given consent, whatever your cookie banner shows” (Littledata: cookie consent). Once on, it reads the visitor’s choice from Shopify’s Customer Privacy API, which Shopify’s own banner and apps such as Pandectes, Consentmo and OneTrust feed.
  2. POS orders are excluded from purchases by default (Littledata: POS orders). Right for most online-only reporting; change it deliberately if you want shop-counter sales in GA4.

Browser events for Meta, TikTok and Pinterest come from the Littledata Pixel, which you add by hand under Settings, Customer events in Shopify. It sends nothing to GA4 or Google Ads (Littledata Pixel).

Elevar server-side tracking: how it works and who it fits

A Shopify app. A script on the storefront builds Elevar’s data layer (the list of shop events tags read from), and an app pixel it creates covers checkout and purchase. Orders go to destinations from Elevar’s servers on Google Cloud, using Shopify’s order notifications (technical details).

You choose one of two set-ups (GTM and GTM-less):

  • GTM: you import Elevar’s tags, triggers and variables into your web container. Full control of custom events and extra GA4 parameters. Someone has to maintain it.
  • GTM-less: events go straight from Elevar’s data layer, managed in Elevar’s interface. Standard ecommerce events, less to customise.

Then:

  • Best for: brands sending orders to many places (ads, affiliates, email and SMS) that want one tool and a per-destination order count.
  • Not for: anyone who wants the whole GA4 funnel sent from a server by default, or who wants the server side on their own servers. Elevar says it “does not support the ability to utilize your own servers” and points to server-side GTM on Google Cloud for that.
  • One minus: in GTM mode you inherit a container to maintain, and re-import tags when Elevar updates them.

On checking what was sent, Elevar’s Channel Accuracy Report shows how many orders reached each server destination against Shopify’s own orders, and email alerts fire when that falls below your target. It also notes that some destinations ignore orders without a click ID or email, with Google Ads as its example.

Two settings to check on day one:

  1. GA4 refunds are off unless you switch them on. They need the Shopify order ID as the transaction ID and don’t work with Consent Mode enabled (GA4 destination).
  2. Consent is set up in steps: browser tags first, then each server destination. A server destination respects consent only once its own step is done (Elevar: consent).

Meta: pick one sender per pixel

Only one tool should send purchases to a given Meta pixel: Littledata, Elevar or Shopify’s Facebook & Instagram app, not two of them.

Meta’s recommended way to merge a browser event and a server event is a matching event name and event ID (Meta for Developers). Each tool matches its own pair, as the Meta table above shows, but neither ID matches anyone else’s. Leave the Facebook & Instagram app sharing data on the same pixel, or run both tools during a switch, and Meta counts purchases twice: F-102 . Littledata’s FAQ says it in one line: “Only run one of them for the same pixel.”

Switching from one to the other

A new tool rarely fixes wrong numbers on its own, because the usual causes sit around the tool. Before you switch, rule out four:

  • a second sender for the same event (F-102 , F-101 );
  • a wrong order value or missing items (F-301 );
  • consent not wired through to the tool (F-201 );
  • ad-blocker loss on browser events the tool doesn’t send from its server (F-401 ).

If you still switch:

  1. List every destination the old tool feeds, including Klaviyo and affiliates, and which ones the new tool will take.
  2. Check the transaction ID. Littledata sends the Shopify order name (such as #1001) by default; Elevar’s GA4 refunds need the order ID. GA4 removes a repeat purchase only when the transaction ID is identical (Google Analytics Help), so two tools live at once with different formats both count.
  3. Turn the old destination off at the moment the new one goes live, one destination at a time.
  4. Compare a week of GA4 and Meta purchases with Shopify orders, leaving out the last two days: Google says GA4 processing can take 24 to 48 hours (data freshness).

Questions to ask whoever sets it up

  1. Which events will reach GA4 and Meta from the server, and which from the browser?
  2. Is consent switched on for every destination, and how did you test a decline?
  3. Which order channels are excluded (POS, drafts, exchanges), and why?
  4. Is anything else sending to the same Meta pixel or GA4 property?
  5. What do we check each week to know it still works?

If you want those answered by someone who sells neither tool: I check what each sender delivers against Shopify orders, whichever tool you run, and say whether the tool or the set-up is at fault. Agencies can bring me in under their own name through white-label.

Common questions

What is the main difference between Elevar and Littledata?

For GA4, where the shopping funnel is sent from. Littledata sends add to cart, checkout steps, purchase and refund to GA4 from its servers, built from Shopify’s own data, and needs no Google Tag Manager. Elevar’s recommended GA4 settings send only the purchase from its servers; the rest of the funnel goes from the browser, through Google Tag Manager or Elevar’s GTM-less setup. For Meta, both send browser and server events.

Which is better for GA4 on Shopify?

For a store that wants a complete GA4 checkout funnel with nothing to maintain, Littledata’s design fits, because its checkout events are sent from Littledata’s servers, built from Shopify’s checkout data, not from the browser. For a store that wants its GA4 events in its own GTM container with custom parameters, Elevar’s GTM setup fits. Either way, check one purchase per order in GA4 against Shopify for the same days.

Is Elevar now Audiense?

Elevar is now part of Audiense. getelevar.com redirects to an Audiense product page called Audiense Online, which describes itself as conversion tracking from Elevar. The Shopify app and the documentation at docs.getelevar.com still carry the Elevar name.

Can I run Elevar and Littledata together?

Not for the same destination. Two tools sending purchases to the same Meta pixel or GA4 property count sales twice unless they share one event ID or transaction ID, and these two set their own. If you switch, turn the old tool’s destination off when the new one goes live, then check one purchase per order.

Both can, once set up. Littledata’s consent mode is off by default on new connections and is switched on per destination. Elevar’s guides make the browser tags and then each server destination consent aware, in steps. With consent wired through and Consent Mode in its advanced form (Elevar calls it sending anonymised data to GA4), Google can model some conversions from visitors who decline, if the account meets Google’s thresholds.

Sources

All read on 13 November 2026.

← back to the reading room