Postback Binom → TikTok Events API
A Binom to TikTok Events API postback sends conversions from your PWA offer straight from the tracker's server into the TikTok ad account, bypassing the limits of a browser pixel. Server-side delivery through the Events API is more reliable and matters most for delayed events — a deposit that happens some time after the PWA install, for instance. Here's how to set up the flow in Binom, map statuses, and deduplicate so nothing gets double-counted.
Why the TikTok Events API matters for PWA traffic
The browser-side TikTok pixel only sees what happens in the user's current session and loses events to ad blockers or a tab closing before the script fires. The Events API sends data straight from the server, so the event lands regardless of what the user's browser does — that matters especially for PWA, where the key conversion (a deposit, a purchase) often happens well after install, not at the moment of it. The more reliably those delayed events land, the better TikTok can optimize delivery toward real outcomes instead of just clicks.
Prep: ttclid, Pixel Code, Access Token
Capture ttclid — TikTok's click ID — from the URL parameter when the user lands on the PWA; it's the only way to match a future server-side conversion back to a specific ad impression. Grab the Pixel Code from TikTok Events Manager, and generate an Access Token separately in the pixel's settings specifically for Events API access. Both values go into the outgoing postback configuration in Binom.
Setting up the postback in Binom and mapping statuses
In Binom, create an outgoing postback pointed at the TikTok Events API endpoint, substituting macros for {clickid} (the stored ttclid), the conversion status, and the value. Map each Binom status to a specific TikTok event — separate events for a lead versus a deposit, say, rather than one generic event for everything, or TikTok ends up optimizing the campaign on a mixed, lower-value signal. APEX supports S2S postbacks with Binom out of the box: status mapping and macro substitution are configured in the interface, no server-side proxy script required.
Deduplication and verifying delivery
When the browser pixel and the server-side Events API run in parallel, the same event can get counted twice — the fix is a single event_id generated by the tracker and passed to both channels. TikTok matches events sharing the same event_id and counts them as one conversion. Verify postbacks are arriving and not doubling up through test events in TikTok Events Manager, which shows the delivery status of each event.
FAQ
- How do you confirm a postback from Binom is actually reaching TikTok?
- TikTok Events Manager has a test events section that shows whether an event arrived from the server, with what status, and whether there's an Access Token authorization error. Binom's logs show TikTok's response code for every request sent, alongside that.
- What happens if event_id deduplication isn't set up?
- The same event, sent by both the pixel and the Events API, gets counted by TikTok as two separate conversions — that inflates reporting and throws off the algorithm's optimization against real cost per result.
- Do leads and deposits need separate events?
- Yes, mapping them to different TikTok events is better practice — it lets the campaign optimize toward the specific funnel stage you actually care about instead of blending signals of very different value into one.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free