wiki:OvaReleaseNote-1.0.0-RC7

Context Navigation

Version 29 (modified by paul, 15 months ago) (diff)
--

TracNav

Project

Dev Corner (restricted)

Support

Other Resources

What's New? (1.0.0 Release Candidate 7)

The following versions have been issued as "release candidates".

OVA for AS3 v1.0.0 RC7
OVA for JW Player 4 v1.0.0 RC7
OVA for JW Player 5 v1.0.0 RC7 (requires JW 5.6 or higher to run)
OVA for Flowplayer v1.0.0 RC7

RC7 includes a number of key changes over RC6:

There have been some filename changes in the package (see section 1 below for details)

The configuration structure has been refined. Various options have moved around and been renamed (consult section 2 for details)

Various APIs in the OVA Framework have changed (see section 3)

A new player display definition model has been introduced into OVA to allow margins etc. to be more effectively specified for various playback types (described further in section 4)

Non-linear ads can now be displayed using HTML5, this allows OVA to support iFrame and Javascript non-linear ad types in overlay and non-overlay format (consult section 6 for further information)

Improved Google Analytics support (see section 5 for details)

RC7 follows RC6 - please refer to the RC6 release note for a full account of all changes made up to and including RC6.

1. SWF and Javascript File Name Changes

The following SWF and Javascript file name changes have occurred in this release:

In preparation for the V1.0 production release, the OVA for JW5 and OVA for JW4 SWFs have been renamed to "ova-jw.swf" - in addition the OVA for JW5 Javascript plugin has been renamed to "ova-jw.js". These will be the official names of the OVA for JW V1.0 plugins (renaming them allows the pre V1.0 plugins/setups to continue operating untouched on the Longtail plugin repository). It is also worth noting that existing OVA configurations will work with the new names (e.g. your JW5 external config files do not require change as the <ova.XXXX> tagset will work with the "ova-jw" SWF naming)

The previously named OVA jQuery companion support Javascript file ova-jquery-companions.js has been renamed to ova-jquery.js to better reflect the new "non-companion" functionality that it now includes

2. Depreciated Configuration Options

While OVA will attempt to remain backward compatible, a number of configuration options have been moved around in the RC7 release as part of a general clean up to the configuration structure. These include:

Regions and Overlay configuration changes

"overlays:{}" config block has become "regions:{}"

"overlays.controlButton" has become "regions.controlButton"

"overlays.regions[]" has become "regions.declarations[]"

"ads.replayNonLinearAds" has become "overlays.replay"

"ads.acceptedNonLinearAdMimeTypes" has become "overlays.acceptedMimeTypes"

"ads.enableOverlayScaling" has become "overlays.enableScaling"

"ads.enforceOverlayRecommendedSizing" has become "ads.overlays.enableScaling"

Companion configuration changes

"ads.companions[]" has become "ads.companions.regions"

"ads.processCompanionsExternally" has become "ads.companions.html5"

"ads.millisecondDelayOnCompanionInjection" has become "ads.companions.millisecondDelayOnInjection"

"ads.displayCompanions" has become "ads.companions.enable"

"ads.restoreCompanions" has become "ads.companions.restore"

"ads.additionalParamsForSWFCompanions" has become "ads.companions.additionalParamsForSWFCompanions"

Skip Ads and Control Bar configuration changes

"ads.controls.skipAd" has become "ads.skipAd"

"ads.controls{}" has become "player.modes.linear.controls"

"ads.disableControls" has become "player.modes.linear.controls.manage"

VPAID configuration changes

"ads.vpaid.controls.hideOnLinearPlayback" has become "player.modes.linear.controls.vpaid.visible"

Ad scheduling configuration changes

"ads.schedule[].position" for non-linear ads has become "ads.schedule[].region"

If you use any of these options you are advised to move to the new configuration structure/options as soon as possible.

For an illustration of the configuration option changes, please consult the OVA RC7 Examples.

3. API Changes

The following API changes have occurred in this release:

TheStageDimensions class has been removed and replaced with a new Player display model (a number of classes) - see "Section 5: Configuring the Player Display" for further information.

_vastController.hasStageDimensions() has been removed and is no longer required

The ControlsConfig class has been removed and replaced with the new Player display model - see Section 5 below for details. As a result

_vastController.config.adsConfig.controlsConfig is no longer available

_vastController.enableNonLinearAdDisplay(DisplayProperties) has been replaced with _vastController.enableDisplayRegions(DisplayProperties)

Config.adsConfig.vpaidConfig.linearBarHeight has been removed - this value can be found in the new player display model

_vastController.disableControls has been removed and replaced with vastController.config.playerConfig.shouldDisableControlsDuringLinearAds(isVPAID)

_vastController.shouldShowControlsDuringLinearAds() has been removed and replaced with _vastController.config.playerConfig.shouldHideControlsOnLinearPlayback(isVPAID)

_vastController.getControlConfig() has been replaced with _vastController.controlEnabledStateForLinearAdType(controlName:String, isVPAID:Boolean):Boolean

OverlayAdDisplayEvent.adSlotKey has been removed and has been replaced with OverlayAdDisplayEvent.adSlot.key

OverlayAdDisplayEvent.ad has been removed and has been replaced with OverlayAdDisplayEvent.nonLinearVideoAd

CompanionAdDisplayEvent.ad has been removed and has been replaced with CompanionAdDisplayEvent.companionAd

The region constant RESERVED_FULLSCREEN_TRANSPARENT_WITH_CB_HEIGHT has become RESERVED_FULLSCREEN_TRANSPARENT_BOTTOM_MARGIN_ADJUSTED

The structure of the DisplayProperties class has been modified. Previously the constructor was:

public function DisplayProperties(
            displayObjectContainer:DisplayObjectContainer=null, 
            displayWidth:int=0, 
            displayHeight:int=0, 
            bottomMargin:int=0, 
            originalWidth:int=-1, 
            originalHeight:int=-1, 
            linearControlbarHeight:int=-1, 
            nonLinearControlbarHeight:int=-1, 
            displayMode:String=DISPLAY_NORMAL, 
            controlBarY:int=-1);

now the constructor is:

public function DisplayProperties(
           displayObjectContainer:DisplayObjectContainer, 
           displayWidth:int, 
           displayHeight:int, 
           displayMode:String, 
           displaySpecification:DisplaySpecification, 
           controlsVisibleAtBottom:Boolean, 
           controlsHeight:Number, 
           controlsYPos:Number);

For more information on the DisplaySpecification class, please refer to "section 4: The New Player Display Configuration Model".

4. The New OVA Player Display Configuration Model

In RC7, the way the player display is configured and programmed within the framework completely changed. The change was required to add support for the display of non-linear ads via HTML5.

The characteristics of the player display are now configured via the "player" configuration block. For example, to hard code the height of a control bar, the following configuration is now used:

{
     "player": {
            "controls": { "height": 35 }
     },
     "ads": {
            ....
     }
}

Or to set the bottom margins for the display, the following configuration can be used:

    "player": {
          "margins": {
                "withControls": 50,
                "withControlsOverride": 50,
                "withoutControls": 30,
                "withoutControlsOverride": 30
          }
    },
    "ads": {
          ...
    }
}

To hide the JW Player custom logo during linear ad playback, the following configuration can be used:

{
    "player": {
         "modes": {
              "linear": {
                    "hideLogo": true
              }
         }
    },
    "ads": {
          ...
    }
}

5. Using OVA with Google Analytics

RC7 includes dramatically improved support for the use of Google Analytics with OVA.

The following VAST/VPAID events can be tracked via Google Analytics:

Linear, Non-Linear and Companion Impressions
Ad calls - succeed, failed, timed out, deferred
Template loads - succeeded, failed, timed out, deferred
Ad slot loads - succeeded, deferred, timed out, failed
Linear Ad progress tracking - first quartile, midpoint, third-quartile, complete
Player pause, resume, mute, fullscreen during Linear ad playback
Linear and non-linear click throughs
VPAID events - ad loaded, ad started, ad stopped, ad linear change, ad expanded change, ad remaining time change, ad volume change, ad video start, ad video first quartile, ad video midpoint, ad video third quartile, ad video complete, ad user accept invitation, ad user close, ad paused, ad playing, error

5.1 Using a Custom Account

To configure a custom account ID, use the following configuration approach:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "enable": true,
                        "accountId": "UA-10158120-1",
                        "impressions": {
                              "linear": "put-your-custom-url-here",
                              "nonLinear": "put-your-custom-url-here",
                              "companion": "put-your-custom-url-here"
                        }
	         }
          }
     },
     "ads": {
           ....
     }
}

In the example above, a custom GA account with an id of "US-10158120-1" is used and the linear, non-linear and companion impressions are tracked to that account using the URLs specified.

5.2 Specifying Additional Tracking Parameters

It is possible to declare additional parameters to be added to the GA calls ad runtime.

The following code snippet illustrates how this can be achieved:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "enable": true,
                        "accountId": "UA-10158120-1",
                        "additionalParams": {
                              param1: "value1",
                              param2: "value2"
                        }

The config above results in both param1=value1 and param2=value2 being appended to all of the custom GA calls that OVA makes.

5.3 Tracking Impressions

Linear, non-linear and companion impressions can be tracked via Google Analytics.

To activate impression tracking to your GA account, use the following configuration structure:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "enable": true,
                        "accountId": "UA-10158120-1",
                        "impressions": {
                              "linear": "put-your-custom-url-here",
                              "nonLinear": "put-your-custom-url-here",
                              "companion": "put-your-custom-url-here"
                        }
	         }
          }
     },
     "ads": {
           ....
     }
}

When OVA makes GA calls, different URLs are used for linear, non-linear and companion impression tracking events.

By default, the following URL structure is applied:

linear - "/ova/impression-counter/custom/linear"
non-linear - "/ova/impression-counter/custom/nonLinear"
companion - "/ova/impression-counter/custom/companion"

A different set of tracking URLs can be specified at any time using the declaring the required URL against the appropriate configuration option. For example, if a path of /ova/impression-counter/ova-test/XXX is to be used, you can configure this as follows:

{
     ...
     "analytics": {
          "google": {
                 "ova": {
                        "accountId": "UA-10158120-1",
                        "impressions": {
                              "linear": "/ova/impression-counter/ova-test/linear",
                              "nonLinear": "/ova/impression-counter/ova-test/nonLinear",
                              "companion": "/ova/impression-counter/ova-test/companion"
                        }
                 }
          }
     },
     "ads": {
           ....
     }
}

For linear ads, these parameters include:

ova_slot_id - the unique ID for this ad slot
ova_slot_type - linear, linear interactive
ova_slot_position - pre, mid or post-roll
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_media_url - the url of the media displayed
ova_media_bitrate - the bitrate of the media displayed
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

For non-linear ads, the parameters added to the tracking URL include:

ova_slot_id - the unique ID for this ad slot
ova_slot_type - linear, linear interactive
ova_slot_position - the region used to display the overlay
ova_slot_start_time - the start time for this overlay
ova_slot_duration - the display duration of the overlay
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_creative_type - the creative type of the media being displayed
ova_creative_width - the width of the creative
ova_creative_height - the height of the creative
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

For companion ads, the following parameters are added to the tracking URL:

ova_slot_id - the unique ID for this ad slot
ova_companion_width - the width of the companion
ova_companion_height - the height of the companion
ova_companion_type - the companion media type
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

5.4 Tracking Ad Calls

Ad calls may be tracked via Google Analytics. If an ad call returns a VAST wrapper, the subsequent ad call will be tracked with a parameter identifying the ad call as wrapped.

A number of ad call states may be tracked:

Fired - logged when the ad call is fired off to the ad server
Complete - recorded when the ad call successfully completes
Timed out - logged if the ad call times out
Error - logged if an error is recorded as the ad call is made
Failed Over - will be tracked if the ad call fails over because no ads are returned
Deferred - logged if the ad call is deferred because the ad slot is "load on demand"

By default, the following URL structure is applied across these states:

Fired - /ova/ad-calls/custom/fired
Complete - /ova/ad-calls/custom/complete
Timed out - /ova/ad-calls/custom/timed-out
Error - /ova/ad-calls/custom/error
Failed Over - /ova/ad-calls/custom/failed over
Deferred - /ova/ad-calls/custom/deferred

The following code snippet illustrates how to enable ad call tracking using the custom GA account setting:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "accountId": "UA-10158122-2",
                        "adCalls": {
                              "enable": true
                        }
                 }
          }
     },
     "ads": {
           ....
     }
}

The default URLs for each ad call state can be overridden via the "adCalls" config option as follows:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "accountId": "UA-10158122-2",
                        "adCalls": {
                              "enable": true,
                              "fired": "/ova/ad-calls/action=fired",
                              "complete": "/ova/ad-calls/action=complete",
                              "timeout": "/ova/ad-calls/action=timed-out",
                              "error": "/ova/ad-calls/action=error",
                              "failover": "/ova/ad-calls/action=fired",
                              "deferred": "/ova/ad-calls/action=fired"
                        }
                 }
          }
     },
     "ads": {
           ....
     }
}

Tracking of ad calls is turned off within OVA by default.

A number of additional parameters are recorded with each ad call tracking URL. These include:

ova_slot_id - the unique ID for this ad slot
ova_slot_position - the region used to display the overlay
ova_slot_start_time - overlays only - the start time for the overlay
ova_slot_duration - overlays only - the display duration of the overlay
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
ova_wrapped_ad_tag - true if the ad tag has been specified in a VAST wrapper
Any additional tracking parameters configured via OVA

5.5. Tracking Template Loads

It is possible to track the load status of VAST templates as they result from ad calls made by OVA.

The following template load events can be tracked:

loaded - successfully loaded after an ad call
error - an error resulted during the ad call
deferred - deferred because there are on-demand ad slots in the schedule
timeout - the ad call timed out

The following code snippet illustrates how to enable template tracking:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "accountId": "UA-10158122-2",
                        "templates": {
                              "enable": true,
                              "loaded": "/ova-example/templates/loaded",
                              "error": "/ova-example/templates/error",
                              "timeout": "/ova-example/templates/timeout",
                              "deferred": "/ova-example/templates/deferred"
                        }
	         }
          }
     },
     "ads": {
           ....
     }
}

Each GA call has the following fields added to the URL:

ova_ad_count - the number of ads recorded in the parsed template
Any additional tracking parameters configured via OVA

5.6 Tracking Ad Slot Loads

The status of on-demand ad slot loading can be tracked via Google Analytics.

The following on-demand ad slot load events can be tracked:

loaded - successfully loaded after an ad call
error - an error resulted during the ad call
deferred - deferred because there are on-demand ad slots in the schedule
timeout - the ad call timed out

The following code snippet illustrates how to enable template tracking:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                        "accountId": "UA-10158122-2",
                        "templates": {
                              "enable": true,
                              "loaded": "/ova-example/adslot/loaded",
                              "error": "/ova-example/adslot/error",
                              "timeout": "/ova-example/adslot/timeout",
                              "deferred": "/ova-example/adslot/deferred"
                        }
                 }
          }
     },
     "ads": {
           ....
     }
}

Each GA call has the following fields added to the URL:

ova_slot_id - the unique ID for this ad slot
ova_slot_position - the region used to display the overlay
ova_slot_start_time - overlays only - the start time for the overlay
ova_slot_duration - overlays only - the display duration of the overlay
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
ova_wrapped_ad_tag - true if the ad tag has been specified in a VAST wrapper
Any additional tracking parameters configured via OVA

5.7 Tracking Playback Events

As OVA ads are played, a number of events can be tracked using Google Analytics. These events include:

Linear Ad progress tracking - first quartile, midpoint, third-quartile, complete
Player pause, resume, mute, fullscreen during Linear ad playback
Linear and non-linear click throughs

5.7.1 Tracking Linear Ad Progress Events

The following non-interactive linear ad playback progress events can be tracked via Google Analytics:

first quartile complete
midpoint complete
third-quartile complete
playback complete
player events such as going fullscreen, pause, resume, mute, close etc.

The following code snippet illustrates how to enable these events to be tracked:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                       "accountId": "UA-10158122-2",
                       "progress": {
                            "enable": true,
                            "start": "/ova-example/progress/start",
                            "firstQuartile": "/ova-example/progress/firstQuartile",
                            "midpoint": "/ova-example/progress/midpoint",
                            "thirdQuartile": "/ova-example/progress/thirdQuartile",
                            "complete": "/ova-example/progress/complete",
                            "pause": "/ova-example/progress/pause",
                            "resume": "/ova-example/progress/resume",
                            "fullscreen": "/ova-example/progress/fullscreen",
                            "mute": "/ova-example/progress/mute",
                            "unmute": "/ova-example/progress/unmute",
                            "expand": "/ova-example/progress/expand",
                            "collapse": "/ova-example/progress/collapse",
                            "acceptInvitation": "/ova-example/progress/acceptInvitation",
                            "close": "/ova-example/progress/close"
                       }
                 }
          }
     },
     "ads": {
           ....
     }
}

Each GA call has the following fields added to the URL:

ova_slot_id - the unique ID for this ad slot
ova_slot_type - linear, linear interactive
ova_slot_position - pre, mid or post-roll
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_media_url - the url of the media displayed
ova_media_bitrate - the bitrate of the media displayed
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

5.7.2 Tracking Click Events

Ad click through events can be tracked via Google Analytics.

The following code snippet illustrates how to enable this:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                       "accountId": "UA-10158122-2",
                       "clicks": {
                            "enable": true,
                            "linear": "/ova-example/clicks/linear",
                            "nonLinear": "/ova-example/clicks/linear", 
                            "VPAID": "/ova-example/clicks/linear"
                       }
                 }
          }
     },
     "ads": {
           ....
     }
}

For linear ads, these parameters include:

ova_slot_id - the unique ID for this ad slot
ova_slot_type - linear, linear interactive
ova_slot_position - pre, mid or post-roll
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_media_url - the url of the media displayed
ova_media_bitrate - the bitrate of the media displayed
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

For non-linear ads, the parameters added to the tracking URL include:

ova_slot_id - the unique ID for this ad slot
ova_slot_type - linear, linear interactive
ova_slot_position - the region used to display the overlay
ova_slot_start_time - the start time for this overlay
ova_slot_duration - the display duration of the overlay
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_creative_type - the creative type of the media being displayed
ova_creative_width - the width of the creative
ova_creative_height - the height of the creative
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

For companion ads, the following parameters are added to the tracking URL:

ova_slot_id - the unique ID for this ad slot
ova_companion_width - the width of the companion
ova_companion_height - the height of the companion
ova_companion_type - the companion media type
ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_ad_server_type - the ad server type configured in OVA for the ad call
ova_ad_tag - the ad tag used to make the ad call to get this ad
Any additional tracking parameters configured via OVA

5.7.3 Tracking VPAID Events

The full set of VPAID events can be tracked via Google Analytics. These events include:

loaded, started, stopped
linear changed
expanded changed
remaining time change
volume changed
video started, video first quartile complete, video midpoint complete, video third quartile complete, video complete
user accepted invitation
user closed the ad
playback paused, resumed
error conditions

The following code snippet illustrates how to setup tracking for VPAID linear and non-linear (overlay) ads:

{
     ...
     "analytics": {
          "google": {
                 "custom": {
                       "accountId": "UA-10158122-2",
                       "vpaid": {
                            "enable": true,
                            "loaded": "/ova-example/vpaid/loaded",
                            "started": "/ova-example/vpaid/started",
                            "stopped": "/ova-example/vpaid/stopped",
                            "linearChange": "/ova-example/vpaid/linearChange",
                            "expandedChange": "/ova-example/vpaid/expandedChange",
                            "remainingTimeChange": "/ova-example/vpaid/remainingTime",
                            "volumeChange": "/ova-example/vpaid/volumeChange",
                            "videoStart": "/ova-example/vpaid/videoStart",
                            "videoFirstQuartile": "/ova-example/vpaid/videoFirstQuartile",
                            "videoMidpoint": "/ova-example/vpaid/videoMidpoint",
                            "videoThirdQuartile": "/ova-example/vpaid/videoThirdQuartile",
                            "videoComplete": "/ova-example/vpaid/videoComplete",
                            "userAcceptInvitation": "/ova-example/vpaid/userAccept",
                            "userClose": "/ova-example/vpaid/userClose",
                            "paused": "/ova-example/vpaid/paused",
                            "playing": "/ova-example/vpaid/playing",
                            "error": "/ova-example/vpaid/error"
                       }
                 }
          }
     },
     "ads": {
           ....
     }
}

For each VPAID tracking event fired, the following attributes are appended to the GA tracking URL:

ova_ad_id - the ad ID taken from the VAST response
ova_ad_system - the ad system take from the VAST response
ova_ad_title - the ad title taken from the VAST response
ova_ad_description - the ad description taken from the VAST response
ova_creative_type - the creative type of the media being displayed
ova_creative_width - the width of the creative
ova_creative_height - the height of the creative

5.8 The OVA Master Account

OVA uses Google Analytics to collect cursory operational data as it runs to help with support, testing and backward compatibility decisions made during the ongoing development of the OVA for Flowplayer and JW5 plugins. This data is sent to a master OVA GA account "UA-4011032-6".

6. Displaying Non-Linear Ads with HTML5

RC7 includes support for the display of specific non-linear ad types via HTML5. As such, OVA can now be configured to either display non-linear ads via it's internal Flash mechanism or externally via the OVA HTML5 (jQuery) library.

The ad types that can be displayed via HTML5 include:

Image
Non-VPAID SWF
Text
HTML
iFrame
Javascript

OVA can display the following non-linear ad types internally via Flash:

Image
Non-VPAID SWF
VPAID SWF
Restricted HTML
Text

5.1.1 Displaying via Flash

Being written

5.1.1.1 The Defaults

Being written

5.1.1.2 Using "Auto" Regions

Being written

5.1.1.3 Using "Custom" Regions

Being written

5.1.2 Displaying via HTML5

Being written

5.1.2.1 The Defaults

Being written

5.1.1.2 Using "Custom" Regions

Being written

5.2.2 Displaying via Flash and HTML5 Concurrently

Being written

5.2 Activating a Close Button

Being written

5.2.1 The Close Button in Flash

Being written

5.2.2 The Close Button with HTML5

Being written

5.3 Content Matching Rules

Being written

5.3.1 Matching by Size

Being written

5.3.2 Matching by Ad Type

Being written

5.3.1 Ensuring that a match is always found

Being written

5.4 Scaling Non-Linear Ads

Being written

Download in other formats:

Plain Text

Context Navigation

TracNav

Project

Dev Corner (restricted)

Support

Other Resources

What's New? (1.0.0 Release Candidate 7)

1. SWF and Javascript File Name Changes

2. Depreciated Configuration Options

3. API Changes

4. The New OVA Player Display Configuration Model

5. Using OVA with Google Analytics

5.1 Using a Custom Account

5.2 Specifying Additional Tracking Parameters

5.3 Tracking Impressions

5.4 Tracking Ad Calls

5.5. Tracking Template Loads

5.6 Tracking Ad Slot Loads

5.7 Tracking Playback Events

5.7.1 Tracking Linear Ad Progress Events

5.7.2 Tracking Click Events

5.7.3 Tracking VPAID Events

5.8 The OVA Master Account

6. Displaying Non-Linear Ads with HTML5

5.1.1 Displaying via Flash

5.1.1.1 The Defaults

5.1.1.2 Using "Auto" Regions

5.1.1.3 Using "Custom" Regions

5.1.2 Displaying via HTML5

5.1.2.1 The Defaults

5.1.1.2 Using "Custom" Regions

5.2.2 Displaying via Flash and HTML5 Concurrently

5.2 Activating a Close Button

5.2.1 The Close Button in Flash

5.2.2 The Close Button with HTML5

5.3 Content Matching Rules

5.3.1 Matching by Size

5.3.2 Matching by Ad Type

5.3.1 Ensuring that a match is always found

5.4 Scaling Non-Linear Ads

Download in other formats: