Skip to main content
TrackingConsultingFree audit
TikTok · Checkout → purchaseUse-case guide

How to track checkout to purchase for TikTok Ads

Everything between checkout starting and the order existing is where ecommerce tracking actually fails, and it fails differently depending on how your checkout is built. A hosted payment page is a different domain. A wallet payment can complete without the customer ever seeing the confirmation. Both produce orders in your store that no platform ever hears about. On TikTok Ads the specifics that matter are the click identifier (ttclid), the import mechanism (the Events API), and deduplication uses a shared event ID between the pixel and the Events API, the same principle as Meta. The chain only works end to end if the identifier is captured on landing and stored on the order record in your store — no cookie survives the gap between checkout started and purchase sent with the order id.

Get my free conversion tracking auditSee what we check

Free30 minutesNo obligation

By Ariful IslamTikTok · Checkout → purchase, in short ↓

Specific to TikTok × Checkout → purchase

TikTok: InitiateCheckout to CompletePayment across the app hop

On TikTok, send InitiateCheckout and AddPaymentInfo from the pixel and CompletePayment through the Events API from the order webhook, with the order ID as the shared event ID and ttclid saved on the cart at checkout start. That catches orders paid through wallets or hosted pages that never return to the confirmation page.

TikTok checkouts start inside TikTok's in-app browser, and payment is where the shopper is most likely to leave it. A PayPal or wallet button may jump to another app, and the return lands in Safari or Chrome with none of the in-app browser's storage. The pixel on the confirmation page then fires without ttclid, or doesn't fire, and the TikTok-driven order looks organic.

Write ttclid onto the cart when InitiateCheckout fires, not at landing alone, so it travels with the order whatever browser finishes the payment. The order webhook then sends CompletePayment with the stored ttclid, value, currency and hashed email and phone, and the same order ID as the pixel's event ID so a browser CompletePayment that does fire doesn't double-count.

On TikTok, AddPaymentInfo is worth sending even if no campaign optimizes on it, because it separates in-app checkout friction from payment-return loss. If the AddPaymentInfo to CompletePayment rate on TikTok traffic is far below the same rate on desktop traffic, the payment hop out of the in-app browser is the problem, and no audience change will fix it.

TikTok · Checkout → purchase · what breaks

Where this funnel usually breaks — TikTok · Checkout → purchase

  1. 01

    Wallet payments skip the confirmation page

    Shop Pay and PayPal can be abandoned after the money moves. The order is real; the page view never happened.

  2. 02

    A hosted payment page on another domain

    Session splits, the click identifier doesn't cross, and the purchase gets credited to your own site as a referral.

  3. 03

    Every payment method assumed to behave the same

    Card, wallet and redirect gateways each return differently, and the untested one is where the missing conversions are.

TikTok · Checkout → purchase · the fix

What working looks like — TikTok · Checkout → purchase

  • Purchase sent with the order ID attributed to the click

    Weeks later if necessary, because the identifier lives on the order record in your store rather than in a cookie.

  • TikTok bidding fed the real outcome

    Via the Events API, so it optimizes toward completed orders rather than toward checkout starts.

  • A reconciliation that closes

    Your store's order records, web orders only matched per record against what TikTok Ads reports, over a fully closed window.

TikTok · Checkout → purchase · architecture

The exact event sequence — TikTok · Checkout → purchase

Stage three is the one you often can't instrument, which is precisely why stage four has to be the source.

  1. 1

    Checkout started

    Browser-side, with value. The last point you reliably control the page.

  2. 2

    Payment info submitted

    Worth splitting out — it turns one opaque step into a diagnosable one.

  3. 3

    Payment authorised

    Often on someone else's domain, and frequently invisible to your tags entirely.

  4. 4

    Order created

    From the order webhook. This is the only step that sees every order regardless of how payment happened.

  5. 5

    Purchase sent with the order ID

    Deduplicated on that ID, with refunds wired to reverse.

TikTok · Checkout → purchase · diagnose

What's specific to TikTok Ads

  1. 01

    Click identifier: ttclid

    TikTok's click identifier, appended to the landing URL. Capture it on landing and persist it exactly as you would gclid or fbclid — it's the strongest matching signal available and the most commonly missing one, because TikTok is often added to a stack that was built around Google and Meta.

  2. 02

    Import mechanism: the Events API

    Structurally similar to the other server-side conversion APIs: event name, timestamp, event ID, hashed user identifiers, event properties. TikTok's exact field names change more often than the other major platforms', so build against their current documentation rather than a blog post — including this one.

  3. 03

    Deduplication

    Send the same event ID from the browser pixel and the server event. The mechanics mirror Meta's closely enough that a team who has done one can do the other, but verify TikTok's current requirements rather than assuming parity — the deduplication window in particular isn't a figure we'll guess at.

  4. 04

    Window and timing

    Verify the current attribution and import windows in TikTok's documentation. They differ from Google's and Meta's, and quoting a number here that goes stale would be worse than sending you to the source.

  5. 05

    The TikTok gotcha

    TikTok is usually the third platform added to a stack, and it typically inherits whatever assumptions were made for Google and Meta. The most common result is that ttclid is never captured at all, because the capture code was written naming gclid and fbclid and nobody revisited it.

TikTok · Checkout → purchase · prove

How to prove the chain works — TikTok · Checkout → purchase

Source of truth

your store's order records, web orders only

  • The same identifier confirmed on the order record in your store after a full real journey through every step.
  • Purchase sent with the order ID confirmed arriving at TikTok Ads, verified by TikTok's own event diagnostics, plus a reconciliation against your records.
  • Your store's order records, web orders only reconciled against TikTok Ads per record over a fully closed window.

TikTok · Checkout → purchase · free audit

What we check in the free audit

  • Click identifier: ttclid
  • Import mechanism: the Events API
  • Deduplication
  • Window and timing
  • The TikTok gotcha

Checked against

your store's order records, web orders only

Get my free conversion tracking audit

Free30 minutesNo obligation

TikTok · Checkout → purchase · when not to buy

When this doesn't apply to you — TikTok · Checkout → purchase

  • If your checkout is entirely on your own domain with no wallet options and a confirmation page every customer reaches, the browser-side event may genuinely be sufficient — reconcile a closed week and find out before building anything.
  • If TikTok is a small share of your spend, the effort is better spent making Google and Meta correct first — the same infrastructure then extends to TikTok as one additional tag rather than a separate project.
  • If your cycle from click to purchase sent with the order id regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward payment info submitted instead and use the later data for budget decisions rather than for bidding.
  • If almost none of your orders carry a click identifier today, that's the whole project.

TikTok · Checkout → purchase · what we deliver

The implementation, on TikTok Ads

  • Capture ttclid on landing

    ttclid is appended on ad clicks. Add it explicitly to your capture list — the single most common TikTok tracking fault is capture code that predates TikTok being in the account.

  • Persist it to the order record in your store

    Set a first-party cookie server-side before the hop, and pass the identifier into the payment domain where the provider supports it — where it doesn't, the order record is the only path.

  • Send purchase sent with the order id from the record

    The order webhook fires once per order, independent of which payment path the customer took or whether they ever saw a confirmation page. Dispatched to TikTok Ads through the Events API.

  • Deduplicate and reverse

    Deduplication uses a shared event id between the pixel and the events api, the same principle as meta. Refunds reverse from the refund webhook; failed and cancelled orders should never have counted in the first place.

Get my free conversion tracking audit

From $400 · See packages

FAQ

TikTok · Checkout → purchase questions, answered

Often the payment step leaves TikTok's in-app browser and the confirmation page fires without ttclid, or never loads. Send CompletePayment from the order record with ttclid saved on the cart.

More on TikTok · Checkout → purchase

RELATED GUIDES

Funnels next to checkout to purchase, and the checks that close it

Free · 30 min

Get checkout to purchase tracked properly on TikTok Ads

Book the free call WhatsApp

Free30 minutesNo obligation