Events Manager vs Ads Manager: which number?
Events Manager shows what Meta received. Ads Manager shows what was credited to the ad. See how to use both when you compare them with the store.

Events Manager shows the events Meta received, both attributed and unattributed. Ads Manager shows the events it credited to someone who was shown your ad, after discarding duplicates and applying rules. That is why the two numbers usually differ, even in the same period.
TL;DR
- Events Manager answers "what did Meta receive?". Ads Manager answers "what was credited to these ads?".
- Events Manager also includes organic events and traffic from other platforms, including people who were not shown your ad.
- On the Data sources page, the Total events count is not deduplicated. In Ads Manager, events are deduplicated.
- If Events Manager is already far from the store, the problem starts with the send. If it is close and Ads Manager is far, the gap is attribution.
What does each dashboard show?
Meta describes the two surfaces in Differences Between Event Counts in Meta Ads Manager, Ads Reporting and Events Manager. Each tool serves a different purpose, and the event types are not identical either.
| Question | Events Manager | Ads Manager |
|---|---|---|
| What appears | Standard events, custom events and custom conversions | Standard events and custom conversions |
| Attributed or unattributed | Both: organic, credited to your Meta ads, and traffic from other platforms | Only events credited to someone who was shown your ad, after discarding duplicates, data policies or regulations |
| Deduplication | On the Data sources page, the Total events count is not deduplicated | Events are deduplicated |
Ads Reporting sits closer to Ads Manager than to Events Manager: it also shows attributed, deduplicated events. The practical difference for a store owner is between "what arrived" and "what was credited to the ad".
Why does Events Manager often show more?
Because it includes events Ads Manager leaves out. Meta's help says Events Manager reports events even if they are from a person who was not shown your ad or, potentially, a person who does not use Meta technologies.
Deduplication widens that gap. If Meta receives the same event more than once over a short period, Ads Manager may keep one and discard the rest. On the Data sources page, the total can count those repeats. The Custom conversions page in Events Manager follows a separate rule; Meta's help treats that surface as distinct from the Data sources total.
None of these rules is the store's record. The store counts the order at checkout, with status. Events Manager counts what the pixel or the Conversions API managed to send. Ads Manager counts what fits the ad set's attribution. Meta says Ads Reporting counts can differ from third-party tools in About Conversion Count Differences Between Meta Ads Reporting and Third-Party Reporting Tools.
How do I use both to find the problem?
Compare a closed week, with the same time zone, and start with the store: paid orders, with cancellations and refunds set aside.
Then open Events Manager. If the number of purchases Meta received is already far from paid orders, the problem starts with the send: the tag does not fire, a blocker stops the pixel, the thank-you page does not load, or the same order arrives more than once.
If Events Manager is close to the store and Ads Manager is far from it, look at the ad set's attribution setting, view-through credit and the impression date. In About Attribution Models and Attribution Settings Meta describes the default windows for website conversions, including click-through and view-through credit. The ads report uses the impression date, not necessarily the day of payment, as How Conversions Are Attributed in Commerce Manager states. Why Meta Ads sales don't match your store covers those rules. The wider picture with Google Ads and GA4 is in Why GA4, Meta, Google Ads and the store don't match.
Server-side tracking can increase the events Events Manager receives when the browser fails. That does not turn the Ads Manager number into the store's order total. What Is Server-Side Tracking? explains the reach and the limits.
Which number do I compare with the store?
It depends on the question.
If the question is "is Meta receiving purchases from the site?", compare paid orders with Events Manager. If the question is "how many purchases did Meta credit to these ads?", use Ads Manager, always with the same window across the campaigns you compare. If the question is "how much did the store actually sell in this period?", the number that matters for cash is paid store orders.
All three can be useful at the same time. Adding Ads Manager to Google Ads to match the store is still a mistake: both platforms can credit the same order.
When does it help to see both next to the store?
When you want all three answers in the same window, without switching dashboard and time zone at every check. Independent attribution tools exist for that. Clakta is one of them: it brings together the numbers Meta reports and the orders the store confirmed, side by side. Revenue comes from those same store orders, with status; each order enters that total once; a pending delayed payment is not revenue yet; refunds and cancellations update the same order.
Clakta does not send events to Meta and does not change Events Manager or Ads Manager. The pixel stays in place. Clakta runs alongside it, does not change the platform report and does not replace GA4 (What is Clakta?, How attribution works). For stores, see the ecommerce page.
Events Manager, Ads Manager and the store remain different numbers. In Clakta, what the platform reports and what the store recorded appear on the same screen.
Frequently asked questions
Is it normal for Events Manager to show more purchases than Ads Manager?
Yes. Events Manager includes events not attributed to an ad and, on the Data sources page, the Total events count is not deduplicated. Ads Manager shows only what was credited to someone who was shown your ad, after deduplication.
Which of the two should match the store?
Neither is the store's cash register. Events Manager can be closer to the volume the site sent. Ads Manager answers the attribution question. The list of paid orders is still the store's.
If both Meta dashboards are far from the store, where do I start?
With Events Manager. If what Meta received is already far from paid orders, the problem starts with the event being sent.
Does Clakta replace Events Manager?
No. Clakta brings together what Meta reports and the store's orders, side by side. It does not send events to Meta, does not change those two dashboards and does not replace GA4.