NOTE-002 · FIELD NOTE FILED 30 OCT 2026 · REVISED 30 OCT 2026 F-401 F-102 F-201 F-101 F-301 F-302
Elevar vs Stape vs Littledata vs native: Shopify server-side tracking (2026).
ABSTRACT — Start with Shopify's native Meta and Google apps. Elevar or Littledata for managed multi-platform, Analyzify for GTM done for you, Stape to build server-side GTM.
Baris Asa, tracking consultant, London · Last checked: October 2026
Do you need server-side tracking on Shopify? Usually not at first. On its Enhanced or Maximum level, Shopify’s Facebook & Instagram app already sends Meta server events, and its Google & YouTube app sets up Google Ads conversions. Start there. Need several platforms fed from a server someone else runs? Elevar or Littledata. Want Google Tag Manager installed for you? Analyzify. Building server-side GTM yourself? Stape.When Meta, Google Ads or GA4 disagree with Shopify on sales, it is usually one of three things:
- Browser loss, F-401 : ad blockers stop the browser reporting a sale.
- Declined consent, F-201 : the visitor said no.
- Double counting, F-102 : the same sale sent twice.
Server-side tracking helps with the first. It doesn’t fix the other two.
I have no partnership, affiliate or commission arrangement with any tool on this page. Hiring someone instead? Six questions to ask.
Do you need server-side tracking on Shopify? Three checks
Whether server-side tracking is worth having at all is argued in You don’t need server-side tracking. On Shopify, three checks settle it for your store.
- Find the native Meta app’s level. In Shopify admin: Sales channels, Facebook & Instagram, Settings, Data sharing settings.
- What you should see: Customer data sharing switched on, at Enhanced or Maximum. That means Meta already receives server events.
- In Meta Events Manager, open your pixel’s Purchase event and compare its count with Shopify orders for the same days.
- What you should see: Browser and Server both listed as sources, and roughly one purchase per order. Close to double is the classic sign of F-102 .
- Compare Shopify orders with GA4 purchases for seven days from Shopify’s Orders over time report, leaving out the last two days. Google says GA4 processing can take 24 to 48 hours (Google Analytics Help: data freshness).
What the checks tell you:
- Meta on Enhanced, one purchase per order, GA4 within 5%: you don’t need a paid tool.
- Meta close to double: fix the second sender first. A new tool would add a third.
- GA4 and several platforms all short, with ad-blocker loss the likely cause: a paid tool is likely the fix. The tables below pick one.
- Short mainly on Safari: a server only helps if it sets first-party cookies from your own domain. Managed apps that send purchases from the vendor’s servers don’t change Safari’s cookie limits. More in why Tag Gateway doesn’t fix Safari ITP.
- The checks don’t settle it, or you already run a tool and the numbers still don’t match: that is a fault, not a missing tool. Those three numbers are where a tracking audit starts.
What “server-side” means on a Shopify store
A tool can read a Shopify store in two places.
In the browser, tools run as pixels: small scripts Shopify loads on the storefront, checkout and thank-you page in a sealed-off environment. Where the store requires consent, a pixel runs only after the visitor grants it (Shopify Help: pixels). The browser sees the ad click.
On the server, tools read order data from Shopify’s backend through webhooks (automatic messages Shopify sends when an order is placed). The server sees the order, but not the visitor’s browser. Stape’s own guide recommends webhooks only as a secondary option, mainly for orders placed outside the website (Stape documentation).
Setups that credit sales correctly join the two. They save the click ID (the tag that says which ad was clicked, Meta’s fbc and Google’s gclid) in the browser and send it with the server event. A sale sent from a webhook alone, with no click ID saved, has to be matched on hashed customer details such as email, and fewer sales are credited to the right campaign. Meta scores that matching as Event Match Quality (Meta: customer information parameters, Google Ads: enhanced conversions).
One rule applies to every tool below: two senders need one shared key. Meta’s recommended way to merge a browser event and a server event is the same event ID and event name, within 48 hours. A fallback that matches on fbp or external ID works only when the browser event arrives first (Meta for Developers). Without a shared key, Meta counts the purchase twice: F-102 .
How to choose: five questions
Server-side GTM, below, means Google Tag Manager running on a server you rent, with tags someone has to build and maintain.
| Question | Why it decides the tool |
|---|---|
| Which platforms need server data? | Meta alone is often covered natively. GA4, TikTok and Klaviyo, or Google Ads sent from a server, point to a paid tool. |
| Who maintains it after launch? | A managed app needs a marketer. Server-side GTM needs someone who can build and debug tags. |
| Do you already run GTM? | Analyzify and Stape fit a GTM-based store. Littledata is sold as a no-GTM setup. |
| How is consent handled? | Confirm the tool reads Shopify’s consent state and your banner (Cookiebot, CookieYes and similar) before it sends. |
| How is it billed? | Per order (Elevar, Littledata), per server request (Stape) or by plan and order tier (Analyzify). |
The five options at a glance
| Option | Best for | Not for |
|---|---|---|
| Shopify native apps | Stores that mainly need Meta and Google Ads conversions | Server-side GA4, or one controlled setup across platforms |
| Elevar | Brands feeding several ad platforms who want it run for them | Teams that want every tag rule in their own GTM |
| Littledata | Stores wanting server-side GA4 and ads data with no GTM | Stores whose tracking lives in GTM and should stay there |
| Analyzify | GTM-based stores that want the setup done for them | Teams after a fully managed, no-GTM service |
| Stape | Teams that build and maintain server-side GTM themselves | Stores with no one who works in GTM |
Not compared here: TrackBee, Aimerce, Addingwell and hand-built Shopify custom pixels. This page covers five.
Elevar vs Stape vs Littledata
| Tool | Who runs the server | GTM needed |
|---|---|---|
| Elevar | Elevar, or your own server-side GTM | Optional |
| Littledata | Littledata | No |
| Stape | Stape hosts it; you build the tags | Yes |
Elevar and Littledata bill by orders, Stape by server requests. Elevar’s Base and Core plans list up to 2 destinations and Advanced up to 4; Littledata has the same list on every plan; on Stape it is whatever you build.
Sources: Elevar on the Shopify App Store, Elevar docs, Littledata pricing, Stape pricing.
Elevar vs Littledata. Both are managed: you install an app, they run the server. Elevar’s plans cap destinations (the platforms it sends to); Littledata includes GA4, Meta, Google Ads, TikTok, Pinterest, Microsoft Ads and Klaviyo on every plan.
Elevar or Littledata vs Stape. Stape is a different kind of product: it hosts server-side GTM and every tag is yours to build. Choose Stape if you have the skills and the hours. Choose a managed app if you don’t.
Prices, as published
US dollars, from each vendor’s own pricing page or Shopify App Store listing, read on 30 October 2026. They change; check the links in Sources before you buy.
| Option | Entry plan | Next plan |
|---|---|---|
| Shopify native | $0 | None |
| Elevar | Base: $0/mo, 100 orders, then $0.75/order | Core: $225/mo, 2,000 orders, then $0.50/order |
| Littledata | Flex: from $0.35/order | Scale: from $159/mo, 1,500 orders |
| Analyzify | Standard: $145/mo or $1,305/yr, up to 5,000 orders | Plus: $275/mo or $2,475/yr |
| Stape | $0/mo, 10,000 requests | Pro: $17/mo billed annually, 500,000 requests |
My calculation from those pages, for a store with 1,000 orders a month:
| Option | At 1,000 orders/mo |
|---|---|
| Shopify native | $0 |
| Elevar | Core: $225 (Base: $675 in overage) |
| Littledata | Scale: $159 (Flex: about $350 at the starting rate) |
| Analyzify | Standard: $145, or $1,305 a year |
| Stape | Set by traffic, not orders |
Stape bills by server requests (each event your server receives and forwards), so its cost follows traffic rather than orders.
Shopify native: Facebook & Instagram and Google & YouTube apps
The Facebook & Instagram app has three data-sharing levels. Standard is the Meta pixel only, Enhanced adds Meta’s Conversions API (its server-to-server feed), and Maximum adds Meta’s latest ad features on top (Shopify Help: Facebook data sharing). So the app sends sales to Meta from a server only on Enhanced and Maximum. The Google & YouTube app suggests purchase, add-to-cart and checkout-started conversions by default and lets you switch on Enhanced Conversions, which sends hashed customer details with each sale (Google Ads Help).
Best for: stores whose paid media is mostly Meta and Google Ads, with nobody to maintain tags. Not for: server-side GA4, or Google Ads sent from a server. Google’s guide to the app describes browser conversion tags plus Enhanced Conversions; it doesn’t document a server path. One minus: little control. You can’t edit what the apps send, so when a number looks wrong there are few places to inspect.
Elevar
A Shopify app that sends conversions from Elevar’s servers, or from your own server-side GTM; its documentation recommends the managed route (Elevar docs). Destinations include GA4, Google Ads, Meta, Klaviyo and TikTok (Shopify App Store).
Best for: brands sending purchases to several platforms who want one place managing them. Not for: a team that wants every tag rule in its own GTM and nowhere else. One minus: destination limits by plan, and a charge per order above the plan’s allowance. Leave the native Meta app sharing alongside it and you have two senders: F-102 .
Littledata
A Shopify app that sends each purchase from Shopify’s side through each platform’s own server connection, with “no GTM and no code required” in its own words (Littledata). Every plan includes the same destinations and a 30-day trial (Littledata pricing).
Best for: a store that wants server-side GA4 and ad-platform purchases with no GTM to look after. Not for: stores with a mature GTM setup that should stay the single place tags live. One minus: less to inspect. With no GTM of your own, debugging means trusting the vendor’s view of what was sent.
Analyzify
A Shopify app with a Google Tag Manager integration. Purchase data routes through Analyzify’s servers to GA4, Meta and TikTok. On monthly plans you can set it up yourself, or pay $295 once for Analyzify’s team to do it; annual plans include that setup. A managed server-side GTM build is a separate one-off add-on (Analyzify pricing).
Best for: a GTM-based store that wants an installed, documented setup without hiring a developer. Not for: anyone who wants the managed, no-GTM model of Littledata or Elevar. One minus: the base app’s server routing covers three platforms. A full server-side GTM build is the add-on, not the app.
Stape
Stape hosts the server; you build the tags. Its Shopify app, listed at no charge, supplies the store’s events and order webhooks. Two features need a server hosted on Stape: one helps with ad blockers on every plan, the other with Safari cookie loss from Pro up (Custom Loader and Cookie Keeper: Stape on the Shopify App Store, Stape documentation, Stape pricing).
Best for: teams that know GTM and want full control of the server side. Not for: a store with nobody to build and maintain tags. One minus: building what runs on the server is on you. Run a Meta tag here while the native app still shares data, without a shared event ID, and you have F-102 .
What none of them will fix
A tool moves a signal; it doesn’t correct it. Four faults on file that no tool fixes:
- Wrong value or missing items. A server delivers the wrong value more reliably. See F-301 and F-302 .
- Two senders, no shared key. The native app and a paid tool both sending Meta purchases. See F-102 .
- Declined consent. Google’s Consent Mode (Google’s way of adjusting tags to the visitor’s consent choice) can model some of those conversions from consented traffic, if your account meets Google’s volume thresholds. A server can’t send what the visitor declined. See F-201 .
- A thank-you page that fires twice. Duplicate purchases on Meta and Google Ads, and in GA4 too when the transaction ID is missing or changes. See F-101 .
Common questions
Is Shopify’s Facebook & Instagram app already server-side?
Yes, from the Enhanced level up. Shopify states that Enhanced uses Meta’s Conversions API as well as the pixel. Standard is pixel only. Check your level before buying a separate tool for Meta.
Do I need Elevar if I have the Facebook & Instagram app?
Not for Meta alone, if the app is on Enhanced or Maximum. Elevar or Littledata are worth adding when GA4, TikTok or Klaviyo also need server data, or you want Google Ads conversions sent from a server rather than the app’s browser tags. Pick one sender for Meta.
- Option A: once the paid tool’s Meta pixel and Conversions API are published, open the Facebook & Instagram channel, then Settings, then Data sharing settings, and switch off customer data sharing. Elevar’s guide gives the same step under its own labels (Share Data, Change, customer activity data). Afterwards, view the page source in a private window and confirm the native Meta pixel no longer loads.
- Option B: keep the native app and switch off the paid tool’s Meta destination.
Then check that Events Manager shows one purchase per order.
Do I need server-side GTM for Shopify?
Only if you want to own the server side. Elevar, Littledata and Analyzify each run it for you. Server-side GTM, hosted on Stape or Google Cloud, makes sense when you need rules the apps don’t offer, extra data added to events, or platforms the apps don’t cover.
Does server-side tracking get around cookie consent?
No. A server event must respect the consent the visitor gave. For visitors who said yes, server-side means fewer sales lost to ad blockers. It lengthens cookie life on Safari only when the server sets the cookie in its HTTP response and Safari does not treat the server as a third party. WebKit deletes cookies set by script after 7 days without a visit (24 hours after some ad-click arrivals), and caps cookies set through a cloaked third-party domain or IP address at 7 days (WebKit tracking prevention).
Hiring a Shopify server-side tagging expert
Six questions to put to any Shopify server-side tagging expert before they start:
- Which of the three causes is my gap: browser loss, consent or double counting? How do you know?
- Can you show deduplication in Events Manager: one purchase per order, with browser and server merged?
- Will you reconcile GA4 and ad-platform purchases against Shopify orders for the same days?
- Will it be built in our own GTM container or cloud account, so we keep it?
- How does it read Shopify’s consent state and our banner before sending?
- Do you have a partner or commission arrangement with the tool you recommend?
That is the work I do as Synctag, from London. Eight years in tracking. Nineteen faults on file in the archive, six of them linked above. Five conference talks, including HeroConf and PPC Live.
An audit of a Shopify setup, whichever of these tools it runs, checks:
- what fires in the browser and checkout;
- what each platform receives;
- whether purchases deduplicate;
- whether totals reconcile with Shopify orders.
It ends with which fault you have and whether a paid tool is the fix: tracking audit.
Agencies can bring me in under their own name through white-label.
Sources
Read on 30 October 2026:
- Shopify Help Center, pixels overview and Facebook data sharing
- Google Analytics Help, data freshness
- Google Ads Help, conversion tracking with the Google & YouTube app on Shopify, about enhanced conversions and consent mode modelling
- Meta for Developers, deduplicate pixel and server events and customer information parameters
- WebKit, tracking prevention in WebKit
- Elevar, Shopify App Store listing and plans, server-side documentation and disabling the native Meta pixel
- Littledata, product page and pricing
- Analyzify, pricing
- Stape, Shopify App Store listing, Shopify setup guide and pricing