Server-side tracking

Meta Conversions API, done for you

Trakt sends your purchases and leads to Meta server-side, with the fbc and fbp identifiers and a hashed match set, deduplicated against your existing pixel. No developer, no double-counting.

Why the Meta pixel alone is not enough

Browser-based pixel events are blocked by ad blockers, capped by Safari and Firefox, and lost when a page fails to load. Meta built the Conversions API so the sale can be reported from your server instead, where none of that reaches it. On its own it is a developer project; Trakt runs it for you.

  • Purchases and leads sent from our servers, not the shopper browser
  • fbc and fbp captured first-party so events match the pixel
  • Customer match data hashed before it ever leaves your side
  • Deduplicated on event id, so the pixel and CAPI never count the same sale twice

How it works

Matched to the exact click, sent on the right delay

Captured first-party

Trakt records the click and the Meta identifiers on your own domain when the visitor lands, so the conversion can be matched back to the real ad interaction later.

Joined server-side

The order arrives from Shopify or WooCommerce with authoritative revenue, and Trakt attaches it to the browsing session that earned it before sending.

Deduplicated

Each conversion carries the same event id your pixel uses, so Meta collapses the two into one. Turning on CAPI does not inflate your numbers.

Verify in shadow mode

Trakt builds the exact CAPI payload and logs it without sending, so you can check every field before a single event reaches Meta.

Turn on the Meta Conversions API in shadow mode first.

See the exact events Trakt would send to Meta, and verify the match rate, before anything goes live.

Start free Sign in