Why it happens
The test browser blocks the pixel
The test browser blocks the pixel
An ad blocker, a privacy browser or strict tracking protection stops the script. The test sees nothing while real visitors fire normally.
Consent was never accepted
The pixel waits for the cookie banner. Skip it and the test stays empty.
The wrong dataset is open
Test events lives inside one dataset. Testing a site that fires another pixel shows nothing here.
Server events lack the test code
Server events show in Test events only when the request carries the test_event_code from that tab.
The URL redirects
A redirect to another domain or a login wall takes the test session somewhere the pixel does not run.
How to fix it, step by step
Open the right dataset
In Events Manager, open Data sources, select the dataset your ads use, then Test events.
Test in a clean window
Enter the URL, open the site from the tab, accept cookies, and turn off blockers. Browse a few pages.
Test server events with the code
Copy the test code shown in the tab into test_event_code on a server request, send it, and watch it arrive.
Check real traffic
Go to Overview. If events arrived in the last hour, tracking works and only the test setup is off. Compare with what your analytics sees in GA4 vs Meta.
Take the code out
Remove test_event_code from production requests when you finish.
Steps checked against Meta Business Help Center articles: Test your events in Events Manager; Troubleshoot your Meta Pixel; About the Conversions API.
Sprites diagnoses this
Sprites diagnoses it
Sprites reads your pixel and CAPI health and shows where it breaks, so you know whether the tracking or only the test is the problem.
What Sprites does
- Reads whether real browser and Conversions API events reach the dataset, outside the test tool.
- Reads the last time Meta received anything from the pixel.
- Reads Meta's own diagnostics for the dataset.
What it doesn't do
- Read the Test events tab or your test code
- Send test events
- Open your site in a browser
Questions
Why is Meta Test events not showing anything?
A blocker or a consent banner in your test browser, the wrong dataset open, or server events sent without the test code.
Do test events count in my results?
No. They show in the Test events tab only and never reach reporting or optimization.
Where do I find the test event code?
In Events Manager, your dataset, Test events, under the server events section.
Test events works but Overview is empty. Why?
Give Overview about 20 minutes. If it stays empty, check that production server events do not carry the test code.
See where it breaks
Connect your accounts. Sprites reads them side by side and shows you exactly where the numbers split.