How to track webinar attendance to purchase for Meta 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 Meta Ads

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

1. 1

   Click identifier: fbclid, which becomes the _fbc cookie

   fbclid arrives on the landing URL and is normally written into the _fbc cookie. If it isn't captured on landing, _fbc never exists — and _fbc is the strongest click signal Meta has, so its absence caps your match quality regardless of what else you send. Forward _fbp too, from the browser rather than regenerating it server-side.

2. 2

   Import mechanism: the Conversions API

   Server events go through CAPI with an action_source describing where the conversion happened. Offline outcomes flow through the same API rather than a separate product. Verify current field names against Meta's documentation before building — this surface changes.

3. 3

   Deduplication

   This is the mechanism that decides whether adding CAPI helps or doubles your conversions. Both the Pixel and the server event must carry the same event_id — the order or booking reference works best, because both sides can produce it without coordinating. A case difference in the event name alone produces two events even with a matching ID. Read the Deduplicated indicator in Events Manager over a full week, not one session.

4. 4

   Window and timing

   Meta's default attribution is a 7-day click and 1-day view. View-through is included by default, which is a large part of why Meta claims more conversions than your other platforms — that overlap is expected rather than a fault.

5. 5

   The Meta gotcha

   Match quality is where most Meta accounts lose attribution, and it's almost always normalization rather than coverage. An email hashed with a capital letter, or a phone hashed with brackets, produces a perfectly valid hash that matches nobody and errors nowhere. Normalize first, then hash, and read the score per event rather than overall.

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 Meta 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 Meta Ads, verified by the Deduplicated indicator and the per-event match quality score, both read over seven days.
• Your billing or crm record, joined to the webinar attendance log reconciled against Meta 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 you're advertising a business type Meta restricts data collection for — health being the obvious one — the parameters you can legitimately send are narrower, and that constraint should shape the build rather than be worked around.
• 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.