Broadcaster
A broadcaster who needs visibility into whether SCTE-35 markers are actually being added and distributed on each channel, so a silent failure does not leave breaks unsignalled downstream
Streaming platformReady to pilotBuilt by Professional ServicesLast updated 13 August 2026
Streaming platformReady to pilotBuilt by Professional ServicesLast updated 13 August 2026
SCTE Markers Web Hooks
Notify systems the moment a live-stream marker appears
Broadcasters already put the signals that matter - ad breaks and other live-stream events - into the feed as SCTE-35 markers, but if the distribution system cannot pass those markers on, nothing downstream can use them. SCTE Markers Web Hooks detects each defined marker and pushes it to a configured receiver as a webhook the moment it appears, so connected systems receive the information immediately instead of polling an API and hoping they ask at the right time.
SCTE-35 detectionReal-time webhooksCustom receiversEvent-driven automation
The problem this solves
Ad break signalling and other live-stream events are already present in the feed as SCTE-35 markers. The problem is not that the information is missing - it is that if the distribution system cannot carry those markers further, they stop at the stream and cannot be used. The cue the broadcaster added never reaches the systems that would act on it.
That is exactly the information ad decisioning, reporting, social automation and alerting need: the metadata broadcasters already insert into the live stream to mark when something happens. Without a way to forward it, those systems fall back to pulling an API, watching playlist changes or reconstructing the event after the fact - and by then the moment to use it has often already passed.
You should not have to poll an API waiting for news the stream already knows. Your system can receive that information the instant the marker is detected and act on it immediately.
Who this is for
This is relevant if you are:
Platform operator
A platform operator who needs the exact time an advertisement occurred in a live stream - including to enforce seek locks during that window when the product requires scrubbing of content to be blocked
Telco
A telco or platform team running SSAI or ad reporting that needs the exact break window the moment it opens, so ad decisioning and impression reconciliation are driven by the live marker rather than by delayed playlist inference
How it works
- 1
Configured SCTE-35 markers are detected in the live stream as they pass, rather than reconstructed later from manifest or playlist changes.
- 2
Each marker is normalised into an event that carries the channel, the marker type and the exact time it occurred.
- 3
The event is delivered immediately to a predefined receiver as a webhook, so connected systems are notified when the marker happens rather than when they next ask.
- 4
The destination system, API, protocol and payload shape can be adapted per customer, so the same marker detection can drive different downstream workflows without those systems needing to understand transport streams or manifests.
What makes it different
The markers are already in the stream; what is usually missing is a distribution path that turns them into something outside systems can consume. SCTE Markers Web Hooks closes that gap: the same cue a broadcaster added for ad breaks or other live events becomes an ordinary webhook any receiver can act on, without that system needing to understand transport streams or manifests. The value is not limited to exposing SCTE-35 data - the same approach enables custom event-driven integrations that connect markers inside the video workflow directly with systems outside the streaming stack. Instead of repeatedly asking whether something has happened, downstream systems are told when it happens.
Current status & next steps
Ready to pilotReviewed 13 August 2026
SCTE Markers Web Hooks is ready to pilot. The solution is already deployed on the Simpli platform, where it is used to block seeking across advertising blocks on linear TV catch-up recordings - a requirement from the channel providers on that service.
Simpli includes a player integration that consumes those marker events and enforces the seek lock for the duration of each ad break, so the restriction is driven by the live-stream markers rather than by a separately maintained schedule.
If you have a similar need, we can help. The same approach can be adapted to your environment - changing the input protocol, the delivery method, the receiver shape or the optimisation around how and when events are pushed - so the integration fits the systems you already run.
Need the same for your catch-up or live workflow?
Tell us how markers reach your platform today and what should happen when a break opens. We can adapt the protocol, delivery and player-side integration to your requirements.