Dynamic Ad Insertion Application

Ad Insertion logic

1. Without Transcoding involved
   When no transcoding Service is associated to the DAI Service, it is expected that the creatives are transcoded and packaged outside of broadpeak.io. It is also expected that the VAST response will contain m3u8 or mpd Mediafiles.
   In the case where the VAST response does not contain m3u8 or mpd Mediafiles, no insertion will be performed.
   This use-case is often associated with the scenario of direct sales where creatives can be retrieved a long time before air time, and therefore can be prepared in advance.
2. With Transcoding involved
   As soon as a transcoding Service is associated to a DAI Service, it is expected that the flow will go through the transcoding and preparation of the creatives through broadpeak.io so they can be delivered in HLS and MPEG-DASH formats.
   This use-case is often associated with the scenario of sales through programmatic where creatives are retrieved in real time, and cannot be prepared in advance. However, it also remains a valid use-case in Direct Sales, whenever creative are not prepared to be delivered over HLS and DASH by another system than broadpeak.io.

# Transcoding logic

Ad creative transcoding is activated by default in broadpeak.io when a transcoding Service is associated with the Ad Insertion Service.

If the VAST response contains a MediaFile of type "mezz" or "mp4", the transcoding flow will be triggered. If the VAST response contains other MediaFile, the transcoding flow will not be triggered.

The insertion will not be performed in the case where the VAST answer does not contain any compatible MediaFile.

Creating a Transcoding Service in broadpeak.io

Transcoding Services definition

It is not possible to define a transcoding Service on your own at this stage. We know it is not ideal but you have to get in touch with us to define the Service. Please reach out to us via your direct CSM contact or via the live chat.

Transcoding consideration period

The first time a creative is returned in the VAST response under a compatible MediaFile, a transcoded job is created to prepare the creative for HLS or DASH delivery. Depending on the transcoding profiles expected and the duration of the Creative, this process may take more or less time.

The creative will only be inserted into a Manifest when the transcoded jobs is over, and ready to be packaged for HLS or DASH delivery through JITP.

Transcoded Ad retention

By default, transcoded creative are stored 1 month in broadpeak.io.
Origin HTTP Cache-Control header is set to max-age 3600 seconds.