Clear search
Close search
Google apps
Main menu

Video implementation guide

When you monetize video or games inventory with DoubleClick Ad Exchange, you must comply with the implementation requirements, below. These requirements provide the best experience for your users, and promote a healthy ad ecosystem and efficient auction. 

Specific requirements apply to outstream video ads. Learn more in the outstream video ad policy.

The guide is divided into the following sections:

Interaction of ad with video player
Video ad placement
Video player and ad requirements
Requirements for running video in deals
Seller-rendered video ad policy
Placement guidelines

Interaction of ad with video player

  • Once an ad is served via Ad Exchange to a video player , the ad must be displayed until one of the following occurs:

    • the ad finishes playing
    • the user skips or closes the ad
    • the user navigates away from the video content by, for example, closing the browser window with the page displaying the video.
  • Content playback must also be paused when a user clicks an ad.

Video ad placement

  • Only one video ad may be displayed within the video player at any given time.
  • Sellers may not do any of the following:

    • obscure, hide, or remove any elements of the ad units (unless agreed upon by the Seller and Advertiser through Programmatic Guaranteed or Preferred Deals).
    • place the ad such that it obstructs the video player's play, pause, volume or any other controls
    • hard-code the ads into the content stream.
  • Players and games must pause the content when a user clicks an ad (though the ad may continue to run). After an ad click, content may not resume without user initiation (for example, the user clicks to play).

Video player and ad requirements

  • Video player requirements:

    • Video players used to request and display ads through Ad Exchange must meet the technical specifications set forth in the Ad Exchange Video Player Requirements and support all forms of user interaction supported by the video format of such ads. For example, all clickable links within an ad must remain clickable while displayed in the video player.
    • Sellers must not (i) alter the configuration of the video player to manipulate the targeting or delivery of ads in any way that is not expressly permitted by Google, (ii) hard code ads into the video player, or (iii) display any images, including creatives, in the template background of the video player.
  • Video ads may not be muted by default. They must be played back at the same volume level as the video content.
  • All video ads that are not skippable video ads (for instance, TrueView) must play to completion in the video player.
  • Companion ads must (i) be placed adjacent to their corresponding video ads, and (ii) meet one of the following dimensions:

    • 300 x 250
    • 300 x 100
    • 468 x 60
    • 728 x 90
    • 300 x 60
  • Players and games must maintain an aspect ratio of 4:3, 16:9, 1:1, 3:4, or 9:16, or as otherwise approved by Google.
  • To display video and overlay ads, players and games need to be larger than 400 x 200 pixels.

    • For overlay ads, players and games need to be larger than 400 x 100 pixels (see Supported overlay ad sizes).
    • For video ads, players and games need to have a minimum size of 240 x 200 pixels.
  • Players and games must accommodate all appropriate types of user interaction with ads (for example, click-through URLs, volume controls, pause).
  • Players and games that auto-play on page load must be above-the-fold on a typical browser (viewport) size of 1024 x 728 pixels.
  • Only one ad can be displayed within the player or game at any given time.

Requirements for running video in 1:1 deals (Programmatic Guaranteed or Preferred Deals)

Sellers must use a video player compliant with VAST 2, VAST 3, VPAID 1, or VPAID 2 standards. Unless otherwise permitted by Google and subject to the Seller-rendered video ad policy, below, Sellers must implement video inventory using the IMA SDK.

Requirements for running video Inventory in the Open Auction or Private Auctions

Sellers must utilize video players and/or games based on the following platform prerequisites:

  • HTML5-based ActionScript 3 players and games capable of Google HTML5 IMA v3 SDK integration.
  • Mobile app video players and games capable of Google iOS/Android IMA v3 SDK integration.
  • Unless otherwise permitted by Google and subject to the Seller-rendered video ad policy below, Sellers must implement video inventory using the IMA SDK.

Seller-rendered video ad policy

Google may from time to time, at its discretion, allow certain Sellers to forgo using the IMA SDK. Such implementations will be considered a “beta” feature and will require Google’s prior written approval. Seller understands and agrees that Google may cease providing access to beta features at any time in its discretion, and Google has no obligation to provide any support (technical or otherwise) in relation to any beta features. Sellers not using the IMA SDK for their implementation must abide by the following prerequisites (“Seller-rendered video ad policy”):

  • May only be used in a Connected TV environment where IMA SDK integration is unavailable unless otherwise approved by Google in writing at Google’s discretion. A “Connected TV” means a television set connected to the internet natively, or via another device, such as a Blu-ray player, game console, or set-top box.
  • Google DoubleClick Ad Exchange serves VAST 2 and VAST 3 responses that may contain VPAID 1 and VPAID 2 creatives. The Seller is responsible for ensuring the standards corresponding to these formats and assets are supported on Seller’s platform to ensure that all the creatives are correctly rendered. Google will not provide any support (technical or otherwise) in relation to these implementations.
  • Google will not be responsible for applying filtering of fraudulent/non-human traffic. 
  • Sellers must implement Ad Exchange tags for Seller-rendered video ads (including specifications for passing advertiser identifiers) per the technical protocol document that Google provides to Seller’s account manager.
  • Seller understands and agrees that buyers may be able to detect whether video ad inventory is seller-rendered versus Google-rendered, and accordingly may refrain from purchasing seller-rendered inventory. In addition, for seller-rendered video ad inventory, demand from AdWords buyers will not be available in the Open Auction or Private Auctions.

Placement guidelines

Video ads must comply with all applicable Ad Exchange policies, including the Google DoubleClick Ad Exchange Seller Guidelines. To ensure compliance with the Ad Placement in the Open Auction policies, Sellers' video ads must abide by the following:

  • Video ads may only be displayed in a video content clip that runs for at least as long as the duration of the video ad.

    • For TrueView ads, the duration of the ad is considered as the amount of time before a user is able to skip the ad.
  • To display more than one video ad, the duration of the video content clip must be longer than the sum duration of all the video ads.
Was this article helpful?
How can we improve it?