Via ad sets. Create an ad set with one FreeWheel ad setting in Backlot which
contains some movie details but does not contain the position at which an ad will play.
This sets up data that then tells FreeWheel to decide which ads to play.

Each of these options is described below.

Prerequisites

Before you can use Ooyala's FreeWheel ad integration, you need to log into the Customer Portal and submit a ticket requesting to add the FreeWheel
ad source to your account. Once the ad source is enabled you'll be able to create an ad set
for integrating with FreeWheel.

Option 1: Integrate the FreeWheel Ad Manager with the Ooyala Player via Player
Embedded Parameters

Follow the steps below to integrate FreeWheel ads with a player
via player embedded parameters.

Log into your Backlot account.

Go to the PUBLISH page.

Find the player branding name for the HTML5 or Flash player. This is the value you will
include on your web page.

Pass FreeWheel ad tags to the Ooyala player using the
freewheel-ads-manager parameter, as shown in the example below.

If you are creating an HTML5 player, provide an AdServer URL. You can use either:

a page-level override "html5_ad_server".

a third_party_module_parameters with a name "html5_ad_server". In the following
example, we use "html5_ad_server."

Set the fw_mrm_network_id on either the player third party module parameter level or at
the page level.

(Optional) Specify additional embedded parameters. See FreeWheel Ad Set
Fields for the list of fields you can use with FreeWheel.

Note: When you work with FreeWheel ad manager, you must provide an AdServer URL for
HTML5 either via a page-level override "html5_ad_server" or via
third_party_module_parameters with a name "html5_ad_server".

Note: The values in the following example are only used to illustrate how to use the
freewheel-ads-manager. You need to replace them with your own profiles,
ids, and URLS.

Backlot API: For
instructions on how to create an ad set programmatically, see Ad Sets. For the Ad Source, select the
FreeWheel OPF Module.

The required ad set fields for creating a FreeWheel ad set are:

Ad Set name: A name for the ad set.

MRM network ID: Provided by your FreeWheel account.

Player Profile: Provided by your FreeWheel account.

Video Asset network ID: Provided by your FreeWheel account.

Site Section ID: Provided by your FreeWheel account.

Note: The Tracking Pixel URL field is not relevant to the FreeWheel ad manager and
should be left blank.

Assign an ad set to an asset or multiple assets using the Backlot UI, Player API, or
Backlot API.

Backlot UI: For instructions on how to assign your FreeWheel ad set
to a single asset, see Managing Monetization. For instructions on how to assign your FreeWheel ad set
to multiple assets, see Bulk Applying
Settings.

Note: If the ad manager is defined using Backlot it will only
apply to your Flash Players.

Player API: With the Player API you can only associate an ad set with an asset
on your web page. To associate an ad set with an asset on multiple players you must
replicate the code for each player. To associate an ad set with an asset using the
Player API, see Assigning Ad Sets
Dynamically.

Backlot API: With the Backlot API you can associate
an ad set with an asset more concretely. That is, when you associate an asset with an ad
set using the Backlot API the asset and the ad set will be paired together on any player
and page you play the asset on. To associate an asset with an ad set using the Backlot
API, see Associate Ad Set with
Asset.

FreeWheel Ad Set Fields

The fields described
here pertain to Ooyala's FreeWheel ad manager integration. The last two columns of the table
note if the field is supported for Flash and/or HTML5

The ad manager is the location from which the player will load the FreeWheel
AdManager.swf from. The value assigned to this key must be HTTP. This is a
Flash-specific override, used when the site is loaded over HTTP.

X

adServer

The ad server is the location from which the player will request ads from. The
value assigned to this key must be HTTP. This is a Flash-specific override, used when
the site is loaded over HTTP.

X

html5_ad_server

The ad server is the location from which the player will request ads from. The
value assigned to this key must be HTTP. This is a HTML5 player-specific override, used
when the site is loaded over HTTP.

X

html5_ssl_ad_server

The ad server is the location from which the player will request ads from. The
value assigned to this key must be HTTPS. This is a HTML5 player-specific override, used
when the site is loaded over HTTPS.

X

flash_ssl_ad_manager

The ad manager is the location from which the player will load the FreeWheel
AdManager.swf asset. The value assigned to this key must be
HTTPS. This is a Flash-specific override, used when the site is loaded over HTTPS.

X

flash_ssl_ad_server

The ad server is the location from which the player will request ads from. The
value assigned to this key must be HTTPS. This is a Flash-specific override, used when
the site is loaded over HTTPS.

X

fw_ad_module_js

The ad module is the location from which the player will load the FreeWheel
AdManager.js from. The value assigned to this key must be HTTP. This is a HTML5
player-specific override, used when the site is loaded over HTTP.

X

fw_mrm_network_id

A unique identifier assigned by FreeWheel that identifies a company. Clients are
assigned their own Network ID during integration, and the player passes this value to
the AdManager before making an ad request.

X

X

fw_player_profile

A set of configurations that define what ads will be playable given the player
environment and framework. For example, profiles ensure that the Ad Server does not try
to return Silverlight ads for a Flash player. This is set up in the back end during
integration, and the correct profile for the player to set will be provided by
FreeWheel.

X

X

fw_site_section_id

The site section tag is
a string that identifies the site section, similar to the custom video ID for a video
asset. This is the site section tag as specified by you in the Network Module.

While the player does not directly interact with BVI, this is the system by which the
Custom Asset ID that it will supply is entered into the FreeWheel system.
Consequently, the player will need access to at least some of the same CMS information
so it can provide this identifier.

X

X

fw_site_section_id_type

Type of Site Section ID.

X

X

fw_site_section_network_id

Unique identifier of site section network to segment ad retrieval.

X

X

fw_tracking_pixel_url

URL for tracking pixels to monitor the delivery of your ad assets.

X

X

fw_video_asset_id

The piece of content a user is viewing. The player will need to identify the
asset to the AdManager for targeting purposes, using the custom asset ID provided via
FreeWheel’s Bulk Video Ingestion (BVI).

This field can be set on the page-level or by
movie metadata (configured via Backlot UI or Backlot APIs). If neither are set, the
value for this field will fall back to an externalID or an
embed_code (whichever is used to embed our player).

X

X

FreeWheel Example

The following example illustrates the use of the FreeWheel ad manager for video assets that
are played back in a Flash player.

With
these values, you will also see pre-roll, mid-roll, post-roll, and overlay ads on the ad response. For a
description of each field see "FreeWheel Ad Set Fields" later in this topic. In order to
display companion ads, you would need to include the following HTML content on your demo: