What is it and what it can do?
The Teads CTV SDK is built in Typescript and it can deliver these types of ad experiences:
- InPlay: the ads are delivered during the video content playout;
- InPause: the ads are delivered when the end-user pauses the video content.
- InStream: the ads are delivered during linear ad-breaks in the video content (on preroll, midroll and postroll ad breaks).
All these ad formats can be delivered with or without user-interactivity by remote-control.
Where can it work?
The SDK can be integrated on any VOD or streaming applications that run on internet-connected devices like CTVs, Set-Top-Boxes or other similar devices.
The current available SDK is meant for web-based (HTML5) applications that run in various browser engines or that run in any native OS webview components.
As supported platforms:
- it is compatible with apps running on: Samsung Tizen, LG webOS, Hisense VIDAA, Vizio, WhaleTV, TiVo OS, Foxxum, etc.
- it may be compatible with Android-based and other native OS apps and this depends on the native apps use of a webview for their execution or if there is built a simple native Android bridge for webview SDK API interface: Android TV, Google TV, (Amazon) Fire TV, PlayStation, Xbox, etc.
- it is NOT compatible with apps built on: Roku, Apple TV.
What types of integrations are possible?
The CTV SDK can be integrated within the application as:
- CSAI: (see the implementation details here)
- InPlay ads: the application controls the ad-breaks for the frequency and the duration of the ad-break
- InPause ads: are initiated by the end-user of the application and the application intercepts these events and initializes the SDK requesting an InPause ad
- InStream ads: the application controls the ad-breaks for the frequency and the duration of the ad-break
- SGAI: (implementation not fully described in the documentation - see here)
- InPlay and InStream ads: the content stream controls the ad-break opportunities and their duration via the SCTE35 ad-marker signals specific for in-content ads; the SDK supports now only AWS Mediatailor streams and in-content ad-markers read-out; for other SSAI providers it can be added support, please reach out to our team for a technical discussion
- InPause ads: this is only possible as a CSAI integration due to the end-user interaction as the trigger event, see above
What InPlay ad experiences formats can be delivered?
There are 3 main formats:
- Overlay: the visual assets cover partially, on the sides, the video content player
- Squeeze-backs: the video content player is being resized and repositioned and the ad experience visual assets are shown around it
- Picture-in-Picture: similar to squeeze-back, with also a video ad being played, along with the video content and the other visual branded images.
See the demos here.
What InPause ad experiences formats can be delivered?
As InPause formats:
- Fullscreen: light-animated or static images that are shown and executed continuously for the entire duration of the content pause
- soon new formats will be added (OnScreen: part-of-screen coverage, customizable)
See the demos here.
What InStream ad experiences formats can be delivered?
As InStream formats: standard linear ad (without interactivity) or advanced formats supporting user interactivity with the remote-control executed in a pre-, mid- or post-roll content ad break.
- Fullscreen: a linear video ad.
- Fullscreen interactive: a skinned video ad along light-animated or static images with or without an interactive capability (by remote-control or QR code)
See the demos here.
In what consists an ad experience?
All the formats allow for each visual asset to set up their own animation, position and timeline execution details.
Besides the described formats, the Teads CTV SDK allows designs and implementation of very custom ad experiences and behaviors.
User interactivity is possible?
Yes - via the remote-control keys and QR codes.
A very important feature of the CTV SDK ad experiences is the capability to have end-user interactivity via the device remote-control keys: the 4 directional keys and the OK/Return key allow actions to be performed from the end-user.