What This Tutorial Covers
By the end, your TikTok purchase events will fire server-side through the Events API with hashed identity attached, your pixel and server events will deduplicate on a shared event ID instead of double-counting, and refunds will send CancelOrder corrections so TikTok's targeting stops training on buyers who reversed.
You will need:
- A TikTok Ads Manager account with a pixel created in Events Manager
- An Events API access token (generated per pixel in Events Manager)
- A tracker or server layer that can fire server-side events
- Access to your opt-in or checkout form to capture identity
- The offer you are running TikTok traffic to
I will use ClickerVolt as the reference layer because it ships the full twelve-field TikTok payload and CancelOrder refund correction on every plan, and I built it, so the examples are ones I can vouch for. The same structure applies with RedTrack or another server-side tracker; I will flag where the manual work appears.
Step 1: Create the Pixel and Generate the Access Token
In TikTok Events Manager, create a pixel (or open your existing one), then generate an Events API access token under the pixel's settings. The token authorizes server calls for that specific pixel, so if you run separate pixels per geo or offer, you need a token for each.
One naming note that saves audit pain later: TikTok renamed the purchase event from CompletePayment to Purchase in May 2025. Both names still work and report identically, but pick one convention for your stack and keep it consistent, because a funnel firing CompletePayment from the pixel and Purchase from the server is the kind of mismatch that makes debugging miserable.
Step 2: Keep the ttclid Alive Through Your Funnel
When someone clicks your TikTok ad, TikTok appends a ttclid parameter to your landing page URL. That click ID is the strongest matching key you have, it is valid for 30 days, and it is also the most fragile thing in your entire setup. Every hop in an affiliate funnel is a chance to drop it.
The ttclid only has to go missing at one hop for the conversion to arrive anonymous; capture it at first touch and reattach it server-side instead of praying every redirect preserves it.
The reliable pattern is to stop depending on the URL after the first touch. Your tracker should read the ttclid the moment the click lands, store it server-side against the visitor's session, and reattach it when the conversion event fires days later. ClickerVolt does this automatically at the redirect layer. If you are wiring this manually, audit every 302 in your chain and every CTA link on your landers, because one bare URL anywhere breaks the chain silently.
Step 3: Capture Identity at Opt-In
TikTok matches server events against three identity keys beyond the click ID: hashed email, hashed phone, and your external ID for the user. The click gives you none of these. Your opt-in form gives you all of them.
Normalization matters more than most guides admit. Email is lowercased and trimmed before SHA-256 hashing. Phone goes to E.164 format (country code, no spaces, no dashes) before hashing. A phone hashed as "(555) 123-4567" and the same phone hashed as "+15551234567" are two different hashes, and only one of them matches anything in TikTok's graph. Hash mismatches do not error; they just silently match nothing, which is why setups that look complete still underperform.
Step 4: Build the Server Event With the Full Payload
A complete TikTok purchase event carries twelve fields. Most setups send five or six.
The identity block: hashed email, hashed phone, hashed external ID, the ttclid you persisted in Step 2, the ttp cookie value if present, client IP, and user agent. The transaction block: value, currency, content ID, order ID, and the event ID you will use for deduplication in Step 5.
The order ID deserves a special mention for affiliates: it is what lets you tie this conversion back to the network transaction later, which is exactly what you need when the refund arrives in Step 6. Skip it and your CancelOrder events have nothing to reference.
Step 5: Deduplicate the Pixel and the Server Event
Run the pixel and the Events API together; the pixel catches what the server misses and vice versa. The trap is double-counting: without deduplication, TikTok counts one sale twice, your reported CPA looks better than reality, and you scale a campaign on fiction.
Mint one event ID per conversion. Pass it to the pixel as the event_id and to the server event as the same event_id. TikTok merges the pair into a single conversion. Test this before trusting it: fire a test conversion and confirm Events Manager shows one event, not two.
Step 6: Fire CancelOrder When the Refund Hits
This is the step almost nobody builds, and it is the one that compounds. On affiliate offers, 5 to 20 percent of sales reverse within weeks. If those reversals never reach TikTok, the algorithm keeps every refunded buyer in its model of your ideal customer and goes looking for more people like them. You pay for the traffic twice: once for the refund, once for the lookalikes of the refunder.
The fix is the CancelOrder event: a server-side correction referencing the original order ID. When your network reports a reversal (ClickBank IPN, network postback), fire CancelOrder for that order. ClickerVolt's Refund Sync does this automatically because its IPN receivers already parse reversals; in a manual stack, this is a webhook handler you write once and never regret.
Step 7: Verify in Events Manager
Three checks before you call it done. First, event volume: server events should be arriving alongside pixel events, deduplicated to single conversions. Second, match quality: TikTok scores your events on identity richness, and a complete Step 3 and 4 payload is what pushes that score up; if it is sitting low, something in your hashing or persistence is silently broken. Third, parameter completeness: open a received event and confirm the ttclid, hashed identity, and order ID actually arrived. Events Manager showing green is not the same as Events Manager showing complete.
The Mistakes That Quietly Break This
Four patterns account for most broken TikTok setups I get asked to look at. Hashing un-normalized values, so identity fields match nothing (Step 3). A redirect chain that strips the ttclid on hop two, so conversions arrive anonymous (Step 2). Pixel and server events with no shared event ID, so every sale counts twice (Step 5). And no CancelOrder handling at all, so the model trains on refunders forever (Step 6). None of these throw errors. All of them cost money every day they go unnoticed.
Why This Matters More on TikTok Than Anywhere Else
Meta has had a decade to build fallback matching for weak signals. TikTok's ad platform is younger, its audience is more locked inside in-app browsers, and its algorithm reacts faster to the data you feed it, in both directions. A complete Events API payload gets rewarded quickly. A thin one gets buried just as quickly. The affiliates winning on TikTok in 2026 are not the ones with better creative; they are the ones whose conversion signal the algorithm can actually use.
FAQ
Do I need the TikTok Events API if I already run the TikTok pixel?
Yes, if you care about match rate. The pixel alone loses signal to in-app browser restrictions, ad blockers, and cookie limits, and it cannot carry the full identity payload. Run both, deduplicated on a shared event ID, with the server event as the primary signal.
What is the ttclid and how long does it last?
The ttclid is the click ID TikTok appends to your landing page URL when someone clicks an ad. It is valid for 30 days and is the strongest attribution key in a server event. Capture it at first touch and store it server-side, because redirect chains drop it easily.
Is CompletePayment or Purchase the right event name in 2026?
TikTok renamed CompletePayment to Purchase in May 2025. Both still work and report identically. Pick one convention across your pixel and server events and stay consistent.
What is the CancelOrder event for?
CancelOrder is the server-side correction you send when a tracked sale refunds or reverses. It references the original order ID and tells TikTok's algorithm to stop treating that buyer as a successful conversion. Without it, refunders stay in your targeting model permanently.
Can I do this whole setup without a tracker?
Technically yes: persist the ttclid yourself, hash identity at opt-in, build the Events API calls, and write a reversal webhook. It is a real engineering project. A tracker that does this natively collapses it to connecting your accounts; that is the entire reason I built the TikTok stack in ClickerVolt the way I did.
