Server side ad insertion is a modern streaming technique that minimizes buffering times and helps with avoiding lost ad inventory to client-side ad blockers.
This is accomplished by leveraging popular adaptive streaming protocols like HLS or DASH, creating a unified streaming manifest that contains both ad as well as main content.
When a request for a SSAI enabled streaming URL is made, our backend systems will ping pre-configured VAST ad servers and a manifest is generated on the fly, leveraging all available targeting data. This ensures that only the most relevant ads are still delivered to users.
Whenever new ad creatives are returned by the downstream ad servers, these ads are transcoded on the fly so that they match the variants of the original content.
Since ads are now part of the video stream, video players need additional feedback in order to determine whether an ad is currently rendered, and adapt the UI accordingly. Veeplay 3.x player SDKs for HTML, Android, and iOS support client-side reporting out of the box. The SDKs will handle all ad tracking and overlays on the client-side automatically.
See the ad behavior docs for more info.
Our backend can also automatically process ad-server tracking server-side, according to the VAST standard, making this integration scenario essentially a drop-in replacement.
In order to be able to use existing content sources with SSAI, incoming content needs to follow a set of requirements:
HLS(Apple HTTP Live Streaming) or in
DASH(MPEG Dynamic Adaptive Streaming over HTTP);
Is live content, or video-on-demand (VOD);
Is accessible on the public internet and has a public IP address;
Contains ad markers to delineate ad breaks in the content.
Learn how Veeplay handles multiple audio and subtitle streams.
In order to know where inside the stream ads should be injected, the system relies on either
SCTE-35 markers or
VMAP 1.0 responses from the downstream ad-server. If neither are provided, the ads will be injected as pre-rolls at the beginning of the stream.
Veeplay also provides a pipeline that helps with transcoding your content (streams/ad responses), or allows for different ways of accessing the SSAI processor. Please contact your Veeplay representative to learn more.
Read more on creating a configuration.
Once your content is formatted in a compatible playlist the SSAI streaming URLs can be generated.
In order to do this, navigate to
https://panel.veeplay.com and login using your Veeplay credentials. All SSAI settings are grouped inside the
SSAI tab on the main menu.
Fill in the following inputs:
VAST URL- this is the endpoint that will be polled whenever the stream is requested. Our backend will expect that the response at this URL will either be a VAST tag, or a VMAP tag in case you're looking to use VMAP in order to schedule ad breaks.
HLS or DASH content URL- this is the base URL of your CDN where HLS or DASH manifests are stored. Do not point directly to one of your manifests, just to the folder where these are stored. The name of the manifest should be appended to the generated links.
Slate MP4 URL- this is an optional MP4 slate that is used to fill gaps in media content. See slate management for more info.
Read the full specs on using VAST, VMAP and VPAID.
Learn how to send variables to the ad server.
Save, a set of 2 base URLs will be generated. You can append the name of any manifest available at the original URL in order to get links to specific streams on your CDN.
- a server side only HLS endpoint, usable with any HLS enabled player
- a server side only DASH endpoint, usable with any DASH enabled player
Read more about monitoring your streams.
Configuring the front-end libraries to work with SSAI URLs only entails specifying a unit manager when defining the main content. Snippets for programatic as well as JSON configuration methods are outlined below. See the ad tracking docs for more info.