Practical checklist
How to check Meta Pixel and event delivery
A Pixel code on the website does not prove that tracking is correct. Check events, parameters, duplicates and data quality in Events Manager.
01
1. Use Test Events in Events Manager
Select the data source, open Test Events and perform real website actions such as a page view, form submission, add to cart or purchase.
Events should appear with clear names and parameters. One action should not create unexplained duplicates.
02
2. Check browser events with Pixel Helper
Meta Pixel Helper shows whether the Pixel loads, which ID is used and which events are sent.
Duplicate PageView events, an unexpected Pixel ID or missing parameters require investigation.
03
3. Review diagnostics and match quality
Check warnings, event delay and Event Match Quality. Server events should send permitted identifiers in the correct format.
- Remove obsolete domains and events
- Check value, currency and content IDs
- Match browser and server event names
- Retest after website changes
04
4. Verify Pixel and CAPI deduplication
When one action is sent from both browser and server, both versions need the same event name and event_id.
Without correct deduplication reporting may overcount conversions; without server events some data can be lost.