Pixel & CAPI loaded together

One script. Browser pixel and Conversions API, deduplicated

Free trial. No card, no tag manager.

Every event goes out twice, and is counted once

When an event fires, PixelFlow sends it from the browser through the Meta pixel and from its servers through the Conversions API. Both carry the same event ID, so Meta keeps one and discards the duplicate. You get the reach of server-side without the double counting.

yoursite.com · one script

Browser pixel

fbq() in the page

Conversions API

PixelFlow server

Meta · 1 Purchase, same event_id

Browser pixel

Fires in the page as normal, for everything Meta’s pixel does well.

Conversions API

Sent from PixelFlow’s servers, so it arrives even when the browser event is blocked.

Shared event ID

Automatic on every event. No manual event_id plumbing.

Live events

Purchase

{…}

12:04:11

Lead

{…}

12:03:58

PageView

{…}

12:03:41

Identifiers that raise Event Match Quality

Server events carry the visitor’s click ID, browser ID, IP and user agent, plus hashed email, phone and name when the event has them. That is what lifts match quality and lets Meta attribute more of your conversions.

No Google Tag Manager, no code

Add one script to your site and tag events with the Visual Tagger or your platform’s native integration. Server-side is on from the start, not a second project.

yoursite.com/pricing

Buy now

Tag this element

Purchase

Fires on every matching button

yoursite.com

Main pixel

all events

EU pixel

all events

Agency pixel

Purchase only

Test pixel

test events

Works the same for every pixel you add

Add more Meta pixels to the site and each one gets both channels, deduplicated, with no extra scripts.

FAQ

Frequently asked questions

Frequently asked questions

Frequently asked questions

Everything you need to know about how PixelFlow sends events to Meta.

Do I still need the Meta pixel code on my site?

No. PixelFlow’s script loads the pixel for you.

What is the Conversions API?

Meta’s server-to-server way of receiving events. PixelFlow sends every event through it from its own servers, alongside the browser pixel.

How does deduplication work?

Both copies of an event carry the same event ID. Meta matches them and counts one.

Will I see events twice in Events Manager?

You will see both received, marked as deduplicated. Only one is counted.

Does this work with ad blockers?

The server-side copy still arrives when the browser copy is blocked, which is the point of sending both.

Can I turn the browser pixel off and send server-side only?

Yes, per site, if your setup calls for it.

Smarter, server-side tracking

Start sending accurate conversions today - no tag manager, no code, no developer required.

Compatible with

  • GoHighLevel logo
  • Kajabi logo
  • ClickFunnels logo