TikTok Events API
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Ad platform (conversions) | One click: approve bubbl3 on TikTok Events API's own page |
TikTok Events API isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.
What it does
When a lead qualifies, books or buys, bubbl3 can tell TikTok. Each conversion event you choose is sent to a TikTok event set with:
- the event name you map, its time and value;
- TikTok's lead id, for a CRM event set (contacts from TikTok lead forms carry it);
- the contact's email and phone, hashed with SHA-256 before they leave bubbl3.
Setup
You need full access to integrations in bubbl3, and to manage the TikTok ad account.
- In bubbl3, open Settings, Integrations, choose TikTok Events API, then Connect, and authorize bubbl3 for your ad accounts on TikTok's page.
- In Settings, Events, open an event and add a destination: this connection, the event set id, whether it's a CRM or offline set, and TikTok's event name.
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: deliveries to TikTok. Deliveries still waiting are not sent.
- Deleted at once: bubbl3's TikTok access token (TikTok is asked to revoke it).
- Kept: your conversion events and their delivery log in bubbl3.
Data shared
From bubbl3 to TikTok: for each conversion: the event set, event name, time, value, currency, an event id TikTok uses to drop duplicates, TikTok's lead id for CRM sets, and SHA-256 hashes of the email and phone. Never the raw email or phone, and never anyone who opted out or has no consent record.
From TikTok to bubbl3: the ad accounts you authorized and TikTok's answer to each delivery.
Scopes and permissions
| Permission | Why bubbl3 needs it |
|---|---|
report_conversion_event | Send conversion events to your event sets |
Events
What bubbl3 receives
Nothing: TikTok only receives conversions from bubbl3.
What bubbl3 writes back
| What | Where it shows in TikTok |
|---|---|
| Conversions | An event in the event set you chose, in Events Manager |
Sending rules that still apply
TikTok Events API never causes a text. bubbl3 sends it conversion events only for contacts who haven't opted out and have a consent record, and stops for a contact who opts out later. Emails and phone numbers are hashed with SHA-256 before they leave bubbl3.
Limits and known gaps
- A CRM event set needs TikTok's lead id: contacts without one are skipped (the delivery log says why). An offline event set matches on email and phone instead.
- TikTok's access token doesn't expire, but if it's refused you need to reconnect.
Troubleshooting
- Deliveries are skipped with "no match keys". The contact has no TikTok lead id and the destination is a CRM event set. Use an offline set for contacts from other sources.
- The connection needs attention. TikTok refused the token; reconnect.