Introduction

The Server-Guided-Ad-Insertion (SGAI) integration of the Teads CTV SDK relies on the video content stream SCTE35 ad-marker signals for in-content ads (0x038)  as the trigger events to insert and execute an ad experience for InPlay.

The SCTE ad-marker readout depends on the stream provider and the player consuming it - that means that the readout of these has to be done specifically for each such case.

Currently the Teads SDK supports the AWS MediaTailor SCTE35 ad-marker signals read out.

For any other case, the CTV SDK can be technically adapted to read these ad-marker signals. For this case is needed to reach us through your Teads contact and provide us the technical details of your content stream setup.

The SGAI integration allows the delivery of the InPlay ad experiences but not of the InPause ad experiences because pause-ads are initiated by the end-user activity (pausing the content) and are not part of the content stream signals. For InPause ad experiences it has to be used the CSAI implementation of the SDK.

Workflow

The CTV application has to integrate the Teads CTV SDK.

The content stream SCTE35 ad-markers are being read by the Teads CTV SDK and these will trigger the SDK to fetch the ad and start the execution at the given moment and for the given duration in the content stream.

The CTV application will get all the events in the lifecycle of the ad execution but it will not be the one controlling the trigger event - as this is accomplished by the stream carrying the ad-marker signals.

The CTV application will still be able to block the ad or stop it while it is executing, similar as for the CSAI implementation.

Integration

wip - will be available soon