How to track webinar attendance to purchase for TikTok Ads

Architecture

The exact event sequence

Five stages. Two breaks, not one: the identifier is lost at registration because the form is hosted elsewhere, and then lost again between the webinar and the purchase because days pass and the device changes. The identifier has to survive all of them.

1. Step 1

   Ad click

   The identifier arrives on the registration page. Capture it here — the webinar platform will not.

2. Step 2

   Registration

   On a webinar platform's hosted form in most cases, which means the identifier has to be pushed in as a field rather than read from the page.

3. Step 3

   Attendance

   Registration-to-attendance runs between a third and a half for cold traffic. It is the single largest drop in this funnel.

4. Step 4

   Replay watched

   A real stage. Replay buyers are a meaningful share of revenue and are invisible if you only count live attendance.

5. Step 5

   Purchase

   Days later, from an email, on a different device. This is the event worth optimizing toward and the hardest one to connect.

Diagnostic sequence

What's specific to TikTok Ads

The funnel logic above is the same wherever you advertise. These are the parts that change because it's TikTok Ads.

1. 1

   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. 2

   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. 3

   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. 4

   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. 5

   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.

Source-of-truth validation

How to prove the chain works

One real journey, followed all the way, then a reconciliation. Neither on its own is enough.

• A live TikTok ad clicked, and the identifier confirmed present on the landing URL.
• The same identifier confirmed on the order or opportunity that followed the webinar after a full real journey through every step.
• Purchase confirmed arriving at TikTok Ads, verified by TikTok's own event diagnostics, plus a reconciliation against your records.
• Your billing or crm record, joined to the webinar attendance log reconciled against TikTok Ads per record over a fully closed window.
• The same reconciliation repeated 30 days later.

Straight talk

When this doesn't apply to you

Worth checking before you build anything, because two of these are common and both mean the work isn't worth doing.

• If your webinar is a support or onboarding session for existing customers, there is no acquisition funnel here and nothing to attribute.
• 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 regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward attendance of at least a defined watch duration instead and use the later data for budget decisions rather than for bidding.
• If almost none of your post-webinar orders carry a click identifier today, that's the whole project. Fix capture first — the import is the easy half and no tooling rescues a record with nothing to reference.