Server-Side Ad Insertion (SSAI) for OTT Streaming

Server-side ad insertion (SSAI) puts the ad into the video stream on a server, before the stream reaches the viewer. The viewer's device receives one continuous stream instead of a programme plus a separate ad call. That matters on TVs, set-top boxes and players, where ad blockers, autoplay rules and slow ad software often stop ads from playing. Vodlix connects your videos and live channels to Publica or Aniview for SSAI. It also adds 39 built-in targeting macros to every ad request, so buyers know the device, the viewer's consent and the title being watched. For AVOD and FAST broadcasters, that is the difference between an ad break that plays and one that pays.

With server-side ad insertion, viewers watch ads the same way they watch the programme: inside one stream. The ad is already part of the video when it arrives, so the player does not have to fetch and start a separate ad in the middle of playback. That is why SSAI suits living-room screens and FAST channels, where a failed ad call means a black screen and lost revenue. It works for on-demand titles and for live channels. On a live channel, the ad breaks follow the cue markers that are already in the live stream.

Vodlix supports two SSAI partners, Publica and Aniview, and each one is a single switch in your settings.

Publica. Publica puts ads into the stream on its own servers. You add the network and stream IDs Publica gives you, one set for on-demand and one for live. Then you choose how long an ad break is, the shortest and longest ad allowed, whether on-demand titles start with an ad, and where the mid-roll breaks fall. A title only shows Publica ads once you switch them on for it, and any title can use its own IDs, pre-roll choice and break times.

Aniview. Aniview builds the stream addresses for you with its ad macros already added. Enter your Aniview publisher ID and, if you like, add the platform's own macros too. Macros that are already there are not added twice.

For titles that play ads in the player instead, you choose the ad engine: Google IMA by default, or the Vodlix VAST engine, which plays ads without the IMA software and gets round browser autoplay limits.

Macros tell buyers who is watching what, so your ads sell for more. Switch them on and Vodlix adds the macros you pick to every video address, on demand and live. There are 39 macros in five groups.

Session and network. Session ID, IP address, cache buster and timestamp.

Device and app. Device type, operating system, make, name, model and device ID, screen width and height, user agent, app name, app bundle ID and app platform.

Privacy and consent. Advertising ID and its type, limit ad tracking, the GDPR and CCPA flags and the US privacy string, so ad partners can respect each viewer's choices.

Content. Content ID, creator ID, title, category, genre, duration, language, rating, live or on demand, and series ID. The rating can be the one stored on the title or the resolved one, where an episode takes its series rating and maturity defaults.

Geo and URL. Latitude, longitude, page URL, network and app store URL.

Every ad server names these values differently, so you can rename each one to match yours. Select All and Clear set the whole list in one click.

You can publish ads.txt and app-ads.txt without a developer. Ad buyers check ads.txt before they bid on a website, and app-ads.txt before they bid on connected TV and mobile apps. Vodlix keeps both files in your Marketing settings. Paste in the lines your ad partners give you and the platform serves them at the root of your domain, as /ads.txt and /app-ads.txt. When a new seller joins, your ad team can add it the same day, with no release needed. These small files decide whether buyers may bid on your inventory at all. They sit alongside the other revenue options in OTT monetization models.