RedTrack → TikTok Events API Postback
A postback from RedTrack to TikTok Events API sends PWA conversions straight from the server, sidestepping the limits browser pixels run into after iOS updates and ad blockers. Here's how to tie ttclid to the RedTrack click, map statuses to TikTok events, and avoid double-counted conversions when a pixel is already running.
ttclid: how TikTok identifies the click
When a user clicks a TikTok ad, TikTok appends a ttclid parameter to the link — that's the click identifier a later conversion gets matched against. RedTrack needs to capture and store that ttclid alongside its own click ID on the very first hit, so the PWA page can't afford to drop the parameter on a redirect or trim the query string when it lands on the APEX domain.
Setting up TikTok Events API in RedTrack
Add TikTok Events API under RedTrack's integrations: the Pixel Code from TikTok Ads Manager and an access token from Events → Manage. Map RedTrack's conversion statuses to TikTok's standard events — a signup usually goes out as CompleteRegistration, a confirmed deposit or purchase as Purchase, with value and currency whenever the postback carries them.
ttclid matching and attribution quality
An Events API call scores better when it carries the same ttclid the browser pixel saw on that click, plus the ttp cookie if it had time to set. Without ttclid, TikTok sometimes still accepts the event on indirect signals, but attribution and conversion-based optimization both take a real hit.
Deduplication and testing with Test Events
If a TikTok pixel is already live on the PWA page, a conversion can double up — once client-side, once through the RedTrack postback. The fix mirrors Meta's: a shared event_id on both calls for the same event, and TikTok merges them into one record. Before spending real budget, push a test event through and check TikTok Events Manager's Test Events tool to confirm it arrives once, with the right parameters.
FAQ
- Is ttclid mandatory if traffic doesn't come directly from TikTok Ads?
- Without it, an event is much harder to match to a specific click, so for paid TikTok Ads traffic it's effectively required — skip it and attribution and optimization both suffer.
- Can the same event_id be reused across different funnel steps?
- No — event_id has to be unique per event. A signup and a deposit need separate IDs, or TikTok will treat the second event as a duplicate of the first.
- How do I confirm the integration works before spending real budget?
- Push a handful of test conversions through RedTrack and check them in TikTok Events Manager's Test Events tool — it shows whether the event arrived, with what parameters, and whether it doubled up.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free