Voluum → TikTok Events API Postback
A postback from Voluum to TikTok Events API sends confirmed PWA conversions straight from the server — more reliable than leaning on a browser pixel alone once ad blockers and private modes get involved. Here's how to capture ttclid in Voluum, set up the TikTok integration, and avoid double-counting a conversion when a pixel is also live on the page.
How ttclid ends up in Voluum's click data
TikTok appends a ttclid parameter to the link on an ad click, and Voluum needs to capture it alongside its own Click ID on that first hit. If the PWA page trims parameters on a redirect, or a wrapper domain drops the query string, ttclid never reaches Voluum and there's nothing left to match the conversion to that click.
Setting up TikTok Events API in Voluum
Add TikTok Events API under Voluum's integrations: the Pixel Code from TikTok Ads Manager and an access token from Events → Manage. Map the conversion statuses Voluum receives via postback to TikTok events — a signup usually goes out as CompleteRegistration, a confirmed deposit as Purchase, with value and currency when they're available.
Attribution quality: ttclid and the ttp cookie
An Events API call scores better when it carries the same ttclid the pixel saw on that click, plus the ttp cookie if the browser had time to set it. Without ttclid, TikTok sometimes still accepts the event on indirect signals, but attribution accuracy and campaign optimization both drop noticeably.
Deduplication and testing before launch
If a TikTok pixel is already running on the PWA page, a conversion can get counted twice — once client-side, once through the Voluum postback. A shared event_id on both calls for the same event fixes that: TikTok merges them into one record. Before spending real budget, push a test conversion through and check it in TikTok Events Manager's Test Events tool, and check the postback's delivery status in Voluum's log too.
FAQ
- What if some of the traffic isn't from TikTok Ads but organic?
- Without ttclid an event is harder to tie to a specific click, so attribution accuracy drops for organic traffic — but the event can still be sent, just missing some of the matching parameters.
- Can the same event_id be used for one user's signup and deposit?
- No, each distinct event needs its own unique event_id, or TikTok will treat the second event as a duplicate of the first and won't count it separately.
- Where can I check whether a Voluum postback reached TikTok, and with what result?
- Voluum's conversion log shows the postback's send status, and TikTok Events Manager's events tab shows whether it was accepted and with which parameters.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free