Lasso Commerce to TikTok Events API
Forward every Lasso Commerce 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 Lasso Commerce to TikTok Events API with Upstack Data
Lasso Commerce
Capture Lasso Commerce checkouts and upsells server-side, so orders that never touch a storefront page are still resolved and forwarded.
Lasso Commerce 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 Lasso Commerce 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.
Every event, server-side
Storefront and checkout events are captured from Lasso Commerce on the server, independent of the browser.
One setup, every destination
Connect Lasso Commerce once and forward to every ad platform, email tool and warehouse you run.
What actually moves
What Lasso Commerce carries, and what TikTok Events API needs.
Lasso Commerce 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 Lasso Commerce can put on an event, the right is what TikTok Events API can actually use.
Lasso Commerce sends
- order_id
- Lasso checkout order reference
- email / phone
- contact captured at checkout
- line_items
- products and quantities on the order
- total / discount
- order economics after adjustments
- landing_domain
- the site the shopper started on, before the checkout hop
- customer_type
- new or returning, resolved before send
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 Lasso Commerce can send to.
- Lasso CommerceMeta Conversions API
- Lasso CommerceGoogle Ads Conversions
- Lasso CommercePinterest
- Lasso CommerceSnapchat
- Lasso CommerceReddit
- Lasso CommerceMicrosoft Ads
- Lasso CommerceX
- Lasso CommerceAppLovin
Other sources that feed TikTok Events API.
- ShopifyTikTok Events API
- WooCommerceTikTok Events API
- BigCommerceTikTok Events API
- Checkout ChampTikTok Events API
- RechargeTikTok Events API
- Custom stackTikTok Events API
- FunnelishTikTok 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 Lasso Commerce talking to TikTok Events API.
A 15-minute walkthrough of this connector on your own account.