Pixelflow
FAQs

Why are my events not showing in Meta Events Manager?

If your events are not appearing in Meta Events Manager, work through these steps to identify where the issue is occurring.

Step 1: Check the event status in your Event Logs

Open your Event Logs in PixelFlow and find the event in question. Check the status column— it should say Sent.

  • If the status shows Sent, PixelFlow successfully delivered the event to Meta. Continue to the next steps to troubleshoot the Meta side.

  • If the status shows an error or the event is missing entirely, the issue is on the PixelFlow side. See Why are there no events being tracked on my website? to troubleshoot your setup.

Event Logs show exactly what PixelFlow captured and sent to Meta. If the status is Sent, the problem is not with your PixelFlow setup.

Step 2: Verify your Pixel ID is correct

Confirm that the Pixel ID in your PixelFlow dashboard matches the Pixel you're checking in Meta Events Manager.

  1. Open your PixelFlow dashboard and note the Pixel ID connected to your site.

  2. Go to Meta Events Manager and confirm you're viewing the same Pixel/dataset.

If the Pixel IDs don't match, your events are being sent to a different dataset than the one you're checking. Update your PixelFlow settings with the correct Pixel ID.

Step 3: Check the Diagnostics tab in Meta

In Meta Events Manager, open your Pixel and navigate to the Diagnostics tab. Look for warnings or required actions.

Common issues:

  • Domain not accepted: Meta may require you to accept or verify events coming from your domain. If you see a prompt to accept traffic from a new domain, approve it.

  • Event parameters blocked: Meta may have flagged certain parameters. Review and address any data privacy warnings.

For a full breakdown of Meta warnings and how to handle them, see Common Facebook Events Manager warnings, errors, and suggestions.

Step 4: Check for restrictions on your Pixel

Meta can place restrictions on Pixels that violate terms or send non-compliant data. In Events Manager, check for any restriction notices or red warning banners at the top of your Pixel overview.

What to look for:

  • Core setup restrictions that limit data collection

  • Blocked event parameters

  • Policy violations requiring review

If your Pixel is restricted, follow Meta's remediation steps in Events Manager. Restrictions can prevent events from appearing in reporting even if they're technically being received.

Step 5: Check server-side vs browser-side event counts

Sometimes Meta takes time to populate server-side (CAPI) events in Events Manager, while browser-side Pixel events show up faster.

How to check:

  1. In Meta Events Manager, click on your event (e.g., PageView, Lead, Purchase).

  2. Click Export Data or view the breakdown by source.

  3. Compare the counts for Server-side vs Browser events.

If you see browser-side events but zero or very few server-side events, Meta may still be processing your CAPI events. Wait 20–40 minutes and recheck. PixelFlow sends events in real-time, but Meta's reporting can lag behind.

Prioritize server-side events for accuracy— they capture 30–40% more data that ad blockers and iOS privacy restrictions would otherwise block.

When to contact support

If you've worked through all five steps and your events still aren't appearing in Meta Events Manager after 48 hours, contact PixelFlow support for help. Book a free setup call and we'll investigate your integration directly.

Was this helpful?