The IMA SDK should always be used for major platforms. Where not available, the DAI APIoffers similar functionality with client triggered ad metric reporting and support for linear (live) and video on demand (VOD). For a subset of use-cases, Server-Side Beacon (SSB) can also be used.
This table compares the features supported for Dynamic Ad Insertion (DAI) implementations that use the IMA SDK, SSB and the DAI API.
| Feature | IMA SDK | DAI API | SSB | Notes |
|---|---|---|---|---|
| VAST <icons> | |
|
|
IMA SDK supports rendering visual overlays, icons, and badges using VAST <icons>. DAI API supports rendering, however it requires publisher implementation. SSB doesn't support rendering any player-level user interface elements or icons. |
| Ad Exchange monetization | Ad Exchange monetization without IMA is supported through the Programmatic Access Library (PAL). | |||
| Clickable ads | There is IMA SDK support for DAI clickable ads for HTML5, iOS, and Android.
The DAI API supports clickable ads, however, they require publisher implementation. |
|||
| Companion ads | There is IMA SDK and DAI API support for companion ads only on the HTML5 platform using the Ads API. | |||
|
Live or linear stream |
||||
|
Player controls |
The DAI API provides metadata that supports player controls, however, they require publisher implementation. | |||
| Video ad metric reporting |
With SSB, the ad server tracks video ad impressions. However, there is no support on VOD streams for user interaction tracking. |
|||
|
VOD pre-rolls |
||||
|
VOD mid-roll and post-rolls |
DAI implementation types
|
IMA SDK |
The IMA SDK, when used for Dynamic Ad Insertion (DAI) enables the player to request a video on demand (VOD) stream or linear (live) stream and send signals to Ad Manager for reporting. Event tracking with the SDK is more accurate than Server-Side Beaconing (SSB). |
|
DAI AP |
The API for Dynamic Ad Insertion (DAI) allows access to monetized streams where the IMA SDK is not supported (for example, Smart TVs). The IMA SDK is required on platforms where it is available. The API supports all existing DAI features, however, they require publisher implementation. |
|
Server‑Side Beaconing (SSB) |
SSB allows an HLS/MPEG-DASH player to make a direct HTTP request to the Dynamic Ad Insertion (DAI) system, where Ad Manager tracks and reports on video stream metrics based on estimates. Any player should be able to play an SSB stream, however feature support is limited. Server-Side Beaconing (SSB) does not support player-level user interface or badge rendering. Because of this technical limitation, players using SSB cannot render any visual overlays, icons, or badges including VAST <icons>.
|