The 7 Most Common Elevar Tracking Errors (And How to Fix Each)

Q: Why are my purchases counted twice in GA4 or Meta?

Usually multiple sources fire the same purchase (the Shopify native pixel, a hard-coded snippet, and Elevar) without shared event_id deduplication. Remove competing pixels and ensure one shared event_id across browser and server events.

Q: Does Elevar track subscription renewal orders?

Only if configured. Renewal orders from Recharge, Skio, or Smartrr are created via API and bypass the normal checkout, so the subscription platform's order events must be connected to Elevar server-side to capture renewals as purchases.

Elevar is one of the best server-side tracking tools for Shopify — but it's also easy to misconfigure. When it's set up wrong, you don't get an error message. You get quietly wrong data: inflated ROAS, conversions that never reach your ad platforms, and budget spent on decisions made from bad numbers.

After auditing dozens of Shopify stores running Elevar, the same handful of issues come up again and again. Here are the seven most common — what they look like, why they happen, and how to fix each.

1. Why are my purchases being counted twice?

Symptom: Your purchase count in GA4 or Meta is higher than your real Shopify order count, and ROAS looks suspiciously strong.

Cause: Duplicate events — usually the Shopify native pixel, a hard-coded gtag/pixel snippet, and Elevar all firing the same purchase. Without proper event_id deduplication, each platform records the sale more than once.

Fix: Pick one source of truth (Elevar) and remove competing native pixels and theme snippets. Confirm a shared event_id is passed on both the browser and server events so Meta and GA4 can deduplicate.

2. Why aren't my conversions reaching Google or Meta?

Symptom: Elevar's dashboard shows events firing, but Google Ads and Meta report few or zero conversions.

Cause: Server-side container misrouting — a wrong GTM server transport URL, an unverified GA4 Measurement Protocol API secret, or a missing/expired Meta Conversions API token.

Fix: Re-check the server container's transport URL and credentials, then validate with Meta's Events Manager Test Events and GA4 DebugView until live events appear.

3. Why are some orders not tracked at all?

Symptom: Roughly 10–20% of orders never appear in analytics — often post-purchase upsells or express-checkout (Shop Pay, PayPal, Apple Pay) orders.

Cause: Tracking that depends on the thank-you page misses checkouts that skip or alter it, and post-purchase upsells create separate orders that aren't captured.

Fix: Use Elevar's server-side order webhook (not just the client-side thank-you page) so every order — including express checkout and upsells — is captured.

4. Why don't my conversion values match revenue?

Symptom: Purchase values in Meta/GA4 don't match Shopify revenue — sometimes zero, sometimes wildly off.

Cause: Value mapped from the wrong field (subtotal vs total), a currency mismatch (multi-currency stores sending local values without conversion), or inconsistent tax/shipping handling.

Fix: Standardize on one value definition and one reporting currency, map Elevar's value to the correct order field, and normalize multi-currency orders to a single currency.

5. Why is my Meta match quality (EMQ) low?

Symptom: Event Match Quality below ~6 in Meta Events Manager, weaker attribution, and higher CPAs.

Cause: Customer parameters (email, phone, name, location) aren't hashed and passed through the Conversions API, so Meta can't match events to people.

Fix: Enable advanced matching in Elevar so all available customer parameters are hashed and sent server-side. Well-configured stores routinely reach EMQ 7+.

6. Why aren't subscription and renewal orders tracking?

Symptom: First orders track fine, but recurring charges from Recharge, Skio, or Smartrr never show as conversions.

Cause: Subscription apps create renewal orders through the API that bypass the normal checkout flow Elevar listens to.

Fix: Connect the subscription platform's order events to Elevar server-side so renewals are captured as purchases — essential for any store with meaningful lifetime value.

7. Why did my EU data drop after Consent Mode V2?

Symptom: A sharp drop in tracked EU conversions right after enabling Consent Mode V2.

Cause: Consent signals from your CMP (Cookiebot, OneTrust, Consentmo) aren't wired correctly into Elevar/GTM, so events are withheld even when consent is granted.

Fix: Verify the consent-state mapping between your CMP and Elevar, confirm that granted consent actually unblocks tagging, and use consent modeling where appropriate.

The pattern: none of these throw an error. Everything looks like it's working — which is exactly why they quietly cost stores money for months before anyone notices.

How do I know which of these is affecting my store?

The fastest way is a structured audit: compare Shopify's true order count and revenue against what each platform actually received, then trace any gap back to its source. It usually takes about an hour to surface issues that have been running silently for months.

Is your Elevar setup leaking data?

Get a free diagnostic audit of your tracking. I'll show you exactly what's wrong and roughly what it's costing you.

Get your free audit →

Frequently asked questions

How do I know if my Elevar tracking is broken?

Compare your true Shopify order count and revenue against what each ad platform actually received. Gaps, duplicates, or mismatched values point to a tracking issue.

Why are my purchases counted twice in GA4 or Meta?

Usually multiple sources fire the same purchase without shared event_id deduplication. Remove competing pixels and ensure one shared event_id across browser and server events.

Does Elevar track subscription renewal orders?

Only if configured. Renewals from Recharge, Skio, or Smartrr are created via API and bypass the normal checkout, so those order events must be connected to Elevar server-side.