Voluum → Facebook CAPI Postback
A postback from Voluum to Facebook CAPI sends confirmed PWA conversions straight from the server, not just through a browser pixel. Here's how to set up the integration in Voluum, map statuses to Facebook events, and confirm one deposit doesn't turn into two events in Events Manager.
The click's path through Voluum to a Facebook event
On an ad click, Facebook attaches fbclid plus the fbp/fbc cookies to the visit, and Voluum stores them in the click data next to its own Click ID. When the affiliate network fires a deposit postback at Voluum's URL, the tracker pulls that click's stored identifiers back out and builds a server-side event for CAPI.
Setting up the Facebook CAPI integration in Voluum
Add Facebook Conversions API under Voluum's integrations: the Pixel ID and a system-user access token from Business Manager's Events Manager, under Conversions API settings. Map the conversion types Voluum receives via postback to Facebook events — a signup typically goes out as Lead or CompleteRegistration, a confirmed deposit as Purchase, with value and currency whenever the offer's postback carries them.
Syncing click ID data with the pixel
For a CAPI event to score a strong match, it needs the same fbclid and fbp the browser pixel saw on that click — so those parameters can't get lost on redirects between the ad, the PWA page and Voluum's domain. Facebook still accepts the event without them, but attribution and conversion optimization both take a real hit.
Deduplication and checking Voluum's logs
If a browser pixel is already live on the PWA page, a deposit can get counted twice — once client-side, once through the Voluum postback. A shared event_id on both calls for the same event fixes it: Facebook keeps a single record. Voluum's conversion log shows whether the postback went out and with what status, which is a fast way to check things before scaling a campaign.
FAQ
- How does setting up Facebook CAPI in Voluum differ from Keitaro or RedTrack?
- The logic is the same — Pixel ID, access token, and status-to-event mapping — only the menu names differ. Voluum additionally shows the postback's delivery status right in the tracker's conversion log.
- Do I still need a browser pixel running on the PWA?
- Yes, pixel plus CAPI together usually gives a fuller, more accurate picture of conversions, and event_id deduplication resolves any overlap between the two channels.
- What's the fastest way to confirm a Voluum postback reached Facebook?
- Check the status in Voluum's conversion log first, then cross-check the events tab in Events Manager — it shows the source, timing, and whether it lines up with the real deposit.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free