All articles

Webinar platform that fires a webhook at a watch-time threshold

WebinarStack fires a signed webhook when an attendee passes a watch-time threshold, during the session. What other platforms emit instead, and what to trigger.

Josh Miller

WebinarStack sends a webhook the moment an attendee passes a watch-time threshold you set, in minutes or percent watched, so any downstream system can act on real viewing behaviour. Among the platforms we checked, only eWebinar lists percent-watched events, and all of them fire after the session ends. Most others expose registration and attendance events.

What is a watch-time webhook?

A watch-time webhook is a message sent to your own URL when an attendee has watched a set amount of the video, rather than when they register or join. It reports depth of viewing, not presence, which is the difference between "opened the room" and "stayed through the offer".

Most webinar platforms emit events about presence. Zapier's trigger lists, checked on 10 November 2026, show the pattern:

  • BigMarker lists five triggers: registration reports, new registrations and attendee-entered events. None measures how long someone watched.
  • WebinarJam lists eight, including New Live Attendee, Registrant Attends Replay, Registrant Leaves Before, Registrants Stays Until and Registrant Misses Webinar. These describe arrival and departure around a time. Zapier's listing does not describe a percent-watched measure.
  • eWebinar is the exception we found. Its Zapier app lists 15 triggers, three of them percent-based: "Attendee Stayed for X%", noted as not applying to replays and firing at the end of the exit room; "Attendee Left Before X%", also not applying to replays; and "Attendee Watched Replay for X%", noted as firing 15 minutes after the attendee leaves.

The timing is what matters. Every one of those eWebinar events lands after the viewing is over, which is useful for follow-up but cannot change what the attendee sees while they are still watching. We checked three platforms' public Zapier listings, not every product, so treat this as a sample of how the market emits events and not a census.

How does a watch-time webhook work in WebinarStack?

You create an automation rule on the webinar, choose a watch-time trigger, set the threshold, and attach a webhook action with your URL and a secret. When an attendee crosses the threshold, WebinarStack posts a JSON payload to that URL while the session is still running.

There are two watch-time triggers:

  • Watched at least X minutes, for example 20 minutes.
  • Watched at least X%, with a threshold from 1 to 100.

Each fires once the attendee has watched at least that much, and a threshold stays crossed once crossed. Watch state is built from the furthest point reached rather than a running tally, so rewinding does not un-cross a threshold.

The payload is JSON. It carries the trigger type as event_type, the attendee's name, email and registration ID, any UTM parameters they registered with, the webinar's ID and title, and a timestamp. We have not documented the threshold value as its own payload field, so match the trigger type to the rule that fired rather than reading a number out of the body.

Deliveries are signed. The X-WebinarStack-Signature header carries an HMAC-SHA256 signature of the body, computed with your webhook secret, so your endpoint can reject anything that did not come from us. A non-2xx response retries with exponential backoff, up to three retries, and a delivery that exhausts them lands in a dead-letter queue.

What can you trigger with a watch-time webhook?

Anything your endpoint can do. Treat watch depth as a qualification signal and act on it in another system:

  • Tag the contact in your CRM when they pass 50 percent, so sales sees the engaged attendees first.
  • Alert a salesperson the moment someone watches past the offer, while they are still in the session.
  • Enrol the attendee in a course or a waitlist when they finish.
  • Start a follow-up sequence keyed to how far they got, instead of one sequence for everyone.

WebinarStack also sends email, SMS, ESP and Meta CAPI actions from the same triggers, so a webhook is the option when the destination is a system we do not integrate with directly. For the email version of this, see webinar software that triggers emails based on watch time.

What do people do instead, and what does it cost?

They reconstruct watch depth outside the platform. That usually means polling a platform's API after the session, or chaining Zapier or Pipedream steps off whatever attendance events the platform does emit.

It works, and plenty of teams run it. The result arrives after the session, because that is when the platform's data is complete. It is lossy, because attendance events say who was present and not how much they watched. And it adds another subscription to pay for and monitor. None of this is fatal. It is the price of a platform that does not report watch depth natively.

Where does this stop?

Four limits to know before you build:

  • Conditions are AND-only. "Watched 20 minutes and clicked the offer" works as one rule. "Watched 20 minutes or clicked the offer" needs two rules.
  • Minutes-watched is dashboard-only. The percent-watched trigger is available to Zapier and Make, and the minutes-watched trigger is not. Native webhook actions work with both. Only 9 of the 18 automation triggers are exposed to Zapier and Make at all.
  • WebinarStack runs pre-recorded webinars only. If you present live, a live platform is the right tool, and this feature does not change that.
  • It starts at $99 a month. Pricing is on the pricing page.

All 18 triggers are listed out in WebinarStack vs AEvent, and the features page is the shorter tour. The head-to-head comparisons are WebinarStack vs EasyWebinar and WebinarStack vs EverWebinar, and the wider ranking is best automated webinar software for course creators.

Sources

  • BigMarker triggers as listed in Zapier: zapier.com/apps/bigmarker/integrations, checked 10 November 2026
  • WebinarJam triggers as listed in Zapier: zapier.com/apps/webinarjam/integrations, checked 10 November 2026
  • eWebinar triggers and their timing notes as listed in Zapier: zapier.com/apps/ewebinar/integrations, checked 10 November 2026
  • eWebinar integrations page, which names webhooks and Zapier without listing events: ewebinar.com/integrations, checked 9 November 2026
  • WebinarStack triggers, webhook signing and retries: verified against the application source, 10 November 2026

Frequently asked questions

Which webinar platform sends a webhook when someone watches past a certain point?
WebinarStack does. You set a threshold in minutes or percent watched on an automation rule, attach a webhook action, and it posts a signed JSON payload the moment the attendee crosses it, while the session is still running. Of the platforms whose Zapier triggers we checked on 10 November 2026, eWebinar also lists percent-watched events, but they fire after the session, at the end of the exit room or 15 minutes after a replay viewer leaves.
Is a webhook on watch time the same as a webhook on attendance?
No. An attendance webhook tells you someone joined or left. A watch-time webhook tells you how much of the video they actually watched, which separates a person who opened the room and walked away from one who stayed through the offer. Most platforms emit attendance events; watch depth is the rarer signal.
Can I get the same result with Zapier?
Partly. WebinarStack exposes the percent-watched trigger to Zapier and Make, so you can route it there, but the minutes-watched trigger is dashboard-only. For platforms that only emit registration and attendance events, Zapier cannot invent watch depth that the platform never reports.
Is the webhook signed so I can verify it came from WebinarStack?
Yes. Each delivery carries an X-WebinarStack-Signature header containing an HMAC-SHA256 signature of the request body, computed with the secret you set on the webhook. Verify it on your server before acting on the payload.
What happens if my endpoint is down when the webhook fires?
A non-2xx response makes the delivery retry with exponential backoff, up to three retries. If every retry fails, the failure is recorded in the dead-letter queue instead of disappearing, so a missed delivery can be found afterwards.

Run this on your own webinar

WebinarStack records your webinar once and runs it every day after that, with follow-up driven by what each attendee actually did.