Shopify Data Not Syncing to Facebook? How to Find What's Wrong
by Jaz Field
When Shopify data isn't syncing to Facebook, the first job is working out which data is missing. Products, browser events, server events and purchase values travel by different routes, and each one breaks for different reasons. This guide covers the six most common symptoms, what causes each one, and where to check.
"Facebook isn't getting our data" can mean six different problems. Products missing from the catalog. No events in Events Manager. Fewer purchases than Shopify. More purchases than Shopify. Events that arrive but can't be matched to anyone. Purchase values that are wrong.
Each has a different cause and a different place to look, so start by matching your symptom.
Find your symptom
| Symptom | Most likely cause | Where to check |
|---|---|---|
| Products missing from the catalog | Not published to the sales channel, or rejected | Commerce Manager > Catalog > Issues |
| No events in Events Manager | Dataset disconnected, or the wrong pixel | Events Manager > Overview |
| Fewer purchases than usual | Purchase event stopped firing | Events Manager > Test Events |
| More purchases than Shopify | Duplicates without a shared event ID | Events Manager > event details |
| Events arrive but attribution is low | Low Event Match Quality | Events Manager > Purchase > Event Match Quality |
| Wrong or zero purchase values | Value or currency not sent correctly | Events Manager > Test Events, event parameters |
1. Products are missing from your Facebook catalog
The catalog and the pixel are separate systems. A catalog problem does not affect tracking, and fixing tracking will not fix the catalog.
The Facebook & Instagram app in Shopify syncs products to a catalog in Commerce Manager. Products go missing when:
- They are not published to the sales channel. In Shopify, each product has to be available on the Facebook & Instagram channel.
- Required fields are missing. Image, price, title, availability and a working product URL are needed for every item.
- They were rejected. Meta's commerce policies reject some categories and some product descriptions. Commerce Manager lists every rejected item with the reason.
- The app is connected to a different catalog from the one your ads use. This happens after a Business Manager change or a reinstall.
2. No events appear in Events Manager
If the Overview in Events Manager shows nothing recent, Meta is not receiving events at all.
- Check the dataset. Make sure the pixel (now called a dataset in Events Manager) that your ads optimize to is the one connected to your store. After agency changes, it is common to find the store sending to one pixel while the ads use another.
- Check the connection. In the Facebook & Instagram app, confirm the business account, ad account and dataset are still connected. A permissions change in Business Manager can quietly disconnect them.
- Check for a custom Conversions API setup. If a developer built one, its access token may have been revoked or tied to a user who left the business.
3. Meta shows fewer purchases than it used to
Meta will always report fewer purchases than Shopify, because it only counts the ones it can attribute to an ad. What matters is a sudden drop.
- Old order status page scripts stopped running. Shopify has retired additional scripts on the thank-you and order status pages as part of its checkout upgrade. A purchase pixel that lived there stops recording orders.
- Consent blocks the browser pixel. When a shopper declines cookies, Shopify's customer privacy settings stop the browser pixel. Without a server-side route, those purchases never reach Meta.
- Ad blockers and browser privacy features block the pixel's script for a share of shoppers, more on desktop and in some browsers.
- The browser pixel fires late. If the purchase event depends on the shopper staying on the thank-you page until it loads, shoppers who close the tab are lost.
To confirm, open Test Events in Events Manager, place a test order, and check that Purchase arrives from the browser, the server, or both.
4. Meta shows more purchases than Shopify
A platform that reports more purchases than your store took is double counting.
- Two installs of the same pixel. A pixel pasted into the theme years ago, a tag manager container, and the Facebook & Instagram app can all send purchases at once.
- Browser and server events without deduplication. Sending purchases from the browser and through the Conversions API is the recommended setup, but Meta can only remove the duplicate when both events carry the same event ID. Events Manager shows the deduplication status on each event.
- Two tools sending purchases server-side. If you add a server-side integration, make sure only one route sends each event to the same dataset.
The free Littledata Tracking Audit lists every pixel on your storefront, how it was installed and which account it sends to, and flags duplicates.
5. Events arrive, but Meta can't match them
Events Manager may show every purchase while Ads Manager still credits few of them. The likely cause is Event Match Quality: a score from 0 to 10 showing how many of the events Meta can tie to a Facebook or Instagram user.
Match quality depends on the customer details sent with each event, such as hashed email, phone number, name and address, plus the click ID from the ad. Browser-only events tend to score lower because they carry fewer identifiers. On Shopify, purchases sent by the native Facebook & Instagram app average a score of around 7.
- Check: Events Manager > your dataset > Purchase > Event Match Quality, which lists the identifiers Meta receives and the ones it recommends adding.
- Fix: send hashed customer details with every server event, and keep the click ID with the shopper through checkout.
The native app also only sends purchases through the Conversions API. Add to cart and checkout events rely on the browser pixel, so mid-funnel retargeting audiences stay incomplete when that pixel is blocked.
6. Purchase values are wrong or zero
If purchases arrive with no value, the wrong currency or inflated totals, Meta optimizes to the wrong number.
- Zero values usually come from a custom pixel that sends the event without the value parameter.
- Wrong currency happens with Shopify Markets when the event sends the presentment currency under the store currency code, or the other way round.
- Inflated totals can include tax and shipping, or count the same order once in each currency.
Check the parameters on a test order in Test Events, and compare a week of purchase value in Events Manager with Shopify's online sales.
When the problems keep coming back
Most of these failures trace back to the same cause: several separate tags and apps sending data to Meta from the browser, each breaking in its own way when the theme, checkout or consent settings change.
The data layer for Shopify replaces that with one route. Littledata sends every funnel event, not just purchases, from Shopify's servers to the Meta Conversions API, with hashed customer details for an Event Match Quality score of 9 and an event ID for deduplication. Purchases fire for every order, including subscription renewals and post-purchase upsells, so the revenue Meta reports matches your store.
For the next step, comparing Meta with GA4, see why your conversion data differs between Google Analytics and Meta Ads.
Frequently asked questions
Why is my Shopify store data not syncing to Facebook?
First work out which data is missing. Products that don't appear in your catalog are a catalog sync problem in Commerce Manager. Events that don't appear in Events Manager are a pixel or Conversions API problem: a disconnected dataset, the wrong pixel, consent blocking the browser pixel, or tracking that stopped working after a checkout change.
Why are my Shopify products not showing in my Facebook catalog?
Usually because the products are not published to the Facebook & Instagram sales channel in Shopify, are missing required fields such as an image, price or availability, or were rejected for a commerce policy reason. Commerce Manager lists each rejected item with the reason.
Why does Meta show fewer purchases than Shopify?
Meta counts purchases it can attribute to an ad, so it will always be below Shopify. A sudden drop usually means the purchase event stopped reaching Meta: the browser pixel blocked by consent or ad blockers, a dataset disconnected from the store, or old order status page scripts that stopped running after Shopify's checkout upgrade.
Why does Meta show more purchases than Shopify has orders?
Purchases are being counted twice. The usual causes are two installs of the same pixel, or browser and Conversions API events sent without a shared event ID, so Meta cannot deduplicate them. Events Manager shows a deduplication status for each event.
How do I check if Facebook is receiving my Shopify events?
Open Events Manager, select the dataset connected to your store and check the Overview for recent events, split by browser and server. Use Test Events to place a test order and watch each event arrive, and check the Diagnostics tab for errors Meta has detected.
Do I need to remove the Facebook & Instagram app to use Littledata?
No. The app also syncs your catalog and handles shop features, and you can run Littledata alongside it while you validate the results. Send each event to Meta through one route, so purchases are not counted twice.
The short version
Name the symptom first. Catalog problems live in Commerce Manager. Missing, duplicate or unmatched events live in Events Manager. Check the dataset connection, deduplication and match quality there, and you will find most Facebook sync problems in under an hour.
