How to track quote request to closed job for TikTok Ads

Architecture

The exact event sequence

Five stages. The break is almost always between stages one and four, where the identifier has to survive a handoff from a web form into a field service system that a different team administers — and where the value spread between a small repair and a full replacement is wide enough that averaging destroys the signal. The identifier has to survive all of them.

1. Step 1

   Quote requested

   A form or a call. High volume, and most of it is comparison shopping across three or four vendors.

2. Step 2

   Estimate scheduled

   A time commitment from the customer, and the first signal that means anything.

3. Step 3

   Estimate attended

   The visit actually happened. No-show rates on cold paid traffic are meaningful and differ by campaign.

4. Step 4

   Job signed

   The money event, at the actual contract value rather than an average.

5. Step 5

   Job completed

   Final revenue, which can differ from the contract once change orders land.

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 job record in your field service or job management system after a full real journey through every step.
• Job completed confirmed arriving at TikTok Ads, verified by TikTok's own event diagnostics, plus a reconciliation against your records.
• Your job management system's signed and completed jobs, by date, at their contract values 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 you close on the first call at a flat price with no site visit, this funnel collapses into a much simpler one and you do not need the job system in the loop. Say so before anyone quotes you for it.
• 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 job completed regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward attended estimate, valued at your own estimate-to-close rate instead and use the later data for budget decisions rather than for bidding.
• If almost none of your job records 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.