> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.adnabu.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Why do my Meta Events Manager numbers differ from my browser Pixel counts?

## A quick guide to why Events Manager, browser tools, and other analytics rarely show the exact same event count.

Some gap between these numbers is normal — it doesn't mean tracking is broken.

**Common reasons for the gap**

* **Deduplication.** Events Manager shows one number after matching browser Pixel and Conversions API (CAPI) events by name and ID — not the sum of both. [Learn more.](https://www.facebook.com/business/help/2041148702652965?id=818859032317965)
* **Blocked browser events.** Ad blockers, Safari/Firefox tracking prevention, and iOS 14+ can stop the browser Pixel from firing. CAPI sends the same event from our server regardless, so Events Manager can show more than a browser-only tool.
* **Delay.** CAPI events usually land within a few minutes, not instantly — checking too soon can make counts look off.
* **Rejected events.** Meta can silently discard a malformed server event, which can make CAPI totals a bit lower than expected.
* **Different metrics.** Tools like Shopify Analytics or Google Analytics count sessions or orders, not the same event structure Meta uses — they're not directly comparable.
* **Other sources on the same pixel.** Another app or script sending events to the same Pixel ID shows up in Meta but not in our app's Analytics.

**Which number to trust**

Use Meta Events Manager for ads and reporting — it's what Meta's algorithm actually sees. Browser tools are best for confirming the Pixel fires, not for totals.

If the gap looks unusually large, check that **Conversion API** still shows **Enabled** on the **Homepage** for that pixel — an expired token is the most common cause.