Skip to main content
TikTok · Add to cart → purchaseUse-case guide

How to track add to cart to purchase for TikTok Ads

This is the one funnel that mostly happens in a single session, which makes it look easy and hides where it actually fails: the purchase event at the end. Add to cart is cheap and reliable; purchase is the one that has to be right, deduplicated, and sourced from the order record rather than a page a customer can refresh. 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 ad click and purchase sent with the order id.

Free30 minutesNo obligation

Specific to TikTok × Add to cart → purchase

TikTok: impulse cart adds, and keeping CompletePayment honest

On TikTok, send AddToCart from the pixel and CompletePayment through the Events API from the order webhook, with the order ID as the shared event ID and ttclid stored on the order. Optimize on CompletePayment with value; treat AddToCart as reporting, because TikTok cart adds are plentiful and cheap.

TikTok produces the widest gap between cart adds and orders of any platform in this list. A video sells the product in fifteen seconds, the viewer taps through and adds to cart on impulse, and a good share never return to pay. That makes AddToCart a tempting optimization target with low cost per event and fast learning, and a poor one, because it rewards creative that sparks the tap rather than the purchase.

Send the money event as CompletePayment with value and currency from the order record, and confirm whether your account also exposes a newer Purchase event, because TikTok's event naming has shifted and the two should not both be sent for the same order. Value-based optimization only works if value arrives on every CompletePayment, including the server-side ones.

Check where the sale actually happens. If you also sell through TikTok Shop, those orders complete inside TikTok and never touch your site, so they are not website events at all and must not be pushed through the Events API as if they were. Mixing the two inflates TikTok's reported revenue and makes your store's ROAS look worse than it is. For catalog-based video shopping ads, the content_id on AddToCart has to match the TikTok catalog's product ID, or the retargeting audience is built from mismatched items.

TikTok · Add to cart → purchase · what breaks

Where this funnel usually breaks — TikTok · Add to cart → purchase

  1. 01

    Purchase fired on the thank-you page

    Refreshable, bookmarkable, and skippable by wallet payments. The order exists and no platform hears about it.

  2. 02

    Two systems both sending purchase

    A platform app plus a container is two conversions for one sale, and reported ROAS looks excellent until someone checks the bank.

  3. 03

    Refunds never reversed

    So reported revenue climbs and never falls, diverging from your books by your entire return rate.

TikTok · Add to cart → purchase · the fix

What working looks like — TikTok · Add to cart → 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 orders that were actually placed rather than toward cart adds.

  • 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 · Add to cart → purchase · architecture

The exact event sequence — TikTok · Add to cart → purchase

Stages one to three are browser-side and mostly fine. Stage four is where the money is and where the failures cluster.

  1. 1

    Ad click

    Identifier captured on landing and persisted for the session and beyond.

  2. 2

    Add to cart

    Browser-side, with item detail. The first genuine intent signal and the basis of most retargeting.

  3. 3

    Checkout started

    Browser-side. Where drop-off analysis lives.

  4. 4

    Order created

    From the order webhook, not the thank-you page — wallet payments can be abandoned after payment completes.

  5. 5

    Purchase sent with the order ID

    Deduplicated on that ID at every destination, so one sale counts once.

TikTok · Add to cart → 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 · Add to cart → purchase · prove

How to prove the chain works — TikTok · Add to cart → 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 · Add to cart → 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 · Add to cart → purchase · when not to buy

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

  • If you don't have a cart — a single-product checkout, a booking flow — the add-to-cart stage doesn't exist and you want the checkout-to-purchase sequence instead.
  • 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 checkout started 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 · Add to cart → 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

    For a single-session funnel a first-party cookie is usually sufficient — but set it server-side, because a JavaScript cookie is capped at seven days and any returning-visitor purchase falls outside that.

  • Send purchase sent with the order id from the record

    The order webhook fires once per order, carrying the order ID as the deduplication key and the real value and currency. 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 and cancellations should reverse from the refund webhook, which is the step almost nobody builds.

FAQ

TikTok · Add to cart → purchase questions, answered

Only as a short stopgap. TikTok cart adds are impulsive, and bidding on them finds people who tap and leave; switch to CompletePayment as soon as volume allows.

Free · 30 min

Get add to cart to purchase tracked properly on TikTok Ads

Free30 minutesNo obligation