TikTok Pixel & CAPI Documentation
Server-side CAPI & deduplication
Dual delivery sends each event from both the browser and your server, then relies on a shared event ID for accurate counting.
Steps
-
1
Browser pixel fires
The web pixel extension records the event in the browser and sends a beacon to the app backend.
-
2
Server posts to CAPI
The backend posts the same event to the TikTok Conversion API endpoint, including hashed customer data.
-
3
TikTok deduplicates
Because both hits share one event ID, TikTok merges them and counts the conversion only once.
The server-side path keeps working when the browser pixel is blocked, so conversions are still reported.
Was this article helpful?
Thank you for your feedback!
We're sorry this wasn't helpful. Let us know how we can improve.
Contact Support