Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Data direction: This is a destination — Upstack sends event and conversion data out to this platform via server-side APIs.

​
What it does

TikTok’s Events API is the server-side counterpart to the TikTok Pixel. Upstack Signal forwards storefront events — page views, product views, add-to-carts, checkouts, and purchases — directly to TikTok’s servers, bypassing browser restrictions like ad blockers, ITP, and cookie limits. Server-side delivery gives TikTok’s algorithm a fuller picture of the conversions your ads actually drove, which improves campaign optimization, audience modeling, and attribution accuracy. Match rates from server-side events are consistently higher than browser-only tracking because each event carries hashed customer data and the ttclid click identifier when available.
Unlike Meta and Google Ads, TikTok uses token-based auth instead of OAuth. You’ll paste a Pixel ID and an Events API access token into the Upstack destination — there is no OAuth handshake to step through.

​
How it works

Upstack runs as a dual-tracking layer alongside the TikTok Pixel. The Upstack Pixel captures events in the browser and forwards each event to Upstack’s edge infrastructure, where it is hashed, enriched with identity and click-ID data, and sent to the TikTok Events API as a server-side event with a shared event_id. TikTok deduplicates server events against matching browser Pixel events using that event_id, so you do not double-count conversions as long as both sources use the same Pixel ID. PII (email, phone, external_id) is hashed with SHA-256 before delivery, as required by the Events API.

​
Setup guides

Onboarding guide

End-to-end walkthrough for connecting TikTok to Upstack Data.

Configure pixel destination

Configure the TikTok Pixel destination inside Upstack Data.

Find Pixel ID

Locate your existing TikTok Pixel ID in Events Manager.

Create Pixel ID

Create a new TikTok Pixel for your store.

Generate API token

Generate the Events API access token Upstack uses to send events.

Disable Shopify TikTok data sharing

Turn off Shopify’s native TikTok integration to prevent duplicate events.

​
Event mapping

Upstack maps storefront events to TikTok standard events automatically:
Upstack eventTikTok eventKey parametersNotes
PageViewViewContenturl, referrerTikTok has no generic PageView — mapped to ViewContent
ViewContentViewContentcontent_id, content_type, value, currencyProduct page views
AddToCartAddToCartcontent_id, content_type, value, currencyCart additions with product details
InitiateCheckoutInitiateCheckoutvalue, currency, quantityCheckout started
PurchaseCompletePaymentcontent_id, value, currency, order_idCompleted orders with revenue
Every event includes user data parameters (email, phone, external_id) when available, hashed with SHA-256. TikTok click IDs (ttclid) captured by the Upstack Pixel are included for deterministic matching.

​
FAQ

Open TikTok Events Manager, select your Pixel, and check the Overview and Test Events tabs. Server-side events appear with a “Server” source badge, typically within 5–10 minutes of storefront activity. Upstack also surfaces delivery status inside the destination settings.
No — as long as the Pixel ID in Upstack matches the Pixel ID firing in your storefront’s TikTok browser Pixel (ttq.load). Upstack sends a shared event_id on every server-side event, and TikTok’s deduplication logic matches events by event_id and keeps only one. If you see duplicates, the Pixel IDs almost always differ between the two sources.
TikTok’s match rate depends on how much identity data each event carries. Common causes of low match quality:
  • Missing ttclid — TikTok ads should link directly to your storefront so the click ID lands in the URL and is captured by the Upstack Pixel.
  • Anonymous visitors — events from visitors without email or phone have fewer keys to match against. Match rates improve as more identified customers convert.
  • Missing checkout fields — make sure your Shopify checkout collects email and phone; both are strong server-side match keys.
Yes — if Shopify is also sending events to the same TikTok Pixel, you’ll see duplicates that TikTok cannot deduplicate (Shopify does not emit a matching event_id). Follow the guide above to disable TikTok data sharing in Shopify before activating Upstack’s TikTok destination.
Yes. Each destination supports event filtering — you can choose to forward only purchases, only standard events, or any custom subset. Excluded events are dropped at the Upstack level and are not retried.

​
Advanced configuration

If you sell through TikTok Shop, those orders flow into Shopify as fulfilled orders. Upstack processes them like any other Shopify order, which means they get sent to all your active destinations — including Meta.Should you exclude TikTok Shop orders from other destinations?Upstack gives you the option via Settings → Order Source Exclusions, where you can block orders by source. However, sending TikTok Shop orders to Meta is generally beneficial — more conversion data helps Meta’s algorithm find similar high-value customers, regardless of where the original purchase happened.If you still want to exclude them:
  1. Go to Upstack → Settings → Order Source Exclusions.
  2. Add TikTok Shop as a blocked source.
  3. Orders originating from TikTok Shop will no longer fire to other destinations.

​
Troubleshooting

If events aren’t appearing after 10 minutes of confirmed store traffic, check the basics first.Steps to fix:
  1. Go to Integrations → Destinations → TikTok
  2. Verify the Pixel ID and Access Token are correct (no extra spaces or truncated characters)
  3. Confirm the destination status is Active (green)
  4. If the token was revoked or expired, generate a new one in TikTok Business Center and update the destination
If you see inflated conversion counts, another TikTok event source is likely still active.Steps to fix:
  1. Check for the TikTok Shopify sales channel — disable its data sharing / pixel component
  2. Look for third-party pixel apps (Omega, Mega TikTok Pixel) and uninstall them
  3. Inspect your theme code for manual TikTok pixel snippets in the <head> section
  4. After removing duplicate sources, monitor TikTok Events Manager for 24 hours to confirm counts normalize
TikTok’s match quality measures how well server events match to TikTok users.Common causes:
  • High anonymous traffic — Events from visitors who haven’t logged in or provided contact info have fewer matching parameters. Match quality improves as more identified customers generate events.
  • Incorrect pixel ID — If the pixel ID doesn’t match the one associated with your ad account, events arrive but can’t be matched to campaign data.
Match quality typically improves over 1–2 weeks as Upstack’s identity resolution builds visitor profiles.
For additional troubleshooting beyond TikTok-specific issues, see Troubleshooting: Events Not Reaching Destination.

Conversion API forwarding

How Upstack Signal forwards events to ad platforms via server-to-server APIs.

Identity resolution

How Upstack matches anonymous visitors to known customers for higher match rates.

Meta CAPI destination

Set up Meta’s Conversions API as another server-side destination alongside TikTok.

Events not reaching destination

End-to-end diagnostic guide when events aren’t arriving at any destination.