TikTok Ads (Events API)
The outcome reaches the platform that actually has your audience.
TikTok campaigns optimize toward Pixel events. This connection adds the server side: confirmed leads and purchases posted through the Events API with ttclid attached and event_id deduplication against the browser.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
Browser-only events undercount mobile journeys
TikTok lives on the app; the purchase happens later, on another surface or after install delays ate the cookie. The Pixel reports what survived. Bidding learns from fragments.
Server events with stable ids
Apointo preserves ttclid from the landing click, joins it to CRM and checkout outcomes, and posts CompletePayment and lead events with value. The Pixel keeps reporting; deduplication keeps counts honest.
- 01Ad click carries ttclid
- 02Apointo Capture stores the identifier
- 03Your CRM or checkout confirms the outcome
- 04Apointo posts the server event
- 05event_id deduplicates against the TikTok Pixel
Capture stores ttclid from TikTok landing URLs.
Your CRM or checkout confirms qualified leads and purchases.
Apointo posts server events with stable event ids.
Deduplication against the Pixel happens at TikTok, count stays honest.
| From | Apointo |
|---|---|
| Lead captured from TikTok traffic | lead server event |
| Qualified stage reached | custom qualified event |
| Purchase confirmed | CompletePayment server event (value + currency) |
What is ttclid?
The TikTok click identifier carried by ad landing URLs. It lets the Events API join a later outcome to the original paid click without third-party cookies.
Will server events double count with the Pixel?
No. Matching event ids let TikTok recognize both signals as one event.
When does this connector ship?
This page is the working specification. Join the early-access list and build order follows demand.