RedTrack → Facebook CAPI Postback
A postback from RedTrack to Facebook CAPI makes sure every deposit from an offer reaches your ad account exactly once — no drops, no doubles. Here's how to wire up the S2S integration: which click ID to forward, how to map conversion statuses to Facebook events, and how to confirm deduplication before you scale spend on it.
The data path from click to Facebook event
A user clicks the ad, Facebook attaches fbclid plus the fbp/fbc cookies to that visit, and RedTrack stores them next to its own click ID for the same click. When the affiliate network later fires a deposit postback at RedTrack's URL, RedTrack pulls those stored identifiers back out and builds a server-side event for CAPI. That's how Facebook knows exactly which click drove the conversion, even if the deposit lands hours after the click.
Setting up the Facebook CAPI integration in RedTrack
RedTrack ships a ready-made Facebook CAPI connector under its integrations: add the Pixel ID and an access token — a system-user token from Business Manager's Events Manager, under Conversions API settings. From there, map RedTrack's conversion statuses to Facebook events: a signup typically goes out as CompleteRegistration or Lead, a confirmed deposit as Purchase, passing value and currency whenever the postback carries them.
Click ID and pixel match quality
For a CAPI event to score a strong Event Match Quality, it needs the same identifiers the browser pixel saw on that click — which is why fbclid and fbp have to survive the whole PWA-to-RedTrack chain without getting dropped on a redirect. Facebook still accepts the event without them, but attribution and conversion optimization take a real hit.
Deduplication: one deposit, one counted event
If a browser pixel is already live on the PWA page, the same deposit can reach Facebook twice — once client-side, once through the RedTrack postback. The fix is a shared event_id, identical on both calls for the same real event: Facebook keeps one record and flags the other as a duplicate. Before scaling, run a few test conversions and confirm in Events Manager that nothing's doubling up.
FAQ
- Do I still need a browser pixel on the PWA if the RedTrack postback is live?
- Yes — pixel plus CAPI together usually outperforms either channel alone, and any overlap between them gets resolved by event_id deduplication.
- How do I confirm a RedTrack postback actually reached Facebook?
- Check the events tab in Events Manager: it shows the source (Browser or Server), the receipt status, and whether the timing lines up with the real deposit.
- What if Facebook reports a low Event Match Quality score?
- Check that fbclid and fbp are actually reaching RedTrack without getting stripped on a PWA redirect, and pass along extra match parameters where you have them, like country or device type.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free