TikTok (Pixel and Events API)
For anyone running TikTok ads into a Zellify funnel. You'll have Pixel and Events API events in TikTok Events Manager, deduplicated and attributed. You need a TikTok Pixel ID, Events API access token, and a Zellify campaign.
What this integration does#
On a campaign with TikTok as the source, Zellify fires the TikTok Pixel from the browser and sends the Events API event from the server. Events are linked by event_id for deduplication and carry ttp and ttclid for attribution.
Connect TikTok#
- Open Dashboard → Campaigns → <campaign> → Settings.
- Pick TikTok as the source.
- Paste the Pixel ID, Events API access token, and optionally a Test Event Code.
- Save.
Where to find your credentials#
-
Pixel ID: TikTok Events Manager → Web Events → <your pixel>.
-
Events API access token: same pixel → Settings → Events API → Generate access token.
-
Test Event Code: Events Manager → Test event → Copy code.
Events sent to TikTok#
| Funnel event | TikTok event name | Type | Value? | Sent via |
|---|---|---|---|---|
| Page view | PageView | Standard | — | Pixel & Events API |
| Lead | Lead | Custom | — | Pixel & Events API |
| Page completed | PageCompleted | Custom | — | Pixel & Events API |
| Email captured | CompleteRegistration | Standard | — | Pixel & Events API |
| Checkout presented | InitiateCheckout | Standard | Yes | Pixel & Events API |
| Payment method added | AddPaymentInfo | Standard | Yes | Pixel & Events API |
| Payment succeeded | CompletePayment | Standard | Yes | Pixel & Events API |
| Payment failed | PaymentFailed | Custom | Yes | Pixel & Events API |
| Trial started | StartTrial | Standard | No (value: 0) | Pixel & Events API |
| Subscription started | Subscribe | Standard | No (value: 0) | Pixel & Events API |
See Event reference for the canonical taxonomy.
CompletePayment payload#
The payment success event includes:
value— total purchase amount (decimal, e.g.9.99)currency— currency code (e.g.USD)contents— array withcontent_id,content_name,quantity,pricecontent_type— always"product"num_items— item count
Server-side user data (Events API)#
When an Events API access token is configured, the server event carries:
external_id— SHA-256 hashed session idemail— SHA-256 hashed once capturedttp— TikTok browser cookie, auto-set by the Pixelttclid— TikTok click id from the ad URLip— visitor's IP addressuser_agent— browser user agent
TikTok attribution identifiers#
Zellify forwards ttp (TikTok Pixel cookie id) and ttclid (click id) from the ad redirect to the server event. These are what TikTok uses to credit the click.
Event deduplication#
Pixel and Events API events share the same event_id. TikTok counts them as one. The optional Test Event Code is server-side only — it lets you isolate test traffic in the TikTok Events Manager Test Events panel without affecting the browser Pixel.
Test and verify#
- Open Events Manager → Test event → set your Test Event Code.
- Walk through a test funnel to purchase.
- Confirm events appear in Test event within 60 seconds.
:::tip Use the Test Event Code before going live. It isolates test traffic. :::
Going live#
Remove the Test Event Code. Confirm events land in the main TikTok Events view.
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
| CompletePayment missing | ttclid not forwarded | Confirm campaign links include TikTok's ttclid query param |
| Low match rate | Email not captured before paywall | Add a Registration step before the paywall |
| Events rejected with 401 | Wrong Events API access token | Regenerate in TikTok Events Manager |