AWS details critical feature gaps between MediaTailor SSAI and SGAI
Amazon Web Services (AWS) has published a compatibility matrix detailing the differences between MediaTailor's server-side ad insertion (SSAI) and server-guided ad insertion (SGAI) features. The comparison clarifies how ad prefetching, suppression, tracking, and Ad-ID decoration work with each method, providing guidance for streaming professionals. This technical documentation helps users understand the implications of choosing between SSAI and SGAI for their ad insertion strategies.
Key Takeaways
- SGAI does not support ad prefetching or ad suppression because players only fetch intended ads
- Server-side tracking for SGAI is limited to HLS v11+ and uses sessionless beaconing via EXT-X-DEFINE:QUERYPARAM
- Ad-ID decoration is incompatible with SGAI due to metadata timing constraints at the manifest-writing stage
- Client-side tracking for SGAI bypasses the GetTracking API, instead delivering data via the asset list TRACKING section
Why It Matters
The technical limitations of SGAI, particularly the lack of DASH support and Ad-ID decoration, force architectural trade-offs for engineers seeking the lower latency of server-guided models. While SSAI remains the more mature, feature-complete option for high-volume cross-platform monetization, SGAI represents the industry's shift toward shifting manifest manipulation logic toward the edge. This compatibility matrix serves as a roadmap for CTOs deciding between reliable legacy SSAI and the performance-centric SGAI. We are watching for the release of MediaTailor SGAI support for DASH and ad prefetching to signal SGAI's readiness for mainstream, multi-platform deployment.
Additional Context
The push toward SGAI reflects a broader industry effort to resolve the 'SSAIs vs. CSAI' debate by combining the reliability of server-side logic with the reporting accuracy of client-side tracking. Per a December 2025 report from Streaming Media, low-latency HLS requirements and the phasing out of third-party cookies have accelerated the adoption of server-guided architectures. By providing a structured asset list rather than a fully stitched manifest, SGAI reduces the processing load on the CDN edge while maintaining better control over client-side event firing. This aligns with the HLS Interstitials specification, which Apple has continued to iterate upon to reduce the playback 'black screen' during ad transitions. Competitively, AWS is reacting to advancements from Google Ad Manager and SeaChange, which have prioritized hybrid insertion models to combat ad blockers. Per TechCrunch in February 2026, industry-wide ad-blocking losses for premium VOD services reached approximately $1.2B annually, prompting a shift away from easily identifiable client-side ad calls. Meanwhile, the Video Advertising Bureau (VAB) noted in April 2026 that 68% of streaming buyers now require Ad-ID transparency for cross-platform measurement. The current lack of Ad-ID decoration in AWS's SGAI implementation may therefore present a hurdles for buyers focused on standardized metadata, potentially slowing SGAI adoption among major broadcasters until parity with SSAI is achieved.
Read full article at docs.aws.amazon.com
Get this in your inbox → Subscribe
Enjoy our coverage?
Add StreamingMeme as a preferred source on Google to see more of our streaming news at the top of your Search results.
Add as preferred source