Shopify tracking
Elevar for ecommerce stores
Elevar builds and maintains the tracking layer on a Shopify store: a consistent data layer across the theme and checkout, then delivery of order events from the server to the platforms the store runs. Most installs we inherit were switched on to repair one broken purchase event and never revisited, with older pixels still firing beside it. We run it as the store's event pipeline, monitored and compared with Shopify orders on a schedule.
Elevar
Shopify tracking · by Elevar. A text wordmark, not a logo: we are not affiliated with the vendor and make no claim to its trademarks.
What we do with it
The work inside Elevar
A data layer that covers every template
Elevar pushes product, collection, cart and checkout events in a consistent shape. We walk every surface the store actually uses, including quick view, the cart drawer, bundle pages, subscription products and search results, so item id, variant, price and currency arrive the same way everywhere rather than only on the default product template.
Checkout and thank you page purchases
On Shopify, checkout tracking runs inside the customer events sandbox rather than the theme. We configure the pixel Elevar supplies, confirm the purchase event carries order id, value, currency, tax, shipping and line items, and check that nothing important still depends on scripts a modern checkout no longer runs.
Destinations enabled one at a time
Elevar can forward order events from the server to Google Ads, GA4, Meta, TikTok and other endpoints. We turn them on individually, match each identifier and deduplication key to the matching browser event, then confirm in the destination itself that the order was counted once and not twice.
Consent handled per region
Consent state travels with the event, so the banner a shopper sees and the data a platform receives have to agree. We map which regions the store sells into, set the rules for each, and test the outcome with consent granted and denied rather than assuming the default configuration matches the store's policy.
Monitoring the pipeline
Event volume and destination errors are visible inside Elevar, which makes tracking something you can watch rather than discover. We set what gets checked after every theme deploy, app install or checkout change: purchase volume against the previous week, rejected events per destination, and identifiers arriving empty.
Monthly comparison with Shopify
Each month we line up the purchase events each destination received against Shopify orders for the same period, then explain the difference: consent choices, refunds and cancellations, test orders, or events that never left the browser. Spend decisions then sit on a figure the store can defend.
When it fits
Elevar is the right tool when
Shopify and Shopify Plus stores feeding several ad platforms
Every platform now wants its own server connection. Maintaining four of those separately absorbs time and drifts apart. One pipeline that sends the same order event to all of them is easier to keep honest.
Stores whose tracking broke during a checkout or theme change
Checkout upgrades and theme rebuilds are where purchase events usually go missing. A structured pipeline gives the repair a defined shape instead of another layer of app pixels on top of the last one.
Teams without an analytics engineer on staff
A hand-built data layer only works while someone maintains it. A managed layer keeps working through staff changes, which matters more than the initial build quality.
What to watch
Where accounts drift
Facts about defaults and costs, not criticism. These are the settings we check on every account.
Cost follows order volume and destination count
Plans scale with what the store sends and where it sends it. Deciding which destinations actually inform a decision, before switching all of them on, keeps the bill tied to something useful.
Older tags need removing, not layering
A theme pixel left in place beside a server destination produces two purchases for one order. Removal is part of the setup, and it is the step most often skipped when the goal was simply to get tracking working again.
Server delivery does not change what you may collect
Sending an event from a server rather than a browser changes the transport, not the store's obligations. Consent decisions still govern what leaves the store, and the configuration has to reflect that.
New surfaces can bypass the data layer
A landing page builder, a headless section, a third-party cart or a new app checkout can render outside the layer. Anything added to the storefront needs a tracking check before it ships.
Does Elevar replace Google Tag Manager?
Not necessarily. Many stores run both: Elevar produces and delivers the events, and the container decides which vendor tags read them. Others use Elevar destinations directly and keep the container small. Either arrangement works. What matters is that each event has one owner, so nothing is counted twice.
Will Elevar make Google Ads and Meta match Shopify exactly?
No configuration will. Ad platforms count conversions on their own attribution windows and include some activity the store cannot observe. Better delivery narrows the gap and, more usefully, makes it stable from month to month. Reconciliation against orders still decides what a channel is credited with.
Can Elevar track Shopify checkout now that theme scripts are limited?
Yes. Checkout events run through Shopify's customer events framework, and order data can also be sent from the server once the order exists. Neither route depends on editing checkout templates, which is exactly why they survive the platform changes that break older setups.
Do we need Elevar if we already send events through server-side Google Tag Manager?
Rarely both for the same events. A self-hosted server container gives you full control and full responsibility; Elevar ships a Shopify-shaped pipeline with the data layer included. We pick one as the source of purchase events and keep the other only for work it genuinely does better.
Works alongside
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.