Pixelflow
FAQs

Enabling Meta Test Events Mode

What is the Meta "Test Events" Mode?

Enabling Test Events mode in Meta lets you see double check your setup to ensure your website is correctly sending information back to Meta (Facebook/Instagram) when someone takes an action like viewing a page, clicking “add to cart,” or completing a purchase. Think of it as a live dashboard where you can double-check that every important action is being tracked before you start spending money on ads. Without Test Events, you’d only find out later sometimes after wasting budget that something wasn’t tracking properly. It’s basically a safety check to make sure your ads and pixel are working as intended.

Here’s the difference in plain terms:

  • Normal Events are the regular signals your pixel sends to Meta whenever people take actions on your site (like purchases, sign-ups, or page views). These are the events Meta uses to optimize ads, measure results, and build audiences. They’re your “official” tracking data.

  • Test Events are a special mode you can turn on to watch those actions happen in real time, just for testing. They don’t affect your ad performance or reporting—they’re only for you (or your developer) to confirm that the pixel is firing correctly and sending the right details before you rely on the data for real campaigns. They're used to avoid flooding your existing campaigns with false data that you've created by clicking around your website.

👉 In short:

Normal Events = real tracking data used in ads.

Test Events = live debugging tool to make sure your tracking works properly.

Note: Test Events mode is automatically deactivated in 30 minutes after you enable it but you can go ahead and deactivate it immediately in edit Pixel modal in previous steps. Once Test Events mode is turned off, your events will start appearing in your Meta events manager Overview tab.

Please note: It may take up to 40 minutes for events to appear in your Meta events manager

Quick Instructions:

  • Go to the Meta Events Manager Overview page, click on “Data Sources” and select the Pixel you’d like to connect with PixelFlow

  • Click on “Test Events” and then on “Confirm your server’s events are set up correctly” section. Press the “Copy” button to copy the test code

  • Go back to the Pixelflow dashboard, enable the “Test Mode” option, paste this test code into the“Test Event Code” box and press the “Add Pixel” button in the Pixel modal

Detailed Instructions:

  • Go to your Meta Data Source, click on “Test Events” and then on “Confirm your server’s events are set up correctly” section. Press the “Copy” button to copy the test code

  • Make sure “Test Pixel” option is enabled and “Test Event Code” is copied in edit Pixel modal on Connect Pixel step

  • Go back to your Meta Data Source “Test Events” page and then on “Confirm your website`s events are set up correctly” section. Paste you website url in the"Enter Website URL" box and click "Test Events" button

  • Once your website is opened in a new browser tab, refresh it, navigate through different pages, visit configured tracking urls and interact with elements configured via classes (if there are any)

  • Go back to your Meta Data Source “Test Events” page and see both Browser and Server events received. In a few minutes Meta will deduoplicate events using shared event ID, which PixelFlow sends with every event and will mark them as "Deduplicated" as shown in the screenshot. That is a bold indicator that your setup is working correctly

Was this helpful?
Was this helpful?