PartialLeads
Tracking & Attribution

Why Do Shopify Purchases Reach Events Manager but Not Show in Ads Manager?

Events Manager shows your Shopify Purchases, Ads Manager credits almost none. Why Meta can't tie them to ads, and how click ids on the Purchase fix it.

JT
John Dela Torre
Founder, PartialLeads · · 9 min read
Quick answer

Events Manager counts every Purchase your store sends. Ads Manager counts only the Purchases Meta can tie to someone who saw or clicked your ad inside the ad set's attribution setting. The gap is sales that didn't come from Meta ads, plus sales Meta couldn't match because the event arrived without the click id, the browser id or customer details. Carry fbclid, _fbc and _fbp from the landing page through Shopify checkout onto the server-side Purchase and more of the real ones get matched.

Tell us what's broken. We'll fix your tracking — free.

Describe the tracking/attribution problem you're stuck on and we'll map it to a fix: server-side conversions to Meta, Google, TikTok and Pinterest, plus first-party tracking that survives Safari. No code required.

Shopify purchases reach Events Manager but not Ads Manager because the two screens count different things. Events Manager counts every Purchase your store sends. Ads Manager counts only the ones Meta can link to someone who saw or clicked your ad, inside the ad set’s attribution setting. Sales from other channels never show there. Neither do Purchases that arrived without identifiers Meta can match.

So a gap is normal. A huge gap, where Events Manager shows a steady stream of Purchases and your Meta campaigns show almost none, usually means the second problem: the sale happened, the event arrived, and nothing on it pointed back to the ad.

This article walks through how to tell the two apart, why Shopify is especially prone to the second one, and what a Purchase needs to carry for Meta to credit the ad.

Why does Events Manager show purchases that Ads Manager doesn’t attribute?

Events Manager is a delivery log. Ads Manager is an attribution report. Events Manager shows every Purchase the dataset received, from any visitor, whatever brought them. Ads Manager shows a Purchase against an ad only when Meta matches the buyer to a person who interacted with that ad within the attribution setting. Everything else is received but uncredited.

Five things put a Purchase in the first screen and not the second:

  1. The buyer didn’t come from a Meta ad. Organic search, email, Google Ads, a returning customer typing your URL. Those Purchases belong in Events Manager and don’t belong in Ads Manager.
  2. Meta couldn’t match the buyer. The event reached Meta with no click id, no browser id and thin customer details, so there was nobody to link to an ad interaction.
  3. The purchase fell outside the attribution setting. The ad set’s click and view windows decide how long after an interaction a sale can still be credited. A buyer who clicked and came back much later falls out.
  4. The ad isn’t tracking that dataset. Each ad’s tracking settings name a dataset (pixel). If the ad points at an old pixel, or the store sends Purchase to a different one, the sales land somewhere the ad never looks.
  5. You’re comparing different days. Ads Manager ties a conversion to the ad interaction, so a narrow date range can put a sale on a different day than Events Manager does. Compare a full week or longer.

Reasons 1 and 5 aren’t problems. Reasons 2, 3 and 4 are, and reason 2 is the one Shopify makes likely.

How do you tell whether the missing purchases actually came from Meta ads?

Check where the orders came from before you check the tracking. If most of your Shopify orders arrive from email, search or repeat buyers, a small Ads Manager number may be correct. Pull the orders for one week, look at what brought each buyer in, and compare the Meta-sourced count with what Ads Manager credited for the same week.

A quick way to do it:

  1. Open the week’s orders in Shopify and look at each order’s conversion summary or source. Note how many first arrived from a Meta ad (the landing URL carries fbclid, or the UTMs say facebook or instagram).
  2. Set Ads Manager to the same week and read the Purchases column at account level.
  3. Compare. If Shopify shows 40 orders that started on a Meta ad and Ads Manager shows 5, the gap is a matching problem. If Shopify shows 6 and Ads Manager shows 5, your tracking is fine and Meta simply isn’t driving many sales.

Expect the two to differ even when everything works. Shopify credits the session that placed the order, Meta credits its own clicks and views, and Shopify attribution differs from your ad platform for structural reasons. You’re looking for a gap that’s large and consistent, not a perfect match.

Why can’t Meta tie a server-side Shopify Purchase to the ad click?

Because the identifiers that link a buyer to a click are captured in the browser on the landing page, and a Purchase built on Shopify’s servers doesn’t have them unless something carries them there. Shopify’s checkout runs in its own sandboxed context, so the click id seen on landing often isn’t available when the order is created. The event arrives, but the click trail doesn’t.

Meta links an event to a person with a set of identifiers:

  • fbc — the click id. When someone clicks your ad, Meta appends fbclid to the landing URL, and the Meta Pixel (formerly Facebook Pixel) stores it in the _fbc cookie. This is the direct link to the click.
  • fbp — the browser id, stored in the _fbp cookie by the Meta base code.
  • Customer information — hashed email, phone, name and address, plus the visitor’s IP address and user agent.

A Shopify order webhook knows the customer’s email and address. It doesn’t know the fbclid from three pages ago, and it can’t read the browser’s cookies. A server-side Purchase built only from the webhook can therefore reach Meta, show up in Events Manager, and still have no click to point at. That’s the landing-to-checkout break covered in why attribution breaks between your landing page and Shopify checkout, seen from Meta’s side.

Customer details help. Meta can match a hashed email to an account and then find that account’s ad interactions. But fbc is the click itself, and a purchase that carries it is much easier to credit.

A Shopify buyer's journey from a Meta ad click carrying fbclid, to the landing page where the visitor id is set, through the sandboxed Shopify checkout, to the order webhook and a server-side Purchase that carries fbc, fbp and hashed email and phone to Meta

What should a Shopify Purchase event carry so Meta can credit the ad?

A Purchase Meta can credit carries the click id (fbc), the browser id (fbp), hashed email and phone, the buyer’s IP address and user agent, a real value and currency, and an event_id. The click id comes from the landing URL. The browser id comes from the Meta base code’s cookie. The customer details come from the order.

The practical rules:

Capture fbclid on the landing page, not at checkout. It only appears on the URL of the first page after the click. If you don’t save it then, it’s gone. When the _fbc cookie is missing, you can rebuild the click id from the landing URL, because Meta documents how _fbc is built from a timestamp and the fbclid value. You can’t rebuild _fbp that way, because no URL contains it.

Keep the Meta base code on the store. It sets _fbp. Removing it to “go server-side only” lowers matching instead of improving it.

Keep one source per Purchase. If Shopify’s Facebook & Instagram app and a server-side setup both send Purchase with different event ids, Meta counts two. Pick one sender for Purchase and switch the other off.

Check what actually arrived. In Events Manager, open the Purchase event and look at which customer information parameters it received and how often. Low coverage of click id or browser id on Purchase is the signature of this problem. Your Event Match Quality score for Purchase tells the same story as one number.

Confirm the ad is tracking the right dataset. In each ad’s tracking settings, make sure the dataset selected is the one your store sends Purchase to.

How does PartialLeads get the click id onto Shopify purchases?

PartialLeads captures fbclid, _fbc and _fbp with its Shopify Customer Events pixel at landing and through checkout, and ties them to one visitor across the checkout hop. When Shopify marks the order paid, the order webhook triggers a server-side Purchase through the Conversions API carrying those identifiers. Meta gets the click, not only the sale.

Click ids captured where they appear. The pixel reads fbclid from the landing URL and the _fbc and _fbp cookies when present. If fbclid was on the URL but _fbc is missing or malformed, PartialLeads rebuilds it in Meta’s format from the URL value. It doesn’t invent _fbp: that needs the Meta base code’s cookie, so keep the base code on the store.

The visitor followed across checkout. Shopify’s sandbox can hand the checkout a different id from the one set on the landing page. PartialLeads resolves the sessions into one person, using the visitor id, email, phone, IP address with user agent, and click id, so the order is matched to the session that carried the ad click.

Purchase sent from the order, once. Purchase fires from the Shopify order webhook when the order’s financial_status is paid, with the full order total as value, SHA-256 hashed email and phone, and a deterministic event_id. A retry or redelivered webhook can’t send a second Purchase.

PartialLeads Attribution report showing Shopify orders grouped by channel with Meta Ads orders highlighted, beside a lead's journey timeline where the fbclid landing visit leads to the order and the Meta CAPI activity log row for the delivered Purchase

Where you see it working. The journey timeline on a lead shows the landing visit with fbclid and the order it led to. The Attribution report shows which orders started from a Meta click, in first-touch and last-touch views side by side, so you can compare that count with what Ads Manager credits. The Meta CAPI page lists each Purchase sent with its delivery status, and the Leads list’s API column shows which conversion APIs each buyer was sent to.

The honest constraints. PartialLeads controls delivery: every paid order produces a Purchase with every identifier it captured. Meta controls matching. A buyer who opted out of tracking on iOS, arrived through a link without fbclid, or clicked outside your attribution setting may still go uncredited in Ads Manager. Matching is improved, not guaranteed. PartialLeads doesn’t deduplicate against another app’s browser Purchase either, so if Shopify’s Facebook & Instagram app still sends one, switch that off, as covered in fixing Meta CAPI tracking on Shopify.

What breaks The mechanism Where you see it in the dashboard
fbclid seen on landing is lost by checkout Customer Events pixel captures fbclid, _fbc and _fbp at landing and through checkout Journey timeline, landing visit with fbclid
Checkout gets a different visitor id Sessions resolved into one person by visitor id, email, phone, IP with user agent, and click id Journey timeline, order joined to the ad-click session
_fbc cookie missing or malformed _fbc rebuilt in Meta’s format from the landing URL’s fbclid Meta CAPI page, Purchase delivered
Purchase reaches Meta with no click trail Server-side Purchase from the paid-order webhook carries the captured identifiers and hashed email and phone Meta CAPI page, Purchase rows with delivery status
You can’t tell which orders really came from Meta Every matched order gets first-touch and last-touch attribution rows Attribution report, Meta Ads channel

Tell us what's broken. We'll fix your tracking — free.

Describe the tracking/attribution problem you're stuck on and we'll map it to a fix: server-side conversions to Meta, Google, TikTok and Pinterest, plus first-party tracking that survives Safari. No code required.

Sources

Frequently asked questions

QWhy does Events Manager show more purchases than Ads Manager?
Events Manager counts every Purchase your website sends, whatever brought the buyer. Ads Manager counts only the Purchases Meta can link to someone who saw or clicked your ad within the ad set's attribution setting. Sales from email, search or returning customers stay in Events Manager only, and so do Purchases that arrived without identifiers Meta could match.
QIs it normal for Ads Manager to show fewer purchases than Shopify?
Yes. Shopify counts every order, while Ads Manager counts only the ones Meta credits to its ads. The gap becomes a problem when Shopify shows many orders that started from a Meta ad click, with fbclid on the landing URL, and Ads Manager credits only a small share of them. That pattern usually means the Purchase is arriving without the click id.
QDoes sending Purchase through the Conversions API fix Ads Manager attribution?
Only if the server event carries the identifiers Meta matches on. A server-side Purchase built from the order alone reaches Events Manager but may carry no click id or browser id. Include fbc from the landing URL, fbp from the Meta base code's cookie, hashed email and phone, IP address and user agent, and keep one Purchase sender.
QCan I remove the Meta pixel from Shopify if I use the Conversions API?
Keep the Meta base code. It sets the _fbp browser cookie that server events use for matching, and _fbp can't be rebuilt from a URL. What you should switch off is a duplicate Purchase: if a server-side Purchase and a browser Purchase use different event ids, Meta counts both.
QWill PartialLeads make every Shopify purchase show in Ads Manager?
No. PartialLeads sends a Purchase for every paid order with the click id, browser id and hashed customer details it captured, which gives Meta more to match on. Whether Meta credits a sale to an ad still depends on Meta's own matching, the buyer's tracking choices on iOS, and your attribution setting. Matching is improved, not guaranteed.
QHow do I check whether my Purchase events include fbc?
In Events Manager, open your dataset, select the Purchase event and look at the event details for which customer information parameters were received and how often. Low coverage of the click id or browser id on Purchase explains weak attribution. The Event Match Quality score for Purchase summarises the same thing as one number.
What Do You Do When Fake Orders Pollute Your Shopify Pixel Data? A competitor or a bot places a pile of cash-on-delivery orders that will never be paid. Your thank-you page fires a Purchase for every one, and Meta starts hunting for more people like them. Here's how to confirm the orders are fake, contain the damage, and make sure only paid orders ever reach Meta as a sale. Why Does Meta Report a Purchase When Shopify Has No Order? Ads Manager says a $253 purchase came in. Shopify says nobody bought anything. One of them is counting something that isn't a sale, and it's almost never Shopify. Here's how to trace the phantom Purchase to its sender in Events Manager, shut off the four usual sources, and tie every Purchase Meta receives to an order id you can look up. Why Does Meta Count Extra Purchases per Order When Shoppers Return From a Payment Redirect? Your store shows 300 paid orders and Ads Manager shows 390 purchases. The culprit is usually a Purchase event bolted to the order status page, which fires again every time a shopper comes back from a bank or wallet redirect. Here is how to prove it, fix it without a vendor, and move Purchase to the one place it can only fire once: the paid order.
shopifymeta ads managerevents managerconversions apipurchase eventfbclidfbcfbpattribution settingclick idecommerce tracking

Find the qualified leads your forms are currently throwing away.

Install PartialLeads on one landing page, send traffic, and compare what your CRM captured against what PartialLeads recovered and qualified.

Start recovering qualified leads → View pricing