Google IMA Ad Plugin

Use the google_ima.js plugin to load Google IMA ads in Player V4. The way the google_ima.js plugin works, ads will be loaded dynamically before the ad position. The plugin was developed using the Ad Manager Framework.

Google IMA v3

Google IMA v3 is an ad server and ad management platform. The Google Interactive Media Ads (IMA) SDK enables publishers to display linear, non-linear, and companion ads in interactive media content such as videos and games. Publishers can use the IMA SDK to request and display ads served by DoubleClick for Publishers (DFP), the Google AdSense network, or any VAST-compliant ad server. Common scenarios for using the IMA SDK include displaying pre-rolls or overlays in video content.

Note: Google IMA's HTML5 SDK is not supported on all browsers. For a list of browsers supported by Google IMA, go to
Per Google, the Google IMA SDK is intended for the following publishers:
  • DoubleClick for Publishers (DFP) users: Publishers can use DFP to traffic, target, and serve their directly-sold ads. The IMA SDK offers advanced video ad serving features.
  • AdSense publishers: Publishers can also use the Google AdSense Network (AdSense for Video (AFV) and AdSense for Games (AFG)) to monetize their inventory. If you only want to display AFV/AFG ads, DFP is not required. However, AFV/AFG ads still require the IMA SDK.
  • Publishers using VAST ads from a third-party ad server: Publishers can book their VAST ads in DFP and use the IMA SDK to request and display them. VAST ad responses are parsed prior to ad playback. Refer to the VAST guidelines for details.
  • AdExchange for Video: Publishers can make use of remnant ad inventory from AdExchange for Video via the Google AdSense Network.

Supported Platforms

Ooyala supports the Google IMA ads served by DFP or AdSense generated in VAST 2.0 and 3.0 and VPAID 1.0 and 2.0 format on the following platforms for this release of Player V4:
  • HTML5
  • iOS mobile SDK
  • Android mobile SDK

Ad Rules

Ad Rules define how ads display with video content. Publishers can create Ad Rules on their DFP Premium account to determine when ads play in a video, for how long, and as a result of which triggers, such as content targeting parameters. They can also target Ad Rules so that they apply to:
  • Specific videos, such as all episodes of a particular TV show.
  • Video metadata, such as videos in the "sports" genre.
  • Users' geography.
  • Users' browsers.
  • Custom targeting keys and values that you define.

For more information about the supported platforms for Ad Rules, go to

Note: Google IMA's AdRules feature supports ad-breaks without additional code. Do not use AdRules with other types of ads. We highly discourage you from mixing other adTagUrls with an AdRule adTag as it may lead to unexpected behavior.

For ad rule ads, Google handles all ad management and placement of Google IMA ads. For ad rule ads, the Ooyala plugin only tells Google what point the video is at on the video's timeline. One ad tag is used to represent the group of ad rule ads. By default, Ooyala supports Google IMA Ad Rules on iOS Safari (HTML5) with Player V4. See Google's Supported video player platforms for more information.

For ads without ad rules, Google plays and renders the ad, but the Ad Manager Controller determines when to play the ad. One ad tag is used for each ad.

Supported Ad Positions

For this release, ads are supported on Player V4 HTML5 players and the mobile SDKs for iOS and Android for the following ad positions:
  • Pre-Roll
  • Mid-Roll
  • Post-Roll
  • Podded
  • Skippable
  • Clickthrough
  • Overlay (not supported with Ad Rules ads)
  • Companion

Ads and Firefox Private Browsing

For consumers using Private Browsing windows in Firefox, some ads may fail to load because privacy mode blocks certain kinds of tracking URLs.