Are events deduplicated by PixelFlow?

Should you load your Meta Pixel separately to PixelFlow, or will PixelFlow load it alongside your CAPI?

PixelFlow loads both your Meta Pixel and Meta Conversions API simultaneously, ensuring that every event is triggered in real time through both channels.

Meta recommends sending events through both the browser (Pixel) and the server (Conversions API) because it increases reliability and improves attribution. However, this creates a risk of sending the same event twice. For more context on whether both channels are required, see Do You Have to Send Events via Browser and Server to Meta? Deduplication is the process of identifying and removing duplicate events so that Meta only counts each action once.

Without deduplication, you could see double-counting, inflated conversion numbers, and inaccurate campaign reporting.

PixelFlow automatically handles deduplication by assigning a unique event ID to every action sent. When Meta receives events from both Pixel and CAPI, it uses the event ID to merge them into a single event record. This guarantees:

• Accurate tracking without double-counting.

• Maximized data flow to Meta for better attribution.

• Optimized campaign performance with no extra setup required.

Note: You should not load your Meta Pixel separately on your website. PixelFlow already includes Pixel tracking and manages deduplication automatically.