Why Events Manager shows purchases and Ads Manager shows fewer

By the HonestTag team · Published November 5, 2026 · Updated November 11, 2026

One screen lists what Meta received. The other lists what Meta credits to your ads.

Two screens, two questions

A Purchase showing as active in Events Manager, even with a high match score, tells you the event arrived. It says nothing about which ad, if any, gets the credit. Meta's page on event counts draws the line in one sentence: "Events Manager shows most events that have been received, while Ads Manager and Ads Reporting show attributed events that have been received."

So Events Manager answers "did the event reach Meta?" and Ads Manager answers "which of those does Meta credit to an ad?" To check the first with a test order, see how to test your purchase tracking. Nothing requires the second count to come close to the first. How much lower it sits depends on how many of your sales have anything to do with Meta ads.

Why the two counts part ways

• The buyer was never shown your ad. Events Manager includes "organic traffic, events attributed to your Meta ads, and traffic driven from other platforms." A customer who came from your email, from Google or straight to your site still sends a Purchase, and it still shows in Events Manager.
• The same purchase is in the count more than once. Meta says "Events are not deduplicated in the Total events count." Meta says Ads Manager's events are deduplicated, but it has to recognize the copy first. For a purchase sent by both a browser pixel and a server, its deduplication page says "The event_id must be identical for both events", or the event name has to match along with an external ID or the fbp value. A copy Meta cannot pair may stay in. More on this in duplicate purchase events.
• The purchase fell outside your attribution setting. On standard attribution you choose it per ad set. Click-through counts events "within 1-day or 7-day after a link click on your ad", and view-through counts events "within 1-day after an impression of your ad." On a 7-day click setting, a shopper who clicks and buys ten days later shows in Events Manager and not under that setting in Ads Manager. Your own buyers' timing is their click-to-order lag.
• The event is a custom event. Meta lists Ads Manager as showing standard events and custom conversions. Events Manager also shows custom events. Ads Reporting adds "Custom events that were previously used to optimize ad delivery." So an event under a name you or an app chose can sit in Events Manager and never add to the Purchases column, however many arrive.
• You are reading different days. Meta's checklist says "Check that both of your reporting tools are set to the same time zone", and Ads Reporting can report "by time of conversion or time of exposure when the impression was served." A sale on Thursday from an ad served on Monday can sit on a different day from the event.

A worked example

The numbers below are made up to show the arithmetic. They are not from a store. In one week Events Manager's Total events shows 40 Purchase events. Shopify took 30 orders that week. Ads Manager shows 15 purchases.

• 40 events, 30 orders: 10 events are repeats of an order already counted, and Meta recognizes them as copies. 30 left.
• 12 buyers never saw an ad: they came from email and Google. 18 left.
• 3 buyers clicked an ad more than 7 days earlier: outside this ad set's setting. 15 left.

That is 40 in one screen and 15 in the other, with nothing wrong except the 10 repeats. Another made-up case, a small campaign in a quiet week: the store takes 4 orders, 3 from returning customers through an email and 1 from a Google search. Events Manager shows 4 and Ads Manager shows 0, and 0 is correct. On a small budget this happens often enough that a zero needs checking before it needs fixing.

When the gap is a real fault

It is a fault when you can name an order that clicked a Meta ad, inside your setting, and Meta shows no credit for it. If the gap opened from one day to the next, a sudden drop in Meta purchases covers that case. These are the usual causes:

• The ad set points somewhere else. When the dataset and conversion event an ad set names are not the ones you read in Events Manager, the two screens are not talking about the same thing.
• The click did not survive the trip. Meta's ClickID "is passed with the URL" when someone clicks an ad, and looks like ?fbclid=... on the address. An address that has lost it by the time your store has loaded is one way the click goes missing between the ad and the order.
• The event arrived with too little to match on. Meta says "Matched events help you attribute conversions to your ads." Its match quality score reflects the customer information on the events and how many of them matched a Meta account, though a good score on its own does not prove any single order was credited.

What the order check cannot see

Checking orders against Meta's credit runs in one direction. It can find orders Meta should have credited. It cannot prove Meta was wrong to credit one. Meta says that if a person "sees a Facebook ad for your product and doesn't click, but later browses your website and decides to purchase", it may attribute that sale to the ad, and such an order shows no Meta click in Shopify. So Ads Manager can credit orders you cannot trace, while still leaving out others. Ad platform purchases vs Shopify orders covers that side of the comparison.

What this means

For the same days, set Events Manager's Total events, your Shopify orders and Ads Manager's purchases side by side.

• More events than orders points to repeats: one purchase reaching Meta more than once, under event IDs it may not pair.
• Ads Manager well below your orders, with most buyers from email, search or direct visits, is attribution working. Shopify's conversion summary shows where a buyer came from, though it can take up to 48 hours, and draft orders and visits with cookie tracking blocked have none.
• A Meta click outside your attribution setting is the window working; a Meta ad order inside it with no credit is the real fault: the ad set reads another event, the ClickID was lost before your store loaded, or the event had too little to match on.

Repeats Meta cannot pair can stay in its purchases and flatter its return on ad spend. Uncredited sales make a working campaign look weak, and budget moves away from it. HonestTag gives you the store's side: what Meta claims beside the new customers your orders show it first brought, and on paid plans what each order sent to Meta, or why it was not sent.

How HonestTag helps

HonestTag cannot see inside Meta's attribution, so it will not tell you why Meta skipped a given order. What it gives you is your store's side of the comparison.

• On the free Mirror plan, The Gap's "Who brought your customers" shows what Meta claims for the 14 days ending yesterday beside the new customers whose first recorded ad click or ad-tagged link was Meta, from your own orders. It sends no purchases to any ad platform. Critical alerts when tracking breaks are emailed on every plan.
• On paid plans, The Gap sets "Platform-reported purchases" beside "Purchases HonestTag sent it" for each platform, so what Meta reports sits next to what it was sent. Purchases that were not sent are counted, with the reason.
• On paid plans, order proof keeps a record on each order, so you have more than Shopify's conversion summary to go on. Open any order and see the click ID, the timestamps, how it was matched, and what each platform was sent or why it was not.
• On paid plans, every verified web purchase is sent to your connected destinations from HonestTag's server, within your plan's limit, so it does not depend on the shopper's browser. Start with HonestTag_Purchase, which counts every purchase HonestTag sends, new and returning customers both.
• One thing to expect: HonestTag's events are custom events, so by default they do not add to Meta's Purchase column. A confirmed event can be your ad set's conversion event directly. For reporting, HonestTag creates custom conversions on paid plans when your Meta connection allows it. The Meta setup guide covers this and the standard Purchase switch.

Install HonestTag free from the Shopify App Store and see, on the Mirror plan, what Meta claims beside the new customers your own orders show it first brought.

The free tracking check sets out how to read a normal week of a platform's purchases against your Shopify orders for the same days.

Frequently asked questions

Sources

• Meta Business Help: Differences between event counts in Meta Ads Manager, Ads Reporting and Events Manager, read November 5, 2026
• Meta Business Help: About attribution models and attribution settings, read November 5, 2026
• Meta Business Help: Troubleshoot common reporting differences between Meta Ads Reporting and third-party reporting tools, read November 5, 2026
• Meta Business Help: About conversion count differences between Meta Ads Reporting and third-party reporting tools, read November 5, 2026
• Meta Business Help: About deduplication for Meta Pixel and Conversions API events, read November 5, 2026
• Meta Business Help: About event match quality, read November 5, 2026
• Meta Business Help: About reviewing custom events in Meta Events Manager, read November 5, 2026
• Meta for Developers: ClickID and the fbp and fbc parameters, read November 5, 2026
• Shopify Help Center: Viewing order conversion summary, read November 5, 2026
• HonestTag docs: connect Meta
• HonestTag: Order proof
• HonestTag pricing and plan limits