Key takeaways
- The ad is part of the video file, not a separate request from the player.
- Reduces the risk of ad blockers and client-side errors.
- Simplifies analytics because the server logs the exact ad served.
- Requires a capable ad server and compatible player support.
How SSAI works
In a standard video delivery setup, the player requests a video stream. With SSAI, the request also includes ad parameters. The ad server checks the viewer's profile and context, selects the appropriate ad, and stitches it into the video stream at the designated cue points. The player receives a single, continuous media file. It does not know an ad is present; it just plays the stream.
This process happens on the server side. The client player remains simple. It does not need to handle complex ad logic, VAST parsing, or timing adjustments. The server handles the heavy lifting of selecting and inserting the creative. This separation of concerns keeps the player lightweight and consistent across devices.
- Request: Player asks for video with ad parameters.
- Selection: Ad server picks the right creative based on rules.
- Stitching: Server combines video and ad into one stream.
- Delivery: Player receives and plays the combined stream.
Why SSAI matters for a streaming business
SSAI solves two major problems for operators: ad blocking and data accuracy. Because the ad is embedded in the video file, standard ad blockers that intercept network requests often fail to detect it. This protects your ad revenue from being stripped out before the viewer sees it.
Data accuracy is the second benefit. When the player handles ads, you rely on client-side reports to know if an ad played. These reports can be lost or inaccurate. With SSAI, the server logs every ad impression. You know exactly which ad was served to which viewer, at what time, and on which device. This clean data is essential for proving value to advertisers and optimizing your inventory.
For FAST channels, SSAI is often the default approach. It allows you to serve different ads to different viewers within the same live stream without changing the player code. It keeps the viewing experience smooth and the revenue stream reliable. If you are building an ad-supported platform, SSAI reduces the technical debt associated with client-side ad management.
SSAI vs CSAI
SSAI and CSAI (Client-Side Ad Insertion) are two ways to deliver ads. The core difference is where the ad is stitched into the video.
In CSAI, the player receives a video stream with ad markers. The player then makes a separate request to the ad server for the creative. It stitches the ad locally. This method is older and more complex for the player to handle.
In SSAI, the server stitches the ad into the stream. The player just plays the file. This is simpler for the client and more secure for the operator.
| Feature | SSAI | CSAI |
|---|---|---|
| Ad Stitching Location | Server | Player |
| Ad Blocker Risk | Lower | Higher |
| Player Complexity | Low | High |
| Data Accuracy | High (Server logs) | Variable (Client reports) |
| Implementation Effort | Higher (Server setup) | Lower (Player logic) |
Common mistakes with SSAI
Operators often make a few key errors when implementing SSAI:
- Ignoring Cue Points: If your SCTE-35 markers are misaligned with the video content, ads will appear at awkward moments. Test your cue points thoroughly.
- Overlooking Latency: SSAI adds a step to the delivery chain. If your ad server is slow, it can increase initial load times. Monitor your server response times.
- Assuming All Players Support It: Not all players handle SSAI streams the same way. Test on all your target devices, including smart TVs and mobile apps.
- Neglecting Fallbacks: If the ad server fails, you need a plan. Make sure your system can serve the video without ads if the ad request times out.
How Flicknexs handles SSAI
Flicknexs includes SSAI as a core capability. The platform stitches ads into the video stream on the server side, keeping your viewers see the ad as part of the content. This setup works with your existing ad server integrations. You can manage ad rules and targeting through the platform's advertising tools. The player receives a clean stream, reducing the burden on client-side code. This approach supports your FAST channels and on-demand content with consistent ad delivery. It helps you protect revenue from ad blockers and provides accurate impression data for your reports. For details on setting up ad-supported channels, see Launch a FAST channel.
Done reading about SSAI?
Flicknexs ships it as part of a white-label streaming platform: web, mobile and TV apps, billing, ads, DRM and playout, on your own domain.