# How to track delayed live stream starts


If you need to see which live streams started later than planned, use webhooks. We send an event when a media status changes, and your system can compare the actual event time with the scheduled start time.

## When this scenario fits

This scenario fits when you already have the scheduled stream time: for example, in an LMS, CRM, event schedule, or your own admin panel.

Kinescope does not calculate the start delay instead of your system. We can send a status-change event, and your side should calculate the delay: store the scheduled time, receive the webhook, and compare it with the actual event time.

## How to set it up

1. Create a webhook through the API.
2. Subscribe to the media status change event.
3. Store the scheduled live stream start time in your system.
4. When the webhook arrives, check the new status and the event receive time.
5. Compare the actual time with the scheduled time and store the difference.

This lets you build a report showing which live streams started later than scheduled and by how many minutes.

## What to keep in mind

The webhook reports an event in Kinescope, but it does not know your schedule. If the scheduled time lives in an external system, that system should calculate the delay.

Also account for webhook delivery delays and retries on your side. For analytics, it is usually enough to calculate the delay by the actual event time, or by the first successful webhook receive time if your data model has no separate event timestamp.

## Related materials

- [Create webhook](https://docs.kinescope.com/api/#v1-webhooks-create-webhook)
- [Webhook types: media.update.status](https://docs.kinescope.com/developer-guides/webhook-types/#mediaupdatestatus)