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
Apointoo 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.
What it sends to Google Ads
How the data flows
- Ad click carries ttclid
- Apointoo Capture stores the identifier
- Your CRM or checkout confirms the outcome
- Apointoo posts the server event
- event_id deduplicates against the TikTok Pixel
How the connection works
Capture stores ttclid from TikTok landing URLs.
Your CRM or checkout confirms qualified leads and purchases.
Apointoo posts server events with stable event ids.
Deduplication against the Pixel happens at TikTok, count stays honest.
Attribution identifiers
Event mapping
| From | Apointoo |
|---|---|
| Lead captured from TikTok traffic | lead server event |
| Qualified stage reached | custom qualified event |
| Purchase confirmed | CompletePayment server event (value + currency) |
Frequently asked questions
The outcome reaches the platform that actually has your audience.