Custom stack to TikTok Events API
Forward every Custom stack event to TikTok Events API server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Custom stack to TikTok Events API with Upstack Data
Custom stack
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
Custom stack integrationTikTok Events API
Forward resolved conversions to the TikTok Events API so the algorithm optimises on customers, not sessions.
TikTok Events API integrationWhat changes
What changes when Custom stack feeds TikTok Events API.
Server-side delivery
Events reach TikTok through its server API, not the browser — so ad blockers, ITP and consent banners don’t cost you conversions.
Identity-resolved events
Every event sent to TikTok carries a resolved customer, matched against a 750M+ device graph.
Any stack, any framework
Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.
The same event schema
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
What actually moves
What Custom stack carries, and what TikTok Events API needs.
Custom stack and TikTok Events API describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what TikTok Events API can actually use.
Custom stack sends
- event_name
- whatever you choose to call it
- user identifiers
- any of email, phone, external ID
- value / currency
- if the event carries revenue
- custom properties
- any attribute in your own schema
TikTok Events API receives
- email / phone (hashed)
- Events API matching
- ttclid / ttp
- attribute the click
- event_id
- browser and server dedupe
- value / currency
- optimise on revenue
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in TikTok Events API
TikTok Events ManagerTest Events, then the event's match rate once live traffic is flowing.
Related connectors
Other places Custom stack can send to.
- Custom stackMeta Conversions API
- Custom stackGoogle Ads Conversions
- Custom stackPinterest
- Custom stackSnapchat
- Custom stackReddit
- Custom stackMicrosoft Ads
- Custom stackX
- Custom stackAppLovin
Other sources that feed TikTok Events API.
- ShopifyTikTok Events API
- WooCommerceTikTok Events API
- BigCommerceTikTok Events API
- Checkout ChampTikTok Events API
- RechargeTikTok Events API
- FunnelishTikTok Events API
- Lasso CommerceTikTok Events API
- Phoenix TechnologiesTikTok Events API
- SkioTikTok Events API
- Loop SubscriptionsTikTok Events API
- StripeTikTok Events API
- Everything TikTok Events API can take12 sources feed TikTok Events API, and the setup is the same for each one.TikTok Events API integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Custom stack talking to TikTok Events API.
A 15-minute walkthrough of this connector on your own account.