TikTok Conversions API

the tiktok conversions api destination sends event data directly from chord cdp to tiktok's servers, bypassing the browser entirely unlike the tiktok pixel (device mode) , server side events are immune to ad blockers and browser tracking restrictions, providing more reliable signal for attribution and optimization use this destination alongside the tiktok pixel destination for maximum data coverage tiktok deduplicates events using the event id field getting started this is a cloud mode destination you will need access token — generated via tiktok ads manager or the tiktok api found in assets > events > web events > settings pixel code — your tiktok pixel id, found in your tiktok ads manager under assets > events > web events optionally test event code — a test event code from the tiktok ads events manager when set, events are tagged for test mode and will appear in the tiktok test events dashboard connecting to the tiktok conversions api cdp destination warning before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream log into the chord data platform navigate to the cdp click the "add" button next to destinations select tiktok conversions api from the destination catalog enter the destination name, access token , and pixel code optionally enter a test event code during initial setup click "create" to connect events event mapping chord event tiktok event page pageview order completed completepayment checkout started initiatecheckout product added addtocart product viewed viewcontent products searched search payment info entered addpaymentinfo product added to wishlist addtowishlist product clicked clickbutton signed up completeregistration subscription created subscribe (any other track event) chord event name passed as is see custom events user data (all events) all user data fields are sha 256 hashed before sending, except where noted tiktok attribute chord source (priority order) notes external id userid > anonymousid sha 256 hashed email properties email > context traits email sha 256 hashed, lowercased phone properties phone > context traits phone sha 256 hashed, e 164 format first name properties first name > context traits first name sha 256 hashed last name properties last name > context traits last name sha 256 hashed city properties address city > context traits address city lowercased, non alphanumeric chars removed (not hashed) state properties address state > context traits address state lowercased, non alphanumeric chars removed (not hashed) country properties address country > context traits address country lowercased, non alphanumeric chars removed (not hashed) zip code properties address postal code / properties address zip code > context traits address zipcode sha 256 hashed ip context ip not hashed user agent context useragent not hashed locale context locale not hashed ttclid properties ttclid > url query param ttclid tiktok click id ttp properties ttp tiktok cookie page data (all events) tiktok attribute chord source (priority order) url properties url > context page url referrer properties referrer > context page referrer event data (all events) tiktok attribute chord source notes event mapped event name see event mapping above event time timestamp unix seconds; falls back to current time event id messageid used for deduplication with device mode pixel limited data use event limited data use (top level event field) defaults to false order properties (all track events) tiktok attribute chord source (priority order) notes currency properties currency value properties value > properties revenue > calculated from contents ( price × quantity ) order id properties order id shop id properties shop id content type properties content type "product" or "product group" description properties description query properties query > properties search term relevant for products searched multi product events for order completed , checkout started , and payment info entered , products are read from properties products\[] tiktok attribute chord source content id properties products\[] product id content name properties products\[] name content category properties products\[] category price properties products\[] price quantity properties products\[] quantity brand properties products\[] brand single product events for product added , product viewed , product clicked , products searched , and product added to wishlist , product data is read from top level properties tiktok attribute chord source content id properties product id content name properties name content category properties category price properties price quantity properties quantity brand properties brand custom events any track event that does not match a chord tracking plan event name is forwarded to tiktok using the chord event name as is tiktok accepts arbitrary event names for reporting and audience segmentation, though only tiktok standard event names support campaign bid optimization the following non tracking plan events have explicit tiktok standard event name mappings and will be translated automatically if your storefront fires them chord event tiktok event notes form submitted submitform sends form name from properties form name > properties name callback started contact download link clicked download if the tiktok event name you want to fire does not match your chord event name, use a property mapping in the hub to rename the event before it reaches this destination testing and validation after connecting the destination set a test event code in the destination configuration trigger events from your storefront or use the live events tab in the chord cdp in tiktok ads manager, navigate to assets > events > web events and open the test events tab to verify events are received remove the test event code before going live to avoid events being excluded from campaigns custom property forwarding configure destination mappings in hub with properties destination paths to forward additional event properties into the tiktok event's properties object (the same object that holds currency , value , contents , etc ) only explicitly configured non schema fields are forwarded — nothing flows through automatically how to configure open the destination's mappings tab in hub add a mapping with source path properties loyalty tier and destination path properties loyalty tier on the next event, loyalty tier will appear in the properties payload sent to tiktok what is excluded schema fields already handled by the destination transform (e g currency , value , order id , contents ) — these flow through the structured transform pii fields ( email , phone , first name , last name ) — these are handled via user data with sha 256 hashing when a custom mapping targets a schema field (e g properties value → properties value ), the customer configured value overrides the destination's computed default this allows schema fields to be sourced from a different event property — for example, mapping properties total → properties value to use your order total as the conversion value updated 27 may 2026