How to Test and Verify Your PixelFlow CAPI Setup

Overview

After completing your PixelFlow setup you may want to verify everything is setup properly. Below is a number of ways to verify your setup

1. Use the Realtime Event Monitor

The Realtime Event Monitor is a small widget that loads on your website which only you can see. It will let you click any element and see what event has been triggered and what data has been collected. Read more about the Realtime Event Monitor here.

2: Check PixelFlow Event Logs

In your PixelFlow dashboard, you have access to event logs where you can see exactly when and how each event was tracked.

What to look for in event logs:

• Status column: Should show "Sent" (green checkmark) for successful events

• Event Type: Verify the correct event names (PageView, Lead, Purchase, etc.)

• Tracking URL: Check that URLs match your configured event URLs

• Processed at: Timestamp shows when the event was tracked

• Pixel ID: Confirms events are sent to the correct Meta Pixel

Filtering and analyzing your events:

1. Use the Filters button to narrow down events by:

   • Status (Sent or Error)

   • Event type (Lead, Purchase, PageView, etc.)

   • Tracking URL

2. Adjust the Date Range Picker to view events from different time periods (default is last 3 months)

3. Click the Refresh button to see the latest events

4. Expand any event row to view the full JSON payload sent to Meta

3: Verify Events in Meta Events Manager

After confirming events appear in PixelFlow, check that they're reaching Meta Events Manager correctly.

1. Go to Meta Events Manager

2. Select your Pixel from the Data Sources list

3. Click on the Overview tab

4. Check the activity chart for incoming events

What you should see:

• Recent events appearing in the activity timeline

• Event counts matching (or close to) what you see in PixelFlow logs

• Both Browser events (blue) and Server events (green) on the chart

• Events marked as "Deduplicated" when the same action was tracked by both Pixel and CAPI

4: Test Events Mode (Optional but Recommended)

For real-time debugging and verification, use Meta's Test Events tool to watch events as they arrive.

1. In Meta Events Manager, select your Pixel

2. Click on the Test Events tab

3. Scroll to "Confirm your server's events are set up correctly"

4. Click the Copy button to copy the test event code

5. Go to your PixelFlow dashboard, edit your Pixel settings

6. Enable Test Mode and paste the test event code into the Test Event Code field

7. Update your script on your website and republish

8. Back in Meta Events Manager Test Events, scroll to "Confirm your website's events are set up correctly"

9. Enter your website URL and click Test Events

10. Navigate through your website in the new browser window that opens

11. Return to the Test Events tab in Meta Events Manager

What Test Events shows you:

• Events appear in real-time as you trigger them (within seconds)

• Both Browser and Server events are listed separately

• Deduplication status shows which events were successfully merged

• Event parameters and data quality are visible for each event

For detailed setup instructions, see our guide on Enabling Meta Test Events Mode.

5: Check for Duplicate Events

PixelFlow automatically loads your Pixel & Conversions API together so that events are sent both ways using the same eventID. This ensures events are correctly deduplicated on Meta's side.

However, if you are running other Facebook scripts or loading your Pixel separately it can cause duplicate events.

Common causes of duplicate events:

• Multiple Meta Pixel scripts installed: Your website has both PixelFlow and a manually added Meta Pixel script running simultaneously

• Platform native integrations: Squarespace, Webflow, or other platforms have their own Facebook Pixel integration enabled alongside PixelFlow

• Page reload tracking: Users refreshing thank-you pages or checkout confirmation pages trigger the same conversion multiple times

• Multiple tracking rules: The same event is configured using both a tracking URL and a class-based trigger

How to prevent duplicates:

• Only use PixelFlow for Meta tracking—do not add the Pixel separately

• Check your event logs regularly to verify clean tracking

• Avoid setting up the same event type in multiple ways (don't use both event URLs and classes for the same trigger)

• Use event blocking rules to prevent duplicate triggers from page refreshes

For more details, see our article on Why Some Events Are Duplicated.

6: Verify Deduplication is Working

PixelFlow automatically deduplicates events by sending the same event_id through both the browser (Pixel) and server (CAPI). Meta uses this ID to merge duplicate events into a single record.

How to confirm deduplication:

1. In Meta Events Manager, go to the Overview tab

2. Look at the event activity chart—you should see both browser events (blue) and server events (green)

3. Check that total event counts are reasonable (not double what you expect)

4. If using Test Events mode, events will be explicitly marked as "Deduplicated"

PixelFlow manages this process automatically—no manual configuration required. For more background, read Are Events Deduplicated by PixelFlow?

7: Remove Old Meta Pixel Scripts

If you previously had Meta Pixel installed manually or through platform integrations, you must remove it to prevent duplicate tracking.

For Squarespace:

1. Log in to Squarespace and go to Pages

2. Expand Custom Code in the bottom left sidebar

3. Click Code Injection

4. In the Header section, locate and delete any code that starts with <!-- Meta Pixel Code --> or <script>!function(f,b,e,v,n,t,s)

5. Check the Footer section and individual page code injections as well

6. Additionally, go to Settings > Advanced > External Services

7. If a Facebook Pixel ID is entered, remove it

8. Click Save and republish your site

For Framer:

1. Open your Framer project

2. Go to Settings (gear icon in the top right)

3. Select General > Custom Code

4. Look in the Start of <head> tag and End of <body> tag sections

5. Delete any Meta Pixel code (starts with !function(f,b,e,v,n,t,s))

6. Save changes and republish your website

For Other Platforms:

• Check your platform's code injection settings, header/footer scripts, or third-party integration settings

• Remove any Facebook/Meta Pixel code snippets

• Disable native Facebook Pixel integrations if your platform offers them

• Republish your website after making changes