Postback Binom → Facebook CAPI
A Binom to Facebook CAPI postback sends conversions from your PWA offer straight from the server to the Facebook ad account, sidestepping the browser limits and blockers that dent a standard pixel's accuracy. The Conversions API (CAPI) is Facebook's server-side channel, meant to run alongside the pixel, and it needs careful deduplication or the same event gets counted twice. Here's the full setup, from click ID capture to verification in Events Manager.
Why CAPI matters even with a pixel already on the page
The browser-side Facebook pixel loses events to ad blockers, Safari's privacy limits, and tightening mobile browser privacy rules — buyers commonly see meaningfully lower event counts on some geos as a result. CAPI sends the same event straight from the tracker's server, bypassing the browser, giving Facebook a fuller picture to optimize delivery toward conversions. For PWA offers where the deposit happens some time after install rather than immediately, CAPI matters even more — those later events are exactly what the pixel tends to miss.
Prep: click ID, Pixel ID and Access Token
Attribution needs fbclid — Facebook's click parameter, which the tracker (Binom) has to capture from the URL on the user's first visit to the PWA and store alongside the click data. In Facebook Events Manager, grab the Pixel ID of the existing pixel, and generate an Access Token separately — either through the CAPI settings in Events Manager or via a system user in Business Manager for a more secure integration. Both values are needed on the Binom side to configure the outgoing postback.
Setting up the postback in Binom
In Binom, an external tracking postback is configured under the campaign or offer settings: point it at the Facebook Graph API endpoint for CAPI events, and pass macros for {clickid}, a conversion status mapped to the right Facebook event (Purchase for a deposit, for example), and the value. Map Binom's statuses (lead, sale, etc.) explicitly to specific Facebook events rather than firing the same event for everything — otherwise Facebook's algorithm optimizes toward the wrong signal. APEX ships a ready S2S postback setup, including Keitaro and Binom to Facebook CAPI, so status mapping is a one-time configuration in the interface, no server-side proxy script needed.
Deduplication via event_id
If the pixel and CAPI both fire the same event independently, Facebook counts it twice — that skews reporting and throws off cost-per-conversion optimization. The fix is a single event_id generated on the tracker side, passed to both the pixel and the CAPI request for the same event — Facebook deduplicates automatically on that identifier within a window of a few minutes. After setup, verify the flow under Test Events in Facebook Events Manager — it shows whether the event is arriving from both the browser and the server, and whether it's being double-counted.
FAQ
- What if conversions from Binom aren't reaching Facebook CAPI?
- Check that fbclid is actually being captured by the tracker and isn't arriving empty, that the Access Token hasn't expired and is tied to the right Pixel ID, and check Facebook's response code in Binom's logs — it usually points straight at the rejection reason.
- What's the right way to deduplicate conversions between the pixel and CAPI?
- Generate a single event_id on the tracker side for each event and pass it to both the pixel and the CAPI request at the same time — Facebook matches the two signals as one event within its deduplication window.
- Should you keep the browser pixel once CAPI is set up?
- Yes, they're designed to work together — the pixel covers the upper funnel well in-browser, while CAPI recovers what it misses, especially later events like a deposit.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free