DAI Pod Serving is a beta intended for advanced Ad Manager publishers and video technology partners who either have an in-house manifest manipulation service or are currently using third-party manifest manipulation that's already integrated with DAI. Contact your account manager for details.
Set up a live/linear channel and share the DAI ad tag
-
Identify where to enable DAI Pod Serving or have a new channel created.
Your in-house or third-party partner should update the channel configuration utilizing the DAI Pod Serving integration.
-
Provide the DAI ad tag for the live channel to the in-house or third-party partner who should then:
- Implement the ad tag
- Create playback profiles and corresponding live stream events in Ad Manager
- Create DAI authentication keys and associate them with the
LiveStreamEvent
object
- By default, the channel uses the default slate specified in your Ad Manager network. You can manually change the slate using the Live Streams page in Ad Manager or API.
Implement the IMA SDK on the player
See the DAI Pod Serving developer documentation for SDK & API configurations and examples. Available for HTML5, Android, iOS, tvOS, DAI API. |
Stream content
Once the IMA SDK is implemented on the player:
-
Perform a stream create request via the SDK, supplying:
- Your Ad Manager network code
- You Ad Manager asset key
The SDK then returns a
stream_id
. -
Configure the initial playback request to the application and include the following:
- The
stream_id
returned from the SDK - The ad configuration containing the Ad Manager network code
- The
-
When the application generates a live stream session:
- Ad breaks are filled with ads selected by Ad Manager
- Ad beacons are sent by Ad Manager
- Ad debug data is available in Ad Manager