Overview
After completing your PixelFlow setup on Squarespace, Framer, or any other platform, you need to verify that your Conversions API (CAPI) is correctly tracking events and sending data to Meta. This guide walks you through the complete testing process to ensure your setup is working properly, events are firing correctly, and deduplication is functioning as expected.
Prerequisites
Completed PixelFlow setup with script installed on your website
Meta Pixel ID and Access Token configured in PixelFlow
Website published with the PixelFlow script in the header
Access to Meta Events Manager
Access to your PixelFlow dashboard
Before You Begin
Remove any existing Meta Pixel scripts from your website before testing. PixelFlow loads both the Meta Pixel and Conversions API automatically with built-in deduplication. Having a separate Meta Pixel script will cause duplicate events and inaccurate tracking. Check your website's code injection settings, header scripts, and platform integrations (like Squarespace's Facebook Pixel integration) and remove all existing Meta Pixel code.
Events may take up to 40 minutes to appear in Meta Events Manager after they're triggered. During initial testing, be patient and allow sufficient time for data to flow through the system.
Step 1: Use the Built-in Setup Test
PixelFlow includes an automatic setup verification tool that checks for incoming events immediately after installation.
During the PixelFlow setup wizard, you'll reach Step 4: Test Your Setup
The system will display "Awaiting for the events" with a loading indicator
Open your website in a new browser tab
Navigate through a few pages to trigger PageView events
Click any buttons or visit URLs you've configured for tracking
Return to the PixelFlow dashboard
Success! When PixelFlow detects your first event, you'll see a confetti animation and a "Congrats" message. This confirms your CAPI connection is working and events are being sent to Meta successfully.
What happens during testing:
PixelFlow polls for events every 10 seconds for up to 1 hour
The system checks that events have
is_sent_successfully: truestatusIf an event fails, you'll see the full error message with troubleshooting steps
Pro tip: If you're stuck waiting for events during the test, try opening your website in an incognito/private browser window and performing actions like form submissions or page visits. This ensures you're triggering fresh events without cached scripts interfering.
Step 2: Check PixelFlow Event Logs
The PixelFlow dashboard provides detailed event logs where you can see exactly when and how each event was tracked.
Log in to your PixelFlow dashboard
Click Events in the left sidebar navigation
Select your site from the dropdown (if you have multiple sites)
Review the "Detailed Events" table
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:
Use the Filters button to narrow down events by:
Status (Sent or Error)
Event type (Lead, Purchase, PageView, etc.)
Tracking URL
Adjust the Date Range Picker to view events from different time periods (default is last 3 months)
Click the Refresh button to see the latest events
Expand any event row to view the full JSON payload sent to Meta
Common issue: If you see "There are no events for a selected date range for this site," either your script isn't installed correctly, or no events have been triggered yet. Verify your script installation and try visiting your website again to trigger events.
Step 3: Verify Events in Meta Events Manager
After confirming events appear in PixelFlow, check that they're reaching Meta Events Manager correctly.
Go to Meta Events Manager
Select your Pixel from the Data Sources list
Click on the Overview tab
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
Healthy setup indicator: You should see both browser-based events and server-side events on your Meta Events Manager chart. The green line (server events from PixelFlow CAPI) should closely follow the blue line (browser events from Meta Pixel). This shows PixelFlow is successfully sending events through both channels.
Step 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.
In Meta Events Manager, select your Pixel
Click on the Test Events tab
Scroll to "Confirm your server's events are set up correctly"
Click the Copy button to copy the test event code
Go to your PixelFlow dashboard, edit your Pixel settings
Enable Test Mode and paste the test event code into the Test Event Code field
Update your script on your website and republish
Back in Meta Events Manager Test Events, scroll to "Confirm your website's events are set up correctly"
Enter your website URL and click Test Events
Navigate through your website in the new browser window that opens
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
Note: Test Events mode automatically deactivates after 30 minutes, but you can manually disable it anytime. Once disabled, events return to normal tracking and appear in the Overview tab instead of the Test Events tab.
For detailed setup instructions, see our guide on Enabling Meta Test Events Mode.
Step 5: Check for Duplicate Events
Verifying that events are not duplicated is just as important as confirming they're firing.
How to identify duplicates:
In Meta Events Manager, look at your event activity chart
Check if event counts are significantly higher than your actual website traffic
In PixelFlow event logs, expand an event and review the JSON payload for the
event_idfieldCheck if the same action (e.g., page visit, form submission) appears multiple times with different event IDs
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
Fix duplicates immediately: Remove all standalone Meta Pixel scripts from your website. PixelFlow handles both Pixel and CAPI with automatic deduplication, so no additional Pixel code is needed. Check your platform's Code Injection settings, native Facebook integrations, and page-specific scripts.
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.
Step 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:
In Meta Events Manager, go to the Overview tab
Look at the event activity chart—you should see both browser events (blue) and server events (green)
Check that total event counts are reasonable (not double what you expect)
If using Test Events mode, events will be explicitly marked as "Deduplicated"
Deduplication success indicator: In Test Events mode, Meta will show "Deduplicated" status next to events that were received from both browser and server with matching event IDs. This is the clearest confirmation that PixelFlow's deduplication is working correctly.
PixelFlow manages this process automatically—no manual configuration required. For more background, read Are Events Deduplicated by PixelFlow?
Step 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:
Log in to Squarespace and go to Pages
Expand Custom Code in the bottom left sidebar
Click Code Injection
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)Check the Footer section and individual page code injections as well
Additionally, go to Settings > Advanced > External Services
If a Facebook Pixel ID is entered, remove it
Click Save and republish your site
For Framer:
Open your Framer project
Go to Settings (gear icon in the top right)
Select General > Custom Code
Look in the Start of <head> tag and End of <body> tag sections
Delete any Meta Pixel code (starts with
!function(f,b,e,v,n,t,s))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
How to verify removal: After deleting old pixel code, use the Facebook Pixel Helper Chrome Extension to check your website. You should only see one pixel firing (the one from PixelFlow), not multiple instances.
Troubleshooting
Symptom | Likely Cause | Resolution |
|---|---|---|
No events appearing in PixelFlow event logs | Script not installed or not published | Verify the PixelFlow script is in your website's header code injection. Republish your website. Visit your site in an incognito window to trigger events. |
Events in PixelFlow logs but not in Meta Events Manager | Incorrect Pixel ID or Access Token | Double-check your Meta Pixel ID and Access Token in PixelFlow settings. Update if needed and reinstall the script on your website. |
Events showing "Error" status in PixelFlow | Invalid API credentials or Meta policy violation | Expand the event row to see the full error message. Common fixes: verify Access Token permissions, check Meta Business Manager access, ensure Pixel is not restricted. |
Double the expected number of events | Multiple Meta Pixel scripts installed | Remove all standalone Meta Pixel code from your website. Disable platform native Facebook integrations. Keep only PixelFlow. |
Events not deduplicated in Meta Events Manager | Old pixel script interfering with event IDs | Remove any manually installed Meta Pixel code. PixelFlow assigns matching event IDs automatically—external pixels break this process. |
Test Events mode shows no activity | Test event code not configured or script not updated | Ensure you've pasted the test event code into PixelFlow settings, updated your website script, and republished your site. |
Events delayed by 20-40 minutes | Normal processing time for Meta Events Manager | This is expected behavior. Events show in PixelFlow logs immediately but may take up to 40 minutes to appear in Meta's system. |
Still stuck? Contact PixelFlow support or book a free setup call. Have your event logs and Meta Events Manager screenshots ready to help diagnose the issue faster.
What's Next
Once your setup is verified and events are tracking correctly:
Configure additional event tracking URLs for specific conversions (form submissions, purchases, etc.)
Set up class-based tracking for buttons and interactive elements (platform-specific guides available)
Review your event blocking rules to filter bot traffic or prevent duplicate conversions from page refreshes
Monitor your event match quality score in Meta Events Manager and improve it with proper event parameters
Start using the data in your Meta ad campaigns to optimize targeting and attribution
Platform-Specific Setup Guides
Need to revisit your initial setup? Check out our platform guides: