All integrations

Meta Server-Side Tracking

Meta Server-Side Tracking

Meta Server-Side Tracking

Send every conversion to Meta from the server.
No tag manager, no code.

Send every conversion to Meta from the server.
No tag manager, no code.

Connect with your Facebook login, add the script, choose your conversions and events and PixelFlow sends your data via browser & server automatically

Connect with your Facebook login, add the script, choose your conversions and events and PixelFlow sends your data via browser & server automatically

LIVE EVENTSSent to Meta
PurchaseStripe€149.00Sent
ScheduleCalendlyDemo callSent
LeadFormContact formSent
ViewContentPage/pricingSent
AddToCartButtonAdd to cartSent
1,284 events todayEvent Match QualityEMQ8.6

Why send conversions to Meta server-side?

Why send conversions to Meta server-side?

Why send conversions to Meta server-side?

Server-side tracking sends data back to your ad platform in a way that can't be blocked, unlike the standard Pixel which loads in the browser and can be blocked by adblockers, iOS and browsers.

Sending more (and better) data to your ad platforms helps them understand who your ideal customers are, and show your ads to more of them.

Server-side tracking sends data back to your ad platform in a way that can’t be blocked, unlike the standard Pixel which loads in the browser and can be blocked by adblockers, iOS and browsers.

Sending more (and better) data to your ad platforms helps them understand who your ideal customers are, and show your ads to more of them.

Up to 40%

more data captured

13%

lower cost per result

100%

of data sent via browser & server

10 min

to get setup with no developer

Pick the events that matter.

Pick the events that matter.

Pick the events that matter.

Trigger any event to Meta, however you'd like. Button clicks, page loads & more

Trigger any event to Meta, however you’d like. Button clicks, page loads & more

01

Purchase

A completed payment, with value and currency attached.

02

Lead

A visitor raised their hand: a form, a call request, a quote.

03

Schedule

A booking or appointment confirmed.

04

CompleteRegistration

An account created or a sign-up flow finished.

05

StartTrial

A free trial started.

06

InitiateCheckout

Checkout started.

07

AddToCart

A product added to the cart.

08

ViewContent

A product page, or any page you mark as important, viewed.

+ 10 more standard events, including Subscribe, Contact, Search and AddPaymentInfo. Each one fires from whichever trigger you choose.

Connect in minutes.

Connect in minutes.

Connect in minutes.

Login with your Facebook account using One Click connect or add your pixel details manually. Most sites have events flowing in under ten minutes, with no developer involved.

Login with your Facebook account using One Click connect or add your pixel details manually. Most sites have events flowing in under ten minutes, with no developer involved.

1

Add the code snippet

2

Connect your ad platform

3

Choose the events to trigger

4

PixelFlow sends the events browser & server side

Connect your platforms to Meta.

Connect your platforms to Meta.

Connect your platforms to Meta.

One script works on every website builder, store and funnel. Add it once and PixelFlow sends every conversion to Meta from the server.

One script works on every website builder, store and funnel. Add it once and PixelFlow sends every conversion to Meta from the server.

Set it up with your AI agent.

Set it up with your AI agent.

Set it up with your AI agent.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Connect the PixelFlow MCP server to your agent can set up and install everything. Prefer to build your own custom tracking? Just use our infrastructure and build on top of it.

Setup

FAQ

Meta server-side tracking questions, answered

Meta server-side tracking questions, answered

Can’t find the answer you’re looking for? Get in touch and we’ll help you get set up.

It sends your conversion events to Facebook from a server through the Meta Conversions API instead of from the visitor's browser. Because the request never depends on the browser, it is not stopped by ad blockers, iOS privacy settings or a visitor closing the tab before the Pixel fires. Meta recommends running it alongside the Pixel with deduplication, which is exactly what PixelFlow does.

Yes, and you should keep it. Meta's own guidance is to run the Pixel and the Conversions API together, because each one catches events the other misses. PixelFlow fires both and gives them a shared event ID, so Ads Manager counts the conversion once rather than twice.

No. PixelFlow replaces the whole GTM and server container setup. You connect your site, tag events by clicking them on the page, and PixelFlow handles both the Pixel and the Conversions API. There is no dataLayer to design and no container hosting bill.

Event Match Quality is Meta's score, from 1 to 10, for how well each event identifies a real person. It is not a vanity metric: a higher score means Meta can attribute more conversions to your ads and build better lookalikes. It rises when you send more identifiers, which is why server side events with hashed email, click ID and external_id score so much higher than a bare browser pixel.

When the Pixel and the Conversions API both report the same purchase, Meta needs to know it is one conversion. Deduplication solves that: both copies carry the same event ID and Meta keeps one. Done by hand in GTM this is where setups most often break, and duplicate purchases quietly inflate your reported ROAS until someone notices.

Meta standard events, including Lead, Purchase, InitiateCheckout, AddToCart, ViewContent, CompleteRegistration, Subscribe and StartTrial. You choose which standard event each tagged action maps to, so a demo booking can be a Lead and a paid plan can be a Purchase.

Whatever the page can see: email, phone, first and last name, city, region, postcode and country, plus the click ID, browser ID and an anonymous external_id. Everything personal is SHA-256 hashed in the browser before it is sent, so Meta receives the hash and never the raw value.

PixelFlow is consent aware, so events respect your cookie banner, and all personal data is hashed before it leaves the page. A data processing agreement is available. You still need a lawful basis for tracking in the first place, which is your decision rather than ours.

That is one of the biggest sources of lost attribution. PixelFlow receives Stripe purchases, subscriptions and trials by webhook and stitches them back to the original ad click, so an off-site checkout still lands in Ads Manager against the campaign that earned it. Calendly bookings work the same way.

It is the main reason to use it. ATT stops the browser Pixel firing for a large share of iPhone traffic. A server side event does not depend on the browser at all, so it still reaches Meta and is matched on the click ID and hashed customer data you already hold.

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