Integrations / Advertising
TikTok
Server-side event tracking for TikTok.
Datafly Signal delivers first-party events to TikTok server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TikTok expects.
Why route TikTok through Datafly Signal
Conversions survive ad blockers and tracking prevention
A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions TikTok optimises against are not filtered by the browser.
Phone number and email hashed before it leaves your infrastructure
Signal normalises (trim and lowercase) and applies SHA-256 inside your own deployment, so TikTok receives match keys rather than raw personal data.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what TikTok needs to attribute the event to the right session.
Click identifiers are captured and replayed
Signal stores ttclid first-party at collection time and attaches them to the conversion later, so attribution survives even when the original landing cookie has expired.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the TikTok rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
TikTok is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_payment_infoadd_to_cartadd_to_wishlistbegin_checkoutbooking_completedbooking_startedbrochure_downloadedcontent_vieweddealer_contacteddestination_searchedfinance_quote_requestedgenerate_leadlisting_savedlisting_viewedpagepurchasesearchservice_appointment_bookedsign_upsubscription_startedtest_drive_bookedtrade_in_valuedvehicle_comparedvehicle_savedvehicle_searchedvehicle_viewedview_itemVertical presets
Retail, Travel, Automotive, Media. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the TikTok documentation.
Frequently asked questions
Does Datafly Signal integrate with TikTok?
Yes. Datafly Signal delivers first-party events to TikTok server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload TikTok expects. The integration is included in every deployment at no additional cost.
How is server-side TikTok tracking different from the TikTok tag?
The TikTok tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to TikTok from your server, so delivery does not depend on browser conditions.
What personal data is sent to TikTok?
Phone number and email are normalised and SHA-256 hashed inside your own deployment before delivery, so TikTok receives match keys rather than raw personal data. Which fields are sent is configured per pipeline.
Which events can Signal send to TikTok?
The blueprint ships with mappings for add_payment_info, add_to_cart, add_to_wishlist, begin_checkout, booking_completed, booking_started, brochure_downloaded, content_viewed, and more. Any event in your schema can be mapped to TikTok through pipeline configuration without a code change.
Do I need to keep the TikTok tag on my site?
No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so TikTok deduplicates, then remove the tag once server-side volume matches.
Other advertising integrations
Ready to move TikTok server-side?
See how Datafly Signal delivers first-party events to TikTok from infrastructure you control, with hashed identity and consent enforcement built in.