My Meta (Facebook) Pixel isn't tracking any events
If your Meta Pixel shows as connected but Events Manager shows nothing, the most common causes are a wrong/unsaved ID, the wrong event left unchecked, or Meta's reporting delay — not a broken pixel.
Steps
- Go to Apps > Meta Pixel (or Store Settings > Pixels > Meta) and confirm the Pixel ID matches exactly what's in Meta Events Manager — retype it if you're unsure it saved correctly.
- Open Event Configuration and confirm the event you expect is checked. Note: Lead is not enabled by default — if you're waiting on a Lead event specifically, turn it on here.
- If the pixel is on a landing page, open that landing page's own pixel settings and make sure its status is Active — landing page pixels are separate from your main store's.
- Place a real test order or visit, then check Meta's Test Events tool (faster than Events Manager, which can lag).
- Rule out ad/tracking blockers in your own browser when testing — they silently block
fbevents.jsfrom loading.
Common problems
- Pixel looks connected, zero events after visits/ordersalmost always the ID wasn't saved, or the event type isn't checked in Event Configuration; re-save and re-test.
- PageView and ViewContent fire but Lead/Purchase never doescheck Event Configuration — Lead is off by default, and Purchase only fires once the buyer reaches an active thank-you page.
- Seeing what looks like duplicate PageView/ViewContentthis is usually a visitor re-entering the landing page in the same session, not a real duplicate; check Test Events for a duplicate Purchase, which is what actually affects ad reporting.
- Same checkout shows different event names in different teststhis reflects the order's status at that moment (e.g. pending vs. confirmed), not a tracking bug.
- Everything looks correctly configured and Meta still complainsthis can be a domain verification requirement on Meta's side rather than a pixel/store issue — see How to connect a custom domain to your Dropify store if Meta is asking you to verify a domain.