Why it happens
The events land in another dataset
The events land in another dataset
The page fires a pixel ID that is not the dataset you opened. Common after an agency handover or a second store app.
Server events carry a test code
A test_event_code left in the Conversions API payload sends every server event to the Test events tab only. Overview stays empty.
Consent holds the pixel
Your own visit fires nothing until you accept cookies, so the check you just ran sent no events.
The view hides them
A short date range, a filter on one event, or the wrong business selected in the top left shows an empty screen for a working dataset.
The event call breaks before it sends
A track call that runs before the base code loads, or a script error earlier on the page, stops the event in the browser.
How to fix it, step by step
Check the dataset ID
In Events Manager, open Data sources and note the dataset ID. On the page, filter the Network tab for facebook.com/tr and confirm the id parameter is the same number.
Widen the view
Set the date range to the last 28 days, clear filters, and confirm the right business is selected.
Use Test events
Open Test events, enter your URL and browse. Events showing here but not in Overview are either very recent or flagged as test.
Remove test codes from server events
Ask whoever runs the Conversions API to drop test_event_code from production requests. It belongs only in testing.
Read Diagnostics
The Diagnostics tab names events Meta received but could not use, and why.
Steps checked against Meta Business Help Center articles: Test your events in Events Manager; About diagnostics in Events Manager; Troubleshoot your Meta Pixel.
Sprites diagnoses this
Sprites diagnoses it
Sprites reads your pixel and CAPI health and shows where it breaks: which dataset the events actually reach, and which side never arrives.
What Sprites does
- Lists every pixel on the ad account and reads the events each one received, so events landing in another dataset show up.
- Splits each event into browser and server counts, so the side that never reaches Meta is obvious.
- Reads Meta's diagnostics for each dataset in plain words.
What it doesn't do
- Read the Test events tab
- Change the code on your site or your server
- Send events to the Conversions API
Questions
Why are my pixel events not showing in Events Manager?
Most often they go to a different dataset. After that: a consent banner, a test code on server events, or a date range that hides them.
How long do events take to appear?
Seconds in Test events. Up to about 20 minutes in the Overview graph.
Why do events show in Test events but not Overview?
Either they are very recent, or they were sent with a test code. Events with a test code never reach Overview.
Why does Events Manager show my pixel but no events?
The dataset exists but nothing reports to it. The site fires a different pixel, or none.
See where it breaks
Connect your accounts. Sprites reads them side by side and shows you exactly where the numbers split.