This guide will walk you through the integration process using one of the three available variants, focusing on the involved components and their interactions.

Involved Components

1. Playout: Manages the content stream and incorporates ads as per the defined logic into the manifests.
2. SSAI (Server-Side Ad Insertion): Inserts ads into the stream based on SCTE ad break markers.
3. RapidStream: Handles ad requests and provides VAST (Video Ad Serving Template) responses.
4. Ad Server: Supplies the ads that are eventually played during ad breaks.

Variant 1: Adaptive Ad Break Insertion

Context

In this variant, the content schedule comprises a continuous list of Video On Demand (VOD) segments without predefined ad breaks. The Playout system dynamically determines when to insert ads, enhancing the user experience by ensuring ads are placed at optimal points in the stream.

Integration Flow

1. Ad Request from Playout: Playout asynchronously requests ads from RapidStream based on its domain logic.
2. Ad Break Marker Insertion: Upon receiving a response from RapidStream, the Playout inserts an ad break marker into the stream. This marker includes an ad break ID within the EXT-X-ASSET tag.
3. SSAI Requests VAST: When the stream reaches the ad break, SSAI forwards the ad break ID to RapidStream, requesting the VAST for that particular ad break.
4. Ad Insertion: RapidStream returns the VAST, and SSAI inserts the ads into the stream.

Pros

• Flexible Ad Breaks: Ads are only inserted when available, ensuring viewers do not encounter empty ad slots or see ad slates.
• Enhanced Viewer Engagement: Viewers first see content, creating a more engaging experience before ads appear increasing user stickiness.
• Ease of Program Planning: Simplifies the scheduling process as precise ad break timing is not required.
• Minimal SSAI Configuration: Only standard SCTE marker configuration is needed.

Cons

• Complex Playout Integration: Requires significant work to integrate ad logic within the Playout system.
• Higher Computing Resources: Individual ad sessions increase the demand on computing resources.
• Session Variability: Content and Electronic Program Guide (EPG) can vary per user session.
• Caching Challenges: Individual manifests per user complicate caching strategies.

Variant 2: Scheduled Ad Break Insertion

Context

This variant uses a fixed schedule with predefined ad breaks. The schedule might include fallback ads or slates to ensure ads are played even if personalized ads are not available.

Integration Flow

1. Ad Markers in Stream: The Playout includes ad markers with metadata in the stream. Metadata can be user IDs, EPG IDs, or other relevant information.
2. Synchronous Ad Requests: SSAI makes a synchronous call to RapidStream, expecting a quick VAST response.
3. Fallback Handling: If no personalized ads are available, fallback ads from the schedule are streamed.

Pros

• Simple Integration: Requires minimal integration work in the Playout and SSAI.
• Straightforward Configuration: Easy to set up and configure.
• Consistent EPG: Maintains a straightforward and predictable EPG.
• Efficient Caching: Non-ad manifests can be cached, reducing costs.

Cons

• Fallback Ads: Viewers might see less relevant fallback ads, reducing revenue potential.
• Initial Ads: Users may encounter ads immediately upon switching to the channel.
• Precise Scheduling Required: Content managers must meticulously plan the schedule.
• Potential Scalability Issues: Sudden bursts of ad requests can cause scalability challenges.

Variant 3: Prefetched Ad Break Insertion

Context

This variant is designed for events with high viewership, such as sports matches, where sudden bursts of ad requests are common.

Integration Flow

1. Schedule-Based Prefetching: The fixed schedule is provided to RapidStream. Ten minutes before an ad break, RapidStream initiates a prefetch call to SSAI.
2. User Session Tracking: SSAI responds with active user sessions, and RapidStream requests VAST for these sessions.
3. Ad Insertion: At the ad break, SSAI retrieves ads for active sessions from the prefetch call. New user sessions are handled via synchronous requests (see variant 2).

Pros

• Scalability: Handles high user loads efficiently.
• Smooth Integration: Minimal integration work required for the Playout.
• Reliable Ad Delivery: Ensures ads are pre-fetched and ready for insertion.

Cons

• Complex SSAI Integration: Requires SSAI to manage user sessions and provide an API for prefetch calls.
• Not Compatible with Standard SSAI Services: Custom integration work is necessary, which is not feasible with standard SSAI solutions like AWS Media Tailor.

Conclusion

Integrating RapidStream into your streaming system can be tailored to your specific needs using one of these three variants. Adaptive Ad Break Insertion offers a dynamic and user-friendly approach, Scheduled Ad Break Insertion provides simplicity and efficiency, and Prefetched Ad Break Insertion addresses scalability for large events. Choose the variant that best aligns with your operational requirements and viewer engagement goals.

If you require further information or help, feel free to contact us, we’re happy to help.