Platform Integration Options for Publishers

There's a variety of different client-side integration options available for Publishers. The goal of this article is to help publishers choose the type of integration that's right for them, and outline the quickest path to implementing the integration.

The table below outlines the available options, as well as points that need to be taken into consideration when choosing one of them.

Please note that these integration options are not just for publishers, but also partners implementing the integration on the publisher's behalf.

AdPlayer

  • Publisher’s video player loads the Video SSP AdPlayer.
  • Requires custom video player integration or an off-the-shelf plugin.
  • Ad unit provides automatic failover to the next ad source when an ad source fails (doesn’t return an ad).
  • Supports all ad spots: preroll, overlay, midroll, postroll.
  • Implementing the integration requires an ActionScript development resource, unless the content is using one of the pre-integrated players, such as Brightcove, Ooyala, JW Player, VMIX, Livestream, etc. Please click here to see our list of pre-integrated players.

VAST+VPAID Ad Tag

  • Publisher’s ad serving platform is used to traffic Video SSP VAST tag that includes the Video SSP VPAID ad unit.
  • Requires no integration if the ad serving platform or the video player already supports VAST tags with VPAID Creatives.
  • No limitation on supported preroll ad formats.
  • Ad unit provides automatic failover to the next ad source when an ad source defaults (doesn’t return an ad) when failover setting is configured in the Video SSP console.

VAST only Ad Tag

  • Publisher’s ad serving platform is used to traffic Video SSP VAST tag that includes a video Creative (FLV, MP4, etc.).
  • Requires no integration if the ad serving platform< or the video player already supports VAST tags.
  • Supports 1st party served preroll video ads and 3rd party served VAST ads when VAST Wrapper setting is configured in the Video SSP console.
  • Ad unit does NOT provide automatic failover to the next ad source when an ad source defaults (doesn’t return an ad).

JavaScript / Interstitial

  • Can work in conjunction with an ad server as a display style HTML/javascript ad tag.
  • Implementing requires basic web page editing skills.
  • Can be run in front of content of any type, not tied to video content.
  • Provides automatic failover to the next ad source when an ad source fails (doesn’t return an ad).
  • Supports all preroll ad formats.

Out-stream

  • Can work in conjunction with an ad server as a display style HTML/javascript ad tag.
  • Implementing requires basic web page editing skills.
  • Place in the publisher's page content rather than in a video player.
  • Video disappears from body of article once played to completion being less disruptive to the overall user experience.
  • Only appears when ad creative is greater than 50% visible.
  • Out-stream player supports 3rd Party served VAST + VPAID creative.
  • Out-stream player requires Video SSP Inventory Source or Marketplace Connection tag.

Mobile Android

  • The App is used to traffic Video SSP VAST tag that includes a video Creative (MP4).
  • Implementing requires Android programming skills.

Mobile iOS

  • The App is used to traffic Video SSP VAST tag that includes a video Creative (MP4).
  • Implementing requires iOS programming skills and Xcode.

MobileWeb HTML 5

  • Publisher’s ad serving platform is used to traffic Video SSP VAST tag that includes a video Creative (MP4).
  • Implementing requires basic web page editing skills.
  • Only supports preroll ad format, no companion.
  • Only supports rich media formats through 3rd Party Served VPAID JS.
  • Only supports mp4 media files.

In-Banner

  • Publisher’s ad serving platform is used to traffic a display style HTML/javascript ad tag into an in-banner ad spot.
  • Implementing requires basic web page editing skills.
  • Can serve video ads on to standard 300x250 medium-rectangle ad spaces.
  • Upon ad completion, the video ad is hidden and its associated 300x250 companion is displayed.
  • Supports all preroll ad formats as long as Flash is supported.
  • Ad unit provides automatic failover to the next ad source when an ad source fails (doesn’t return an ad).
  • Use the alternative preroll banner integration if you are also serving into an HTML5/JavaScript environment, as the ad unit will load in VPAID JavaScript mode for non-Flash environments.

 

Which integration option should I choose?

Here are some examples of use cases, along with recommended options based on the use case.

If the publisher has...

...and wants to use...

...they should use...

...because...

a pre-integrated video player (Brightcove, JW Player, Ooyala etc.)

The Video SSP Platform and the Video SSP Marketplace

AdPlayer

AdPlayer is already pre-integrated

a VAST-compliant video player or ad-serving platform

The Video SSP Marketplace

VAST tag

It's already supported, easy to turn on

a VAST- and VPAID-compliant video player or ad-serving platform

The Video SSP Marketplace

VAST+VPAID tag

It's already supported, with full ad format support

Web content / games / apps (no video)

The Video SSP Platform and the Video SSP Marketplace

Interstitial

Simple integration

an Android App

The Video SSP Platform and the Video SSP Marketplace

Mobile Android SDK + VAST

It's the only way

a iOS App

The Video SSP Platform and the Video SSP Marketplace

Mobile iOS SDK + VAST

It's the only way

a Non-Flash-enabled Mobile Platform

The Video SSP Platform and the Video SSP Marketplace

Mobile HTML 5 SDK + VAST

It's the only way

 

Have more questions? Submit a request