← All posts

Blog

ShopifyTroubleshootingServer-Side Tracking

Shopify Conversion Tracking Not Working? A Diagnostic Checklist and the Server-Side Fix

22 November 20269 min readSyncBeacon Team

If your Shopify conversion tracking is not working, you usually notice it in one of three ways. Meta or Google Ads shows far fewer purchases than Shopify does. A purchase shows up in Shopify but never in the ad platform. Or the numbers are now higher than your orders, because something is firing twice.

These look like one problem, but they have different causes. This post is a checklist you can work through in order, from the cheapest check to the structural one. At the end, it explains what a server-side tracking setup fixes and what it does not.


Start with the symptom

Before you open any settings, match what you see to the most likely cause. It saves a lot of guessing.

What you seeMost likely causeFirst place to look
No purchases at all in the ad platformPixel not installed or not connected, or consent blocks itShopify customer events, ad platform diagnostics
Some purchases missing, some presentAd blockers, declined consent, shoppers who never reach the thank-you pageCompare order count to purchase events for one day
More purchases than ordersTwo pixels or apps sending the same eventEvent sources in the ad platform
Purchases arrive but with no value or wrong valueParameters missing in the event payloadEvent details in Events Manager or the Google Ads conversion action
Orders arrive, but the ad platform cannot match them to adsNo click ID or customer identifier on the eventMatch quality and diagnostics in the ad platform

The Shopify tracking diagnostic checklist

This Shopify tracking diagnostic checklist runs in order. Stop when you find the step that explains your gap, fix it, and re-measure before you carry on.

1. Confirm the order really exists in Shopify

Shopify orders are your ground truth. Pick one full day and write down the number of paid orders, excluding test orders, drafts you did not intend to count and orders that were cancelled. This is the number every ad platform should be compared against. Do not compare against sessions or Shopify's marketing reports, which attribute differently.

2. Shopify purchase event missing: check where the event comes from

When a Shopify purchase event is missing, ask which part of the chain should have sent it. There are only two options:

If your only source is a browser pixel, every step below that touches the browser is a potential leak. That is the core reason a Shopify purchase event goes missing for a share of orders: the order is created on Shopify's servers, but the report to the ad platform depends on a page loading in a browser you do not control.

3. Shopify pixel not firing: check the pixel itself

If a Shopify pixel is not firing at all, check these in order:

  1. In your Shopify admin, open Settings > Customer events and confirm the pixel is listed and connected. Pixels set up through a sales-channel app show up here too.
  2. Check Settings > Customer privacy. Depending on your region and settings, Shopify holds back pixels until the visitor accepts marketing or analytics tracking. Pixels that wait for consent will not fire for visitors who decline.
  3. Look at older snippets. Code pasted into legacy checkout or order status settings, or into theme files, may no longer run the way it did. Check Shopify's current documentation for what still works in your checkout.
  4. Check the ad platform's own tool for the pixel ID: Meta's pixel diagnostics in Events Manager, or Google Tag Assistant for the Google tag. Confirm the pixel ID and the conversion action are the ones you think they are.

If the pixel fires in your own browser but orders are still missing, the pixel is installed correctly. The loss happens somewhere between a real shopper and the ad platform, which is steps 4 to 6.

4. Ad blockers and browser privacy

Ad blockers and tracker blocking in browsers stop requests to known advertising endpoints. A pixel that depends on those requests loses the purchase for those shoppers. You cannot fix this inside the browser. We cover the reasoning, with sourced numbers, in ad blockers and conversion tracking.

5. Consent

If you run a consent banner, visitors who decline marketing cookies should not trigger marketing pixels. That is the right behaviour, and it also means those orders will be missing from a browser-only report. Your consent setup decides how many. See Consent Mode v2 for how consent signals work with ad platforms.

6. Duplicates: more than one thing sending the same purchase

Running Meta's Shopify sales channel, a second tracking app and a hand-installed pixel at the same time is common. Check the event sources in Events Manager. If the same purchase arrives from more than one source, deduplication only works when the events carry a matching event_id and event name. Meta documents this in its deduplication guide. For Google Ads, the equivalent is the transaction ID on the conversion. Two sources without a shared ID mean inflated counts.

7. Match data: click IDs and customer identifiers

Even a purchase that arrives can be useless if the ad platform cannot tie it to an ad click. Google Ads needs a click ID (gclid, wbraid or gbraid) or hashed customer data. Meta needs at least one identifier it can match, such as a hashed email or the fbp and fbc browser values. Look at the match quality and diagnostics in each platform before you blame the pixel.

8. Use test events the right way

Place one real or test order in a normal browser with no extensions, then one in a browser with an ad blocker. Compare what reaches the ad platform. If the first arrives and the second does not, you have confirmed a browser-side loss and you do not need to touch the pixel. Do the same with consent declined.


What the server-side fix changes

Server-side tracking moves the purchase report out of the shopper's browser. Shopify tells your tracking service about the order, and that service sends the conversion to the ad platform. Steps 4 and 5 stop mattering for the purchase itself, because there is no browser request to block.

With SyncBeacon on Shopify, the setup works like this:

Destinations are set up in the dashboard, for example Meta Conversions API and Google Ads conversion upload. For the full Shopify walkthrough see Shopify server-side tracking and the post on setting it up without GTM.

Key takeaway: if purchases go missing for some shoppers and not others, the cause is almost always the browser: blockers, declined consent or a page that never loaded. A Shopify order webhook does not depend on any of that, so the purchase report should not either.

What server-side does not fix

Be clear about the limits, so you do not chase the wrong number.

How to confirm it is fixed

  1. Pick the same full day again. Count Shopify orders, then count purchases the ad platform received from the server source.
  2. In the SyncBeacon Conversions page, check that each order shows a delivery result for each connected destination, and look at any forwarding errors.
  3. In the ad platform, check that the server and browser sources do not both count the same order. Deduplication needs matching IDs on both sides.
  4. Expect a small gap to remain. Aim to explain it, not to remove it.

If you want a quick outside view of which tags your storefront loads, the free tracking audit scans public pages. It cannot confirm that conversions are delivered.


Get started

Close your conversion gap today

Connect Meta CAPI, Google Enhanced Conversions, and more - in one setup, no developer required.

Get started

Interface names in Shopify, Meta and Google change over time. Check each platform's current documentation. Consent requirements depend on your jurisdiction and setup; this post is not legal advice.