Every event Segmently sends to TikTok (Pixel + Events API)
The complete list of the events and parameters Segmently sends to TikTok — the browser Pixel events as your visitor moves through the funnel, and the server Events API events from Stripe payments, including the exact TikTok standard-event names each one becomes.
Where this fits
This is reference material for the optional ad-tracking step of launching a funnel, for advertisers running TikTok ads. It assumes you have already added the TikTok Pixel and TikTok Events API integrations (see the TikTok setup guide). Once both are connected, the events below flow automatically — you do not configure events one by one. Use this page to choose which event to optimize TikTok campaigns on and which to build audiences from.
Two paths: the browser Pixel and the server Events API
Segmently sends to TikTok in two ways. The browser Pixel fires from the visitor's device as they move through the funnel and reports rich behaviour, but can be blocked by ad blockers. The server Events API fires from Segmently's servers when Stripe confirms a payment event, and is the reliable money signal that does not depend on the browser. The two are de-duplicated so the same sale is not counted twice.
How browser Pixel events are sent
The browser Pixel sends each event with its original Segmently name (technically ttq.track(name, params)). So in TikTok Events Manager the browser stream appears under names like ScreenDidAppear and StripePurchase. They fire only when the TikTok Pixel integration is enabled and — if you use GDPR consent — only after the visitor accepts cookies. Unlike the browser Pixel, the server Events API remaps payment events to TikTok's standard names (covered below).
Browser Pixel events: journey and navigation
The browser Pixel reports the same funnel behaviour as the Facebook Pixel does. These journey and navigation events fire as the visitor moves through the funnel:
StartOnboarding
Parameters: projectId, onboardingId, versionId. Fires when the funnel starts.
ScreenDidAppear
Parameters: screenID, screenName. A screen was shown.
ScreenDisappeared
A screen was left.
RouteTaken
Parameters: screenID, targetScreenId, actionKey. A navigation route was followed.
PageHidden
Parameters: timeOnScreenMs. The page was backgrounded.
FunnelExited
Parameters: screensVisitedCount. The visitor left the funnel.
OnboardingFinished
The funnel reached its end.
Browser Pixel events: inputs, buttons and interaction
These fire as the visitor answers questions, presses buttons, and interacts with screens:
UserUpdatedValue
Parameters: the value, blockType, dataKey. The visitor changed an answer.
FieldInputValueError
An input failed validation.
VariableUpdated
Parameters: variableName, value. A funnel variable changed.
FirstFooterButtonPressed and SecondFooterButtonPressed
A footer (primary/secondary) button was pressed.
LeftNavbarButtonPressed, RightNavbarButtonPressed, CloseNavbarButtonPressed
A navbar button was pressed.
AbTestLoaded
Parameters: abTestVariantName. An A/B test variant was assigned.
AcceptCookiesPressed / DeclineCookiesPressed
The visitor responded to the GDPR consent banner.
DownsaleTriggered
A downsale offer was shown.
Browser Pixel events: paywall and payment
The buying-intent signals from the browser:
ProductSelected
Parameters: productId, price, currency. A plan was chosen.
PurchaseFooterButtonPressed
Parameters: productId, price_id, offer_type, trial_days, paywall_type, buy_intent_status. Buy / Continue to pay was pressed.
StripeCheckoutSessionCreated
Parameters: sessionId, paywallProductId.
StripePaymentIntentSuccess
Parameters: paymentIntentId, mode.
StripePurchase
Parameters: productId, mode.
StripeSubscriptionCreated
Parameters: subscriptionId, mode.
StripeCheckoutSessionSuccess / StripeCheckoutSessionCancel
The hosted Checkout session succeeded or was cancelled.
StripePaymentElementError
Parameters: error. The in-funnel payment element raised an error.
Why browser payment events are not enough
As with Facebook, these browser payment events can be lost to ad blockers — which is why the server Events API events below are the dependable conversion source.
Server Events API events and their TikTok names
When Stripe confirms money has moved, Segmently sends the conversion to the TikTok Events API, remapped to TikTok's standard event names so they power TikTok's reporting and optimization. Each carries value and currency. The exact mapping (a trial start also maps to Subscribe):
Purchase → CompletePayment
A completed payment — TikTok's equivalent of a purchase.
Subscribe → Subscribe
A subscription started.
RecurringPayment → CompletePayment
TikTok treats a renewal as a payment.
CancelSubscription → CancelSubscription
A subscription was cancelled.
PaymentFailed → PaymentFailed
A charge failed.
What to optimize on
So when you optimize a TikTok campaign for purchases, you optimize on CompletePayment.
How each Stripe moment becomes an event
The Stripe-to-event logic is the same as for Facebook, then remapped to TikTok's names: • A completed one-time purchase, an in-funnel card or wallet payment, the first charged subscription invoice, or the first charge after a real trial → Purchase, which TikTok records as CompletePayment. (A free-trial invoice that charges nothing is skipped.) • A later subscription renewal → RecurringPayment, also recorded as CompletePayment. • A subscription becoming active or in trial → Subscribe. • A cancellation → CancelSubscription. • A failed charge → PaymentFailed. So CompletePayment is your real-revenue signal in TikTok, and Subscribe marks the subscription decision.
What customer and value data is attached
The server Events API events carry the data TikTok uses to match a conversion to the right person. Personal details are securely hashed (SHA-256) before sending: email, phone, and external_id (your Segmently visitor id). Browser-matching signals are sent as-is because TikTok expects them raw: ttp (the TikTok browser id), ttclid (the TikTok click id from the ad URL), ip, and user_agent. The conversion itself carries value, currency, and a contents array carrying content_id (plus order_id and content_type=product), and the request identifies your pixel via event_source_id (your TikTok Pixel Code). This is why mapping ttp and ttclid into Stripe metadata at publish improves how many conversions TikTok can attribute to a click.
Why a sale is not counted twice
Each server Events API event carries a stable event_id derived from the Stripe event, and the same id is used so TikTok can recognise the browser and server reports of the same sale and merge them. The result is better match quality from the server signal without double-counting. This works automatically as long as the Pixel Code matches between your TikTok Pixel and Events API integrations.
Which events optimize your TikTok ads
For most paid funnels: optimize purchase campaigns on CompletePayment (the reliable server revenue signal) and, for subscription products, on Subscribe. Use the browser PurchaseFooterButtonPressed (buy intent) as an upper-funnel signal while you gather enough conversions. Build audiences from the journey events — StartOnboarding, ScreenDidAppear on the paywall, and ProductSelected — to retarget interested visitors who did not buy.
Next
If you have not connected TikTok yet, open the TikTok Pixel and Events API setup guide to add both integrations and the matching Pixel Code. Running Meta ads too? The Facebook events catalog lists the equivalent events and the names Meta records.