Skip to content

SSAI Overview โ€‹

Updated

Server-Side Ad Insertion. This method attaches ads to the main content stream on the server side, so that from the player's perspective the ads and the main content look like one continuous stream.

Request Example โ€‹

In client-side ad insertion (CSAI), the player pauses the main content, separately fetches and plays the ad video, and returns to the main content when it finishes. The player moves back and forth between two streams.

With SSAI, the player sees only one stream. When it reaches an ad break, the server swaps the segments of that period with ad segments and sends them.

Difference in where ads are joined

Key Features โ€‹

ItemCSAISSAI
Ad blocking (ad blocker)EffectiveNot effective
Interruption between ads and main contentYesโ€”
Player requirementsAd SDK requiredโ€”
Measurement accuracyClient-dependentServer-based
Implementation difficultyLowHigh

Because the ads and the main content are delivered in the same stream, the player handles them as a single playback flow.

Signal Flow โ€‹

Ad insertion processing flow

Components โ€‹

ElementRole
SCTE-35 markerSignals the start and length of the ad break
PDTRecords absolute time in segments to align exactly with the marker
ADSDecides which ads to insert. VAST response
Slate AdDefault video that fills the gap when no ad is filled
ThresholdHow many seconds at most to wait when no ad is filled

Where SSAI Is Attached in Tencent Cloud โ€‹

SSAI is enabled per StreamPackage endpoint. It is the endpoint, not the channel. So you can serve the SSAI version and the regular version from the same channel at the same time.

Main content source and two playback paths

Prerequisites โ€‹

  • An encoder or injection system that can insert SCTE-35 markers
  • An ADS that responds with VAST
  • MP4 for the slate ad
  • StreamPackage endpoint
  • CSS playback domain

Next Steps โ€‹

Built with VitePress ยท Deployed on Tencent EdgeOne Pages