Shopify purchases not showing in Meta Ads: fixes
Why Shopify purchases don't show in Meta Ads Manager, or show twice, and how to check the pixel, consent, data sharing and deduplication step by step.
By DATALYR · · 3 min read
Contents
Start by finding where it breaks
When Shopify purchases don't show in Meta Ads, the event either never reached Meta, reached the wrong pixel, or arrived but was not credited to an ad. Each has a different fix, so check them in that order: Events Manager first, then the pixel ID, then attribution.
Open Events Manager, select the pixel your campaigns optimise for, and look for Purchase in the last few days. No Purchase at all is a sending problem. Purchases present but missing from Ads Manager is a credit problem.
No purchases in Events Manager
If Meta shows no recent purchases, or the pixel reads as inactive, work through the senders on your store. The usual causes are below.
- The Facebook & Instagram app is installed but no pixel is connected for data sharing. Shopify's data sharing settings ask you to connect the pixel you want to use.
- The store has a different pixel connected from the one the ad account optimises for.
- The pixel was pasted into theme code or old checkout scripts that no longer run on checkout. Checkout tracking now runs through customer events.
- Visitors in consent regions declined marketing. Shopify pixels need the permissions their configuration requires, so declined visitors send nothing from the browser.
- A custom pixel was added without subscribing to checkout_completed.
Purchases counted twice
The opposite problem is just as common: Meta reports roughly twice the real number of purchases. That almost always means two senders deliver the same order without a shared event ID.
Meta deduplicates a browser event and a server event when both share the same event name and the same event ID, within 48 hours of the first one. It can also deduplicate on fbp or external_id, but that generally works only when the browser event arrives first. Two independent server senders, such as an app's Conversions API and a second tool's, are not merged unless their IDs match.
Illustrative example. A store has 300 orders in a week. The Facebook & Instagram app sends Purchase at its Enhanced level, and a second integration also sends Purchase from the order webhook with a different ID. Meta reports 600 purchases and twice the revenue, and every ROAS figure is inflated by the same factor.
Two senders, one order (illustrative)
Shared event ID
300 purchases
Meta keeps one event per order.
Different event IDs
600 purchases
Each sender's event counts on its own.
Purchases received but not credited
If Events Manager shows purchases but campaigns show few, the events may lack the identifiers Meta needs to match them to a person who saw or clicked an ad. Check Event Match Quality on the Purchase event and look at which customer parameters are missing.
Timing matters too. A purchase outside the ad set's attribution setting will not be credited even when it is received. Ads Manager reports purchases under that setting, while Shopify reports every order, so some gap is normal.
Test with one order
Use one order to prove the path end to end. In Events Manager, open Test events and copy the test code. Place a test order and confirm one Purchase arrives with the right value, currency and order ID. Then check the browser network panel shows exactly one Meta base tag on the page.
Record the order ID and both event IDs if you run browser and server senders. If the IDs differ, deduplication will not happen however long you wait.
How DATALYR sends Shopify purchases
DATALYR sends Purchase to Meta from Shopify's paid-order webhook, so a purchase reaches Meta even when the browser event was blocked. Each order carries its total, currency, order ID, the ad click captured at the visit, and hashed email and phone when known.
Choose one owner for purchases. DATALYR's Shopify guide notes that if Shopify's own Meta sales channel also sends a purchase beside the DATALYR conversion, Meta reports about twice your real purchases. Send purchases from one of the two, not both, and never enable two DATALYR rules for the same event and pixel.
Related articles.
Commerce ·
Shopify Event Match Quality: how to improve it
What Meta's Event Match Quality score measures for Shopify purchases, which fields raise it (email, phone, fbc, fbp, IP, user agent) and how to check them.
Commerce ·
Shopify conversion tracking: reconcile orders, refunds and ad delivery
Verify Shopify order capture, campaign identity, transaction revenue and destination delivery without counting the same purchase more than once.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
