Facebook and Shopify Conversions Don't Match? Here's Why

If your Facebook and Shopify conversions don't match, that is normal: the two platforms almost never agree, and a gap by itself is not a bug. Facebook counts conversions using click and view attribution windows plus modeled, estimated results, while Shopify counts actual orders that hit your store. Here is why the numbers diverge, which one to trust, and when the gap is a real tracking problem.

Why do Facebook and Shopify numbers never match?

Facebook Ads Manager and Shopify Analytics are answering two different questions. Shopify asks “how many orders were placed?” Facebook asks “how many conversions can I attribute to the ads I ran?” Those are not the same number, and they never will be. The main reasons the gap exists:

• Attribution windows.By default Facebook credits a conversion to an ad if the purchase happened within 7 days of a click or 1 day of a view. Someone who clicks today and buys six days later shows up in today's ad numbers, while Shopify records the sale on the day it actually happened.
• Click versus view-through. Facebook can claim credit for people who merely saw an ad and later bought without clicking. Shopify has no concept of a view, so those conversions inflate Facebook relative to your store.
• Modeled and estimated conversions. After iOS opt-outs, Facebook fills gaps with statistical modeling instead of observed events. Those modeled results are estimates, not counted orders.
• Cross-device journeys. Facebook can connect a phone ad click to a desktop purchase through the logged-in user. Shopify only sees the final checkout, so it cannot stitch the journey together.
• Ad blockers and consent. Blocked pixels and declined consent mean some real Shopify orders never reach Facebook at all, pushing Facebook lower.
• Time zone and reporting date. Facebook reports on the ad account time zone and dates conversions to the ad interaction, not the order. A late-night sale can land on different calendar days in each tool.

Which one should you trust?

For revenue, trust Shopify. It records the orders that actually happened, the money that actually moved, and the refunds that came back. It is your source of truth for what the business earned. Facebook is directional: it exists to tell the algorithm which audiences and creative drive results so it can optimize spend, not to reconcile your books.

The mistake to avoid is adding the two together. If Facebook claims 100 purchases and Shopify shows 130 total orders, you do not have 230 sales. Facebook's conversions are a subset it is claiming credit for, overlapping with the same orders Shopify already counted. Use Shopify for total revenue and blended performance, and use Facebook to compare campaigns against each other.

When is the gap normal versus a red flag?

A moderate gap is expected. If Facebook is within roughly 10 to 20 percent of your Shopify orders in either direction, you are in normal territory for a modern account running the pixel plus the Conversions API. The gap becomes a signal worth investigating at the extremes:

• Facebook reporting far more than real orders. If Facebook claims 40 to 100 percent more purchases than Shopify recorded, suspect duplicate events. A pixel and server both firing Purchase without proper deduplication double-counts, and misconfigured events can fire on page refreshes or thank-you page reloads.
• Facebook reporting far fewer than real orders. If Facebook is capturing well under half of your Shopify sales, the pixel or CAPI is under-tracking. Common causes are a Purchase event that never fires, poor Event Match Quality, or heavy consent and ad-blocker loss with no server-side backup.

These extremes are exactly the kind of drift covered in how to explain tracking issues to clients, because the fix starts with agreeing on which number means what.

How do you shrink the gap and fix real issues?

You will never get the two tools to match exactly, but you can close an unhealthy gap and make Facebook's data trustworthy again:

• Set up the Conversions API. Server-side events recover conversions lost to browser blocking and consent. Post-iOS this is the single biggest lever, as covered in what changed with iOS ATT and Meta tracking.
• Deduplicate browser and server events. Send the same event from the pixel and CAPI with a shared event_id so Meta collapses the pair into one. This is the number one cause of Facebook over-reporting; see how to fix duplicate pixel and CAPI events.
• Improve Event Match Quality. Pass hashed email, phone, name, and address with each event so Meta can match conversions to people. Higher EMQ means fewer conversions dropped and better attribution.
• Verify Purchase fires once. Confirm the Purchase event triggers a single time per order, on the real order-confirmation step, with the correct value and currency. For the deeper differences between the two tracking methods, see Meta Pixel vs Conversions API.

Once the setup is clean, the remaining gap is just attribution math, and it will drift again the next time a theme update, app change, or consent tweak breaks a tag. That is why the gap is worth watching continuously rather than auditing once a quarter. Taglert monitors your Meta pixel, Conversions API, and Event Match Quality in the background and alerts you when the numbers start to slip, so a normal gap never quietly turns into lost revenue.