Server Side Ad Insertion (SSAI)

Owned by Lior W. (Unlicensed)
Last updated: May 28, 2024 by Ehud Kulaker
8 min read

SSAI List Page

SSAI is Server Side Ad-Insertion for CTV and OTT.

Screenshot 2024-04-18 at 11.33.12.png
List Page

The SSAI list page gives the user an overview on each SSAI entity:

  1. Stream format - HLS or DASH.

  2. Stream Type - live or VOD.

  3. Publisher- publisher’s name.

  4. Publisher channel - if single channel is selected, the channel’s name appears here.

  5. Inventory split channels - display all inventory split channels with their percentage.

  6. Modified - the last date the SSAI entity was modified.

  7. Status.

  8. Description.

  9. Actions - edit and archive.

Add/Edit SSAI

The SSAI is placed under the supply in the Aniview platform.

When you click in New SSAI or click to edit an existing one, you are presented with many useful options, most of which optional!

The SSAI configuration UI is divided to three tabs:

  1. Basic info

  2. Stream

  3. Monetization

Please remember to click Save after you’re done.

Basic Info

Screenshot 2024-04-16 at 11.58.28.png
Basic Info

The first tab is the basic info, this is where you set the information that is required, such as name, publisher, channel and inventory split…

  1. Name (required) - SSAI name.

  2. Description - any notes related to the channel.

  3. Publisher (required) - choose which of the to connect this SSAI to. The account name is set as default as the publisher.

  4. SSAI Route (required)- select the method you wish to work with:

    1. Single - a ready made channel which is connected to the SSAI entity.

    2. Inventory Split - some clients are required to split their inventory between the publisher channel and other channels. The first main channel is set for 100% of the inventory to the SSAI’s publisher channel and this can't be changed until another channel is added. When selecting add channel, another channel with another bar is added, select the second channel from the dropdown and slide the bar to the exact percentage needed for the split.

  5. Once saved, the inventory is then splits between the channels.

  6. VAST inventory split channel, gets a name that indicates that this channel is based on inventory split + VAST. E.g. Demo SSAI 2_INVSP#2_280524.

  7. There is only option to split between up to three channel at once.

  8. The inventory can be split to channels and VASTs both.

 

  1. Demand Type- defines the way that SSAI is connected to the demand. There are two ways to work in the demand type:

    1. Single - selecting this will open a dropdown with all the created server side channels associated to this network/publisher.

    2. VAST - direct VAST to the demand, which creates the ad source and channel in the backend. Once selected, a VAST box is open.

Using VAST in SSAI

  1. When using VAST directly in SSAI, it generates a channel in the backend without the need for the user to do it by himself.

    1. Channel - When a VAST is set in the SSAI, the system automatically creates a new channel with the a default name taken from the SSAI entity’s name + creation date. E.g. SSAI name: Demo SSAI, channel name: Demo SSAI_160424.

    2. In order to see the new channel in the channels list page, go to the channel list page and in the type filter, mark “THIRD PARTY (SERVER)”. Once doing that, the new automatically created channel will appear in the list below. (Please note, that this action must be invoked every time entering the channel’s list page).

    3. When an automatically channel is created based on a VAST, the channel’s name appears with its ID and is clickable so the user can switch directly to the channel’s page.

  1. When using VAST directly in SSAI, it generates an ad source in the backend without the need for the user to do it by himself.

    1. Ad source - when VAST is set in the SSAI, the system automatically creates a new channel with the a default name taken from the SSAI entity’s name + creation date. E.g. SSAI name: Demo SSAI, ad source name: Demo SSAI_160424.

    2. In order to see the new ad source in the ad source list page, go to the ad sources list page and in source type filter, mark “THIRD PARY VAST (SSAI)”. Once doing that, the new automatically created ad source will appear in the list below. (Please note, that this action must be invoked every time entering the ad source list page). Another way to get to the self-created ad source is via the associated channel.

    3. The VAST placed in the SSAI, now appears also in the created ad source/

  1. Publisher - When a publisher is set as publisher in the SSAI and VAST is set as the demand type, the system automatically creates a new publisher channel and publisher connection with the a default name taken from the SSAI entity’s name + creation date. E.g. SSAI name: Demo SSAI, Publisher Channel name: ch_Demo SSAI_160424.

Stream

The second tab is stream, this is where you set the technical aspects of the stream such as stream type, template, input and output URL’s…

  1. Steam type - defines if the stream is realtime Live (default) or VOD (Video on Demand).

  2. Stream format - there are two formats that can be used in the SSAI - HLS (an Apple format) and Mpeg DASH (an MPEG format). Today, SSAI supports HLS only.

  3. Template - defines the stream’s environment. Currently, there are two options - web (web player) and in app (all the other platforms except web, such as smart tv’s, mobile, tablets…).

  4. URL Type - defines which type of output URL will be used, if dynamic (default), it means that the URL displays only the mandatory macros. The dynamic URL always stays the same (no changes ) and all changes are done in the backend. If static is selected, it means that the URL displays all macros and every change needs to be done in the prefix itself (not in the backend).

  5. Ad Server Response - VAST (default) or VMAP.

  6. Input URL - editable text box, where the origin stream URL is placed.

  7. Output URL - read-only output of the generated URL, with manipulated manifest.

Monetization

The third tab is monetization, were all ads serving aspects are defined.

Markers

Markers indicate where downstream systems can insert other content (usually advertisements or local programs).

Use Markers - supported markers in SCTE35 protocol, these markers should be present in the source video.

Ignore Markers - refers to internal markers in the SSAI, which will be stitched into the video based on provided configuration of cue points every few seconds or minutes.

Pod Duration - is derived from the markers, when ignore markers is selected, the option of setting the pod duration is enabled. The user can set the duration of the pod by seconds or minutes.

Prefetch

The prefetch mechanism, fetches ads from the ad decision server and prepares them for upcoming ad breaks. Ad prefetching helps to maximize ad fill rates and monetization in live workflows that use SCTE-35 markers, where ad request and transcoding timeouts can occur. Ad prefetching provides more time for programmatic ad trading.

The prefetch includes the following settings:

  1. Number of Ad Slots - defines how many ad slots to prefetch. The exact number is based on the number of ad slots in a pod.

  2. Number of Minutes - for how long the prefetched ads are saved before releasing them if not served. The default value is 15 minutes.

  3. Number of Retrieve Requests - if from some reason ads weren't prefetch, the system will continue and try prefetching based on the number of retrieve requests. The default value is 3.

Ad Position

Ad positioning is divided into two sections:

  1. Pre-Roll - refers to ad breaks at the beginning of the stream.

  2. Mid-Roll - refers to ad breaks in the middle of the stream.

Each section is separated by a tab, all ad positions settings are related to the specific tab.

Slot

  1. Min Duration - set the minimum slot duration (Sec), when 0 is the minimum value.

  2. Max Duration - set the maximum slot duration (Sec). The minimum value of max duration can be unrestricted, meaning, that the system will supply slots of any existing durations according to the needs.

Pod

  1. Number of Ad Slots - gives the option to set the exact number of ad slots in a pod. The minimum value can be unrestricted, meaning, that the system fills the pod according to the available slots served by the ad server, without restrictions.

  2. Pre Roll Pod Duration - this option is available only in the pre roll tab. Since pod duration is derived from the markers and pre roll isn't defined by markers, the user has the option to define the duration of the pod, which will be played before the stream starts.

Deduplication

Deduplication, makes sure that the same ad wont be played twice in the same pod based on few criteria's.

  1. Creative ID - same ad with creative id wont be played twice in the same pod.

  2. Creative Media File - ad with the same creative media wont be played twice in the same pod.

  3. IAB Category - an industry standards that are heavily used in advertising services.

  4. Advertiser domain - ads coming from the same advertise domain wont be played in the same pod.