Default behaviour

By default, when you create a DAI (Live Ad Replacement) service, broadpeak.io only performs substitution of ads in future ad breaks (that is: ad breaks that start appearing in the stream after the user has started the streaming session).

In this mode, any ad break that appears in the DVR Window is not replaced.

📘

For the purpose of illustration in this page, we use a very contrived example in which the same ad break is repeated regularly in the live stream. The ad server also always returns the same VAST response with the same 2 ads.

📘

Gap filling

The standard rules apply to determerin whether and how a gap filler is used, as explained in this section

If the live edge is within an ad break, a complete substitution of that ad break is performed, even for segments that precede the live edge.

DVR Window monetization

When configuring your DAI service, you can define whether past ad breaks should be monetized (ie. subject to the ad insertion logic).

• In the WebApp, with the "Replacement of past ad breaks" control in the "Ad replacement" section
• With the APIs, with the liveAdReplacement.pastAdBreakReplacement property of the "Create an ad insertion service" endpoint

❗️

Pre-roll

The monetization of the DVR window is only possible if you do not activate the pre-roll feature for your service, as it blanks the whole DVR window.

With Full DVR window (pastAdBreakReplacement = -1), all ad breaks in the DVR window are replaced.

Instead, if you only want to configure a specific duration in the DVR window within which ad replacement will be performed, use the Configure duration with a value (in seconds).
(with the API: pastAdBreakReplacement = x with x > 0)

❗️

New services

Note that only ad breaks that have been detected since the service have been created can be replaced in this way. If you have just created a service with a live source with a long DVR window, those ad breaks will not have been detected by broadpeak.io and therefore cannot be replaced.