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#

  1. Open Dashboard → Campaigns → <campaign> → Settings.
  2. Pick TikTok as the source.
  3. Paste the Pixel ID, Events API access token, and optionally a Test Event Code.
  4. 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.

Credentials verified: Zellify fires a test event on save. Confirm it appears in Test events.

Events sent to TikTok#

Funnel eventTikTok event nameTypeValue?Sent via
Page viewPageViewStandardPixel & Events API
LeadLeadCustomPixel & Events API
Page completedPageCompletedCustomPixel & Events API
Email capturedCompleteRegistrationStandardPixel & Events API
Checkout presentedInitiateCheckoutStandardYesPixel & Events API
Payment method addedAddPaymentInfoStandardYesPixel & Events API
Payment succeededCompletePaymentStandardYesPixel & Events API
Payment failedPaymentFailedCustomYesPixel & Events API
Trial startedStartTrialStandardNo (value: 0)Pixel & Events API
Subscription startedSubscribeStandardNo (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 with content_id, content_name, quantity, price
  • content_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 id
  • email — SHA-256 hashed once captured
  • ttp — TikTok browser cookie, auto-set by the Pixel
  • ttclid — TikTok click id from the ad URL
  • ip — visitor's IP address
  • user_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#

  1. Open Events Manager → Test event → set your Test Event Code.
  2. Walk through a test funnel to purchase.
  3. 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#

SymptomLikely causeFix
CompletePayment missingttclid not forwardedConfirm campaign links include TikTok's ttclid query param
Low match rateEmail not captured before paywallAdd a Registration step before the paywall
Events rejected with 401Wrong Events API access tokenRegenerate in TikTok Events Manager
Campaigns
Where TikTok is configured.
Event reference
Canonical event taxonomy.
Meta integration
Same shape, Meta equivalents.