Frequently Asked Questions (FAQ)
Using server side ad insertion will push your streaming business to a new level with regard to user experience and monetization possibilities.
To get a feeling if SERVERSIDE.AI is for you, we provide you with an overview of our most frequently asked questions and their respective answers.
If you stumble upon a missing information, our support team will be happy to help you out - just get in touch via our contact form!
Question Overview
What is Server Side Ad Insertion (SSAI)?
Who is using SSAI?
What device types support SSAI?
What streaming formats and DRM schemes are supported?
How do you do the ad targeting?
How do you do ad-tracking, reporting, ad-verification and measurement? Does your solution support Client-side tracking?
Does your solution handle high traffic volumes?
Do you perform transcoding of the ad assets?
Do you support MPEG-DASH for live streaming as well?
What if I don't have SCTE35 ad-marker in-band in my live source?
Our live content is highly dynamic, can your solution cope with this?
Do we have to replace our current VOD encoding workflow to support server-side ad insertion?
We want frame-accurate insertion, but our current encoding workflow cannot support this. What can we do?
Does your solution support MRSS for VOD insertion?
1. What is Server Side Ad Insertion (SSAI)?
It’s a process used to insert ads into a piece of long form content. It allows for a buffer-less transition from content, to ad, then back to content in an OTT streaming environment, providing the same user experience as broadcast TV. This process is managed by Nowtilus as a SSAI vendor. We „sit“ between the Online Video Player, Content Origin and Ad Server to mediate the stitching of the ads into the content. By doing so we enable personalization of each single stream containing precisely targeted ads.
2. Who is using SSAI?
SSAI is used by broadcast-quality media owners. This includes media owners that stream live events, stream live-linear cable TV, and have Video On Demand (VOD). This content is typically high quality and long form.
3. What device types support SSAI?
SSAI content can be accessed across all devices in both web or app environments. This means users can stream SSAI content on desktop, mobile, and connected TV devices.
4. What streaming formats and DRM schemes are supported?
We support HLS and MPEG-DASH for both Live and VOD content. Because this is primarily concerned with the server-side manipulation of manifest files, it is largely agnostic to DRM systems, which are usually concerned with protection of the content segments. Our customers operate with either full "studio grade" DRM (Playready, Widevine, Faiplay) or encrypted HLS.
5. How do you do the ad targeting?
Our solution leverages your existing ad server and audience tracking solutions to perform the user targeting. We are pre-integrated with ad-servers and SSP platforms such as Google AdManager and SpotX. In general, VAST 3.0 and 4.0 compliant ad platforms are supported. A wide range of configuration options make integration and validation really straightforward.
6. How do you do ad-tracking, reporting, ad-verification and measurement? Does your solution support Client-side tracking?
We support ad-tracking and reporting from server-side with tracking beacons as a response back to the ad-serving / SSP platform once stitched into the personalized stream. At the same time, we can insert tracking metadata into the stream manifests for client-side ad-tracking from the player.
As a roadmap item and if supported by your ad-serving partner we are going to support VAST 4.0 ad-verification tags for measurement and brand safety. In addition for Client-side tracking we’ll support Open Measurement SDK and Library of the IAB, as a replacement for former VPAID implementations.
7. Does your solution handle high traffic volumes?
Yes, we handle that. Our SSAI platform service is cloud-native and scales on request. It can be geographically deployed and distributed in all regions of Microsoft Azure cloud. It is specifically designed to support the large audiences that are associated with live sport and event television. It is designed to work alongside your existing single or multi-CDN strategy for the delivery of the content source video data to end users.
8. Do you perform transcoding of the ad assets?
Ad transcoding is a core function of our solution. By normalizing ad content we can not only better guarantee the user experience from a qualitative perspective (such as audio level normalization), but it also guarantees stream integrity -- ensuring that an ad cannot "break" a user's streaming experience. Ad transcoding is processed with Azure Media Services, although we have an ad-asset-management to allow pre-loading of ad assets as part of the ad trafficking process by your ad operations teams.
9. Do you support MPEG-DASH for live streaming as well?
Yes, we do. However please bear in mind that many packager vendors have yet to support SCTE-35 signaling for live MPEG-DASH, so you should check with your packager vendor for their support and roadmap. If you are packager vendor and would like guidance on how to implement SCTE-35 signaling support within your product, please speak with us. If required we can also support you with setting up a cloud-based live encoding and packaging workflow enabled for SSAI.
10. What if I don't have SCTE35 ad-marker in-band in my live source?
For source signals that don’t already have in-band SCTE-35 signaling identifying ad breaks, we provide a third party software component, that provides automated ad-recognition and signaling of ad-breaks. Besides it can integrate with broadcaster live playout automation to determine program and ad breaks, which are then injected into the stream for onward processing by your encoding workflow.
11. Our live content is highly dynamic, can your solution cope with this?
Our solution is designed for highly dynamic ad break patterns. Unscheduled breaks, early or crashed returns into content are supported as long as signaled in you source feeds.
12. Do we have to replace our current VOD encoding workflow to support server-side ad insertion?
We require that you have encoded your VOD catalogue in either HLS or MPEG-DASH – how you achieve that is entirely up to you. To achieve frame-accurate ad insertion, your VOD encoding should ensure that segment boundaries coincide with the known insertion points.
13. We want frame-accurate insertion, but our current encoding workflow cannot support this. What can we do?
We support acquisition and encoding of VOD titles as part of the solution which includes frame-accurate segment conditioning.
14. Does your solution support MRSS for VOD insertion?
Yes, and this is our recommended approach. We do however support single pod VAST responses in combination with a "placement template" that you define.
