This page provides general information on IMA DAI support and compatibility for browsers, video formats, and platforms.
Supported video formats and browsers
HTML5 is still a new and evolving standard. As a result, support for various features differs among browsers, and there is no single default video format supported by all major browsers. The three main video formats used in the majority of browsers are H.264, HLS, and Dash.
VAST event compatibility
This section lists the VAST events that are automatically reported to the server based on the information returned in the VAST response.
rewind (fired when there
is any significant seeking in the backward direction),
Clickevent is only sent for video ads. Clicks cannot be captured on the native fullscreen players on Android, iOS, or desktop, but clicks can still be captured by an in-page click tracking element when the video is closed. However, if the video element uses native controls on the iPad, clicks cannot be captured.
IMA supports a simulated full screen mode, in which the video takes up the whole browser window. IMA considers a video to be in full screen mode when its
offsetHeightare at least the size of the document body. This mode is supported on all browsers.
On the iPhone and pre-3.0 Android platforms, video always plays in full screen mode.
iOS and Android only have native control of the volume. As such, IMA cannot determine the volume or mute state, nor is the SDK notified of changes. Below is a list of the browser versions which do and do not support
- Supported: Firefox 3.5+, Chrome 8+, Safari 4+
- Not supported: iOS, Android
Refer to the IAB guidelines for further details on VAST ad serving.
Ad events when rewatching ad breaks
IMA does not fire ad events when rewatching ads for the following reasons:
- Event URLs should only be triggered once, otherwise it could be read as spammy behavior.
- This lets users seek in and around the ad breaks that they've already viewed, creating a better seeking experience.
These are the only events fired when rewatching ad breaks:
Supported video player platforms
The Google IMA SDKs are supported on the following platforms:
|Desktop: Chrome, Firefox, Safari, Edge, Opera
Mobile: Chrome/Android Browser (Android for phones and tablets), Safari and Chrome (iOS)
|All Cast devices
|All devices that are still receiving software updates from Roku
Video stream format support
IMA supports both HLS and DASH across its SDKs. See this table for support on specific SDK platforms. For proper stream playback, your video player needs to support the stream type being used.
|IMA SDK platform
Video features and SDK versions
To learn more about the following features, read video advertising overview.
|IAB Video Suite
|Ad Manager Video features
|Non-linear ads (Overlays)
|VAST 3 alternate companion ad resources
|Active View viewability
|Companion backfill with display request
|Google Publisher Tag (GPT) compatibility
|Reporting on multi-event tracking (MET)
|Skippable (reservation / non-TrueView)
|AdSense for Video features
|Ad Manager Ad Exchange features
|Active View viewability
|Why This Ad?
1 Of the VAST 4 features supported by Google Ad Manager, IMA support the following features:
- VAST 4.2
- Support for Secure Interactive Media Interface Definition (SIMID)
- Allowance of multiple
- VAST 4.0
- Mezzanine file
- New VAST error codes
- New VAST macros
2 The following VAST 3.0 features are not yet supported:
- Companion delivery options
3 The following VMAP features are not yet supported:
- VMAP-specific tracking events
- VMAP-specific error codes
- Overlay ads
- Time offsets other than hh:mm:ss or "start" and "end"
4 Only image companions are supported. Image companions require custom implementation for populating ads. Companion ads are not supported on tvOS.
5 Traditional skippable ads are only supported in the IMA DAI SDKs for HTML5, iOS, tvOS, Roku, and Android (including Android TV).
6 TrueView skippable ads are only supported in the IMA DAI SDKs for HTML5, iOS, Roku, and Android (including Android TV).
7 Why This Ad? requires that the
adUiElement parameter be passed when creating the