SSAI Architecture Explained: Server-Side Ad Insertion for AVOD & FAST

Advertising-supported streaming has changed how OTT businesses monetize video. AVOD platforms can offer content at no subscription cost, while FAST services can deliver scheduled channels without requiring viewers to pay for access.

But inserting advertising into an internet video stream is more complicated than placing an ad between two pieces of content.

The platform has to identify an advertising opportunity, select suitable inventory, make the ad compatible with the stream, deliver it at the right moment, and measure the result without disrupting playback.

Server-Side Ad Insertion (SSAI) addresses this challenge by moving the ad insertion process into the streaming infrastructure.

Instead of relying primarily on the viewer's device to request and insert an advertisement, the server prepares a stream that includes the appropriate advertising segments.

For AVOD, this enables dynamic advertising within on-demand content. For FAST, it enables personalized advertising within continuous linear channels.

Server-Side Ad Insertion is a technology that integrates advertisements into a video stream before or during delivery to the viewer.

A simplified SSAI request flow is:

Viewer request → SSAI service → Ad decisioning → Personalized stream → CDN → Player

The player receives a stream containing both programming and advertising.

This differs from Client-Side Ad Insertion (CSAI), where the player is responsible for requesting ads and managing the transition between content and advertisements.

The server-side approach can create a more consistent experience across devices because the core insertion logic is handled within the streaming infrastructure.

SSAI is not a single technology component. It connects several systems.

The content origin provides the video assets, while encoding and packaging systems prepare them for streaming through formats such as HLS or MPEG-DASH.

For VOD, this could include movies, episodes, or documentaries. For FAST, the system may provide a continuous channel feed.

The SSAI layer handles the advertising workflow. It identifies available ad opportunities, communicates with advertising systems, and creates the appropriate playback manifest or stream.

The Ad Decision Server determines which advertising should fill an available opportunity. Selection can consider factors such as geography, audience, device, campaign rules, inventory, and the available break duration.

The Content Delivery Network distributes the resulting stream and media segments to viewers. CDN performance becomes especially important for FAST channels with large concurrent audiences.

The player receives the final stream and handles playback. Because the advertising has been integrated into the server-side workflow, the player does not need to perform the entire insertion process itself.

Streaming video is delivered as a sequence of media segments described by a manifest.

A normal content sequence might contain several content segments in order.

During an advertising opportunity, the SSAI service can modify the playback path so that advertising segments are delivered between content segments.

For example:

Content → Content → Ad → Ad → Content → Content

The viewer experiences this as a normal commercial break.

The important part is that the underlying stream can be different for different viewers.

One person may receive an automotive advertisement, while another viewer watching the same program receives a telecom advertisement.

This makes personalized advertising possible without requiring every viewer to watch the same commercial.

For live and linear streaming, the system needs a reliable way to identify when an advertising opportunity occurs.

SCTE-35 is commonly used to signal splice points and advertising opportunities in live video workflows.

This is particularly important for FAST.

A FAST channel is continuously playing. The SSAI system cannot simply insert an advertisement whenever it chooses. It needs to know when the programming allows an advertising break and how much time is available.

Accurate signaling helps the platform maintain:

• Correct ad break timing

• Program continuity

• Appropriate break duration

• Smooth transitions between content and advertising

Poor signaling can lead to problems such as early ad insertion, late breaks, missing advertising, or incorrect program transitions.

AVOD gives viewers access to on-demand content supported by advertising.

The advertising opportunities can be positioned around the content depending on the platform's monetization strategy.

A pre-roll advertisement plays before the main content begins.

This is relatively straightforward because the platform knows the viewer is starting a new asset.

Mid-roll advertising appears during the content.

Long-form movies, episodes, and other programs may contain multiple advertising opportunities.

The placement needs to avoid disrupting important scenes or creating an unnatural viewing experience.

Post-roll advertising appears after the content finishes.

It can provide another monetization opportunity, although fewer viewers may remain until the end.

A single break can contain multiple advertisements. The SSAI system needs to make sure the selected ads fit within the available commercial window.

FAST operates differently from traditional VOD.

Instead of selecting a specific title, the viewer joins a continuously running channel.

A simplified FAST architecture includes the content library, channel scheduling and playout, ad signaling, SSAI, advertising decisioning, CDN delivery, and the player.

The key challenge is maintaining linear continuity while allowing advertising to be personalized.

For example, 50,000 viewers can be watching the same FAST channel at the same time. The programming remains identical, but their advertising can differ based on the inventory available for each session.

That gives FAST operators some of the targeting flexibility associated with digital advertising while retaining the familiar structure of linear television.

The ad decisioning process can evaluate several factors before selecting inventory.

These may include:

• Viewer location

• Audience segment

• Device type

• Campaign requirements

• Frequency limits

• Available inventory

• Ad duration

• Content context

• Commercial value

The SSAI layer then integrates the selected advertisement into the viewer's stream.

This separation is useful because the advertising system can focus on which ad should be served, while the SSAI system focuses on how that ad should be delivered within the stream.

A production SSAI system needs a fallback strategy.

Advertising inventory is not guaranteed to fill every opportunity.

Depending on the platform, an unfilled break might use:

• House advertising

• Promotional content

• Slate

• Filler content

• A shortened break

Without an appropriate fallback, viewers could encounter black frames, gaps, or awkward transitions.

For FAST services, this is particularly important because the channel needs to maintain a continuous viewing experience.

Serving an advertisement is only one part of the monetization process.

The platform also needs to know whether the advertisement actually played.

Tracking can cover events such as:

• Ad request

• Ad start

• 25% completion

• 50% completion

• 75% completion

• Full completion

• Playback error

SSAI environments may combine server-side and client-side measurement depending on the advertising requirements.

Accurate measurement matters because advertisers need reliable evidence that campaigns were delivered, while publishers need accurate data for revenue reporting and optimization.

The main architectural difference is where the insertion process happens.

Neither approach is universally better.

For businesses operating large AVOD libraries or FAST channels, SSAI can be particularly useful when consistency, scalability, and server-controlled delivery are priorities.

SSAI can simplify the viewer experience, but the backend architecture needs careful planning.

Common challenges include:

• Ad decision latency: Slow ad responses can affect playback.

• Duration mismatch: Selected advertising may not fit the available break.

• Media incompatibility: Different codecs, resolutions, frame rates, or audio formats can create playback problems.

• Incorrect ad signaling: Poor SCTE-35 implementation can cause inaccurate insertion points.

• Tracking discrepancies: Different measurement systems may report different results if event handling is not aligned.

• Scalability: Large FAST audiences can create significant manifest, ad decision, and delivery traffic.

These issues make monitoring an important part of a production SSAI deployment.

SSAI should not be treated as an isolated advertising feature.

A successful advertising-supported streaming service needs a connected workflow covering content management, encoding, packaging, advertising, delivery, playback, analytics, and monetization.

This is particularly important when an OTT business operates multiple monetization models.

A platform might offer:

• SVOD subscriptions

• AVOD content

• FAST channels

• Premium rentals

• Hybrid plans

An integrated OTT infrastructure makes it easier to manage these experiences without creating completely separate technology stacks.

Vodlix provides an OTT platform for businesses launching and managing branded streaming services, with capabilities covering content management, streaming, monetization, analytics, and applications.

For businesses exploring AVOD, FAST, or hybrid monetization, having the wider OTT infrastructure in place is important because advertising needs to work alongside the content catalog, viewer experience, applications, and analytics.

The goal is not simply to insert an advertisement.

It is to create a streaming service where monetization can scale without compromising the viewing experience.

SSAI is a core technology for modern advertising-supported streaming.

For AVOD, it enables advertisements to be dynamically integrated into on-demand content.

For FAST, it allows continuous linear channels to deliver personalized advertising while maintaining scheduled programming.

Behind the scenes, SSAI connects content packaging, ad signaling, ad decisioning, manifest generation, CDN delivery, playback, and measurement.

The architecture needs to handle more than simply choosing an advertisement. It must also account for break duration, media compatibility, fallback behavior, tracking, latency, and scale.

When these components are designed correctly, advertising becomes part of the streaming workflow rather than a disruptive experience.

For OTT businesses building AVOD or FAST services, the right SSAI architecture can provide the foundation for reliable ad delivery, personalized monetization, and scalable streaming.

Ready to build an advertising-supported OTT service? Explore Vodlix to launch and manage your branded streaming platform with flexible monetization options.