If you don't find an answer, please click here to post your question.
Reply
Community Manager
Posts: 89
Registered: ‎04-08-2014

Ooyala Video Advertising Release Notes - Subscribe to Receive Updates

[ Edited ]

Hello Ooyala Customers,

 

Welcome to the Video Advertising Release Notes page.

To stay up-to-date on the latest Ooyala Video Advertising updates, please subscribe to this thread. Once subscribed you will receive email notifcations everytime new release notes are published. Note: See this KB article for information on subscribing to community threads/posts.

 

Release Notes

 

Welcome to the Ooyala Video Advertising Release Notes

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2015-10-15 Release

[ Edited ]

Android SDK 2.x

 

New Integration SDK: Android SDK 2.x

 

A second generation version of the Android SDK is released, which is used to develop the ad serving integration for your native Android video player application.

 

 

Integration with Android SDK 2.x supports the following new features:

  • Passbacks: another ad is requested if no ad was served in the first request
  • Session information: enables session level clash protection (only one ad from a group of mutually exclusive ads is ever shown in one session) and ad sequencing

 

To start using these features, you have to (re)write the Android integration with the new Android SDK 2.x, for Android 2.2 or later and preferably using Java 7 or later. Contact Professional Services for help and validation at sthlm-psg-team@ooyala.com.

 

The necessary resources to start developing can be found here: http://help.ooyala.com/downloads

 

 

Documentation Releases

 

This release includes the following documentation additions: Android SDK 2.x documentation.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2015-11-17 Release

2015-11-17 Release

 

Android SDK 2.x demo integration and new Swift iOS SDK 2.x demo

 

Android SDK 2.x Demo Integration

 

The second generation version of the Android SDK was released a few weeks ago and now a demo integration and the accompanying developer documentation is available.

 

The demo integration illustrates the following features of the SDK:

 

  • Linear ads: showing pre-, mid-, and post-rolls
  • Lazy loading: request 3rd party ads as late as possible to avoid wrongful impression tracking by the 3rd party provider
Warning: This demo is not intended to be used in production and Ooyala does not support or fix issues that may arise from blindly copying code from this demo into your app.
 

The necessary resources to start developing can be found here: http://support.ooyala.com/users/resources/mobile-and-client-sdks, under Ad Products, Android.

 

The Android demo integration is located here: adtech-android-2.x-demo

 

iOS SDK 2.x Demo Integration in Swift

 

A new demo integration is available for iOS SDK 2.x written in Swift, and can be found here: ios-2.x-swift-demo

 

Documentation Releases

 

This release includes the following documentation additions: Android SDK 2.x.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2015-11-26 Release

2015-11-26 Release

 

Ooyala Pulse SSP v1.87

 

 

Ooyala Pulse SSP New URLs

 

The URLs to connect to Ooyala Pulse SSP are now in line with our new product naming conventions to create a unified family of Ooyala products.

 

The URL to log into Ooyala Pulse SSP is now: pulse-ssp.ooyala.com. If you connect to the old URL, you will get redirected to this new URL automatically.

 

The URL for the reporting side of Ooyala Pulse SSP is now: pulse-ssp-reporting.ooyala.com. The old URL for the reporting side does not work anymore.

 

Due to the URL changes, your login details are not filled in automatically if you had saved them in your browser previously.

 

Ooyala Pulse SSP Real Time Reporting Enhancements

 

New real time reporting metrics are now available for both direct campaigns and RTB.

  • For Inventory:
    • Impressions, shown on the placement and channel level real time reporting tab, shows the amount of times a placement or channel has recorded an impression.
    • Clicks, shown on the placement and channel level real time reporting tab, shows the amount of times a placement or channel has recorded a click.
    • Video Start, shown on the placement and channel level real time reporting tab, shows the amount of times a placement or channel has recorded a video start event. *Only available for video inventory
    • Video 100% Completion, shown on the placement and channel level real time reporting tab, shows the amount of times a placement or channel has recorded a video complete event. *Only available for video inventory
  • For Network Connections:
    • Requests, shown on the connection and goal real time reporting tabs. Shows the amount of request a goal/connection is receiving.
  • For RTB (programmatic):
    • RTB Invalidated, shown on the real time reporting tab of programmatic buyer, shows the amount of times a programmatic buyer has been invalidated.
    • RTB Losses, shown on the real time reporting tab of programmatic buyer, shows the amount of times a programmatic buyer has lost.
    • RTB Second, shown on the real time reporting tab of programmatic buyer, shows the amount of no times a programmatic buyer has come in second place to a winning bid.
    • RTB No Bids, shown on the real time reporting tab of programmatic buyer, shows the amount of no bids a programmatic buyer has received.

 

Documentation Releases

 

This release includes the following documentation update: PDF.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Community Manager
Posts: 89
Registered: ‎04-08-2014

2015-12-17 Release

2015-12-17 Release

Pulse SDK for HTML5 and many other SDK improvements

 

Pulse SDK for HTML5

 

In our new range of SDKs, a new Pulse SDK for HTML5 is available, which simplifies integrating with Pulse significantly. The Pulse SDK defines a strict and simple communication protocol, allowing developers to quickly build simple event driven integrations. The Pulse SDK automatically manages:

  • ad tracking,
  • error handling,
  • and prompting the video player to play ads.

 

The HTML5 Pulse 2.x SDK is available for download on the Mobile and Client SDKs page, under the Ad Products heading.

 

A sample integration is found on github.com/ooyala.

 

 

Secure Tracking URLs Required for Secured Ad Serving in HTML5 2.x SDK

 

In case you want to securely serve ads to your HTML5 player, you may also want to only allow secure tracking. For this use case, if you initiate the ad requestor in your HTML5 integration with a secure host URL (HTTPS), then the SDK dictates that only secure tracking URLs may be used on your site by default.

 

To override this new security functionality, you must set the ignoreSecure parameter in the adRequesterSettings to 'True'.

 

 

Improved Progress Tracking on Creatives in HTML5 2.x SDK

 

Previously, to track the progress of a creative, you would use the trackVASTProgress method which required you to know what the offset was and pass it in as a string. This functionality has been simplified with a new method called trackProgress, which only needs you to pass in the elapsed time of the creative.

 

The old method is still available to ensure that existing integrations do not break. For new integrations and upgrades, we recommend the new method.

 

 

Survey Element available in HTML5 2.x SDK and Android 2.x SDK

 

The optional VAST (Video Ad Serving Template) survey element is used to store the URI to a survey vendor that could be the survey, a tracking pixel, or anything to do with a survey. The element could be used to display a survey accompanying a specific ad, when that ad is served to the viewer, or the survey might only be activated if the viewer has paused ad playback. For each ad served, there is at most one survey URI available.

Now, the survey element is exposed through the HTML5 and Android 2.x SDKs, which enables customers to handle this element in their integration when it comes in with ads from 3rd party ad providers.

 

For the HTML5 2.x SDK, the survey element is accessed through Ad.survey.

For the Android 2.x SDK, the survey element is accessed through Ad.getSurvey().

 

 

Ad Variant Property Available in iOS 2.x SDK and Android 2.x SDK

 

The ad variant property tells you if an ad is a sponsor ad or not. In case of a sponsor ad, you may want to announce first that the following show is sponsored by the company in the ad. Now, the ad variant property is exposed through the iOS 2.x SDK and Android 2.x SDK.

For the iOS 2.x SDK, the ad variant property is accessed through VPAd.variant.

For the Android 2.x SDK, the ad variant property is accessed through Ad.getVariant().

 

 

Documentation Releases

 

This release includes the following documentation updates:

The SDK documentation for all the features above is found at Ad Products SDK API Documentation.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."
Community Manager
Posts: 89
Registered: ‎04-08-2014

2016-01-11 Release

2016-01-11 Release

 

Pulse Ad Serving improvements

 

Global tracking pixel

External tracking by systems other than the Pulse tracking, has been available on a per-ad basis to satisfy the advertiser's 3rd party tracking needs. Now, customers/publishers also have the ability to set up external tracking over all their campaigns and ads, through the global tracking pixel. All events available in Pulse, for example impressions, clicks and quartiles, can be tracked in this way.

 

pulse_settings_global_tracking.png

 


All added global tracking pixels work retroactively, which means that the tracking is applied to all ads that were already active before the tracker was added.

 

To start using this feature, open the Settings in Pulse, select the Global Tracking tab, and click Add External Pixel Tracker. The URLs may contain macros, which are described on the Ooyala Pulse Macros page.

 

 

Duplicating goals

Pulse now offers you the ability to duplicate goals within a campaign. The duplicate goal:
  • has the same attribute values, like start and end date, as the original,
  • contains the same ads as the original,
  • and the ads are automatically inactivated to prevent the goal from running immediately.

The name of the duplicate goal is set as original goal name - Copy, but can be changed before actually duplicating the goal.

 

pulse_goal_duplicate.png
 

Select-All devices option for Ad creation

The new Select-All option in the Add new ad for goal "XXX" page enables you to select all device and service categories defined for your account in one go. Selecting this option marks all other categories automatically, which may be particularly handy if you need to exclude only one option.

 

pulse_create_ad_select_all_option.png

Documentation Releases

 

This release includes the following documentation updates:

Global Tracking section added to Settings.

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2016-01-15 Release

[ Edited ]

2016-01-15 Release

 

Pulse new and improved forecasting functionality

 

New Planner with Improved Forecasting

Warning: The following features are not automatically rolled out to all customers! A staged rollout plan is being created and customers will be notified well in advance of when they are scheduled to transfer to the new planner and forecasting.
 
 

New Planner

The planner enables you to simulate inventory and campaign delivery. The planner runs inventory forecasts, which are predictions of future conditions based on past and present data.

Now, with the new planner, you can:

  • simulate inventory separately from campaign simulations.
  • have multiple simulations.
  • create new simulations based on the parameters of an older simulation in the list.

 

pulse_new_planner.png

 

 

The campaign simulation reports, specifically, give you information about all the competing campaigns. This list contains links directly to the competing campaigns to easily adjust them if necessary.

 

 

Improved Forecasting

The new planner also uses a new forecasting engine, which employs a simulation based forecasting approach, as opposed to a calculation or mathematical model based approach. This means that the forecasting engine simulates ad delivery by fast-forwarding the same ad decisioning engine, which will later deliver the ads, through a future inventory based on historical user data. The result is more realistic and accurate than a traditional calculation or mathematical model based approach.

 

 

Campaign & Goal Progress Bar

The new forecasting engine is also used for projecting delivery for running campaigns and goals and is visualised on the Campaign Overview page in the form of the progress bar on each campaign and goal.

 

pulse_campaign_progress_bars.png
 
 

Documentation Releases

 

This release includes the following documentation updates:

For more information about the new planner and forecasting engine, refer to Planner in the Ooyala Pulse User Guide

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2016-01-21 Release

2016-01-21 Release

 

tvOS and iOS SDK contain bitcode, new customer portal, and more ...

 

 

tvOS and iOS SDK Contain Bitcode

 

To be able to release tvOS applications on the Apple Store you are required to include bitcode in your app binary. Any libraries the application uses must also include bitcode. From v2.1.16.1.1 onward, the tvOS SDK contains bitcode.

 

Although the same requirement does not apply to iOS applications, from v2.1.16.1.1 onward, the iOS SDK also contains bitcode.

 

For more information about bitcode, refer to the following Apple Developer article:https://developer.apple.com/library/tvos/documentation/IDEs/Conceptual/AppDistributionGuide/AppThinn...

 

 

New Customer Portal 

 

The Ooyala Support team is pleased to announce the release of our new Customer Portal, unifying support portals across Ooyala's products. The old Zendesk support portal will be phased out completely by February 15th, 2016.

 

For more information regarding the new portal, and how to sign up, refer to the following article: http://community.ooyala.com/t5/Information-News/Our-new-Support-Portal-is-now-available/td-p/7908

 

 

New Macro for Ad URL

 

Macros are used in the Pulse UI when adding third party tags and external tracking links. The macros are resolved into values when the tags or links are added to an ad response. 

A new macro, called [ad.sourceURL], is available, which enables you to send the precise URL of a served ad to any external tracking system. This URL, in turn, allows you to view the ad for verification or classification purposes without generating tracking events.

 

 

Hide FTP Password in Pulse UI

 

The FTP password on the Account Settings tab in the Settings window is now hidden by default to further improve our SOC2 compliance. To view the password, click the Show FTP password button.

 

pulse_show_ftp_password.png

 

 

Fix for Underestimation in Inventory Simulation

 

Due to a bug in how inventory was simulated using the new forecasting engine, certain customers who have a larger number of positions (4 or more) for ads in their ad breaks were seeing too low numbers of total, used, and available inventory. This bug is now fixed and will result in seeing more total, used, and available inventory when running simulations. The increase in total inventory may be up to 400% of previously simulated numbers, depending on your account settings and simulation parameters. The increases in used and available may be more dramatic and can range up to 10 times previous forecasts.

 

Affected customers may be those who:
  • are using the new forecasting engine already.
  • have set a larger number of positions (4 or more) for ads in their ad breaks.

For more information regarding the release and roll out of the new planner and associated new forecasting engine, refer to New Planner with Improved Forecasting release note.

 

 

Documentation Releases

 

This release includes the following documentation updates:

Refer to the Changelog Document for tvOS and iOS SDKs at: http://pulse-sdks.ooyala.com/ios_2/latest/docs/Changelog.html

For more information about macros, refer to the following Community Knowledge Base article: Ooyala Pulse Macros

 

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2016-02-04 Release

2016-02-04 Release

 

Logging on Pulse SDKs & HTML5 Core SDK adParameters

 

Logging enabled in HTML5, iOS and tvOS Pulse SDK

Previously, your integration with Ooyala Pulse using one of the Pulse SDKs was not able to get log messages. Now, new methods are available to create a log listener, which picks up any error and warning messages.

 

These messages relate to, for example:

 
  • Problems in network responses, which may be caused by a misconfigured Pulse account or third party servers.
  • Network request failures, like a failure to get the a requested session from Pulse.
  • VAST responses from third party servers that do not conform to the VAST standard.
  • Coding mistakes in the integration, like a missed argument or wrongly typed argument.
  • And so on.

 

These messages help you debug your integration during development, and help you identify any issues that may occur in production.

 

The new methods are:
 
  • HTML5: OO.Pulse.setLogListener
  • iOS & tvOS: OOPulse.setLogListener

 

VPAID 2.0 enabled in HTML5 Core and Pulse SDKs

In order to handle VPAID 2.0 ads in your video player, you need access to the <AdParameters> element in the VAST response. In the HTML5 Core and Pulse SDKs, we now expose this element through the adParameters method on the creative.

 

 

Documentation Releases

This release includes the following documentation updates:

Refer to the Changelog Document for HTML5 Pulse SDK at: http://pulse-sdks.ooyala.com/pulse-html5/latest/

Refer to the Changelog Document for iOS & tvOS Pulse SDK at: http://pulse-sdks.ooyala.com/ios_2/latest/docs/Changelog.html

Refer to the Changelog Document for HTML5 Core SDK at: http://pulse-sdks.ooyala.com/html5_2/latest/

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!
Posts: 1,241
Topics: 170
Kudos: 107
Blog Posts: 78
Ideas: 3
Solutions: 38
Registered: ‎08-20-2012

2016-02-11 Release

2016-02-11 Release

 

Ad info available in ad error events on Flash SDK, new Pulse SDK for Android

 

 

Ad info available in ad error events on Flash SDK

Previously, information about the ad was passed along with any tracking error events (TRACKING_ERROR_EVENT) in the Flash SDK. Now we have extended the same functionality when ad error events (AD_ERROR_EVENT) are sent. This allows you to extract more specific information about the ad that caused an error, like the ad ID, URL, format, and so on.

 

 

Pulse SDK for Android

In our new range of SDKs, a new Pulse SDK for Android is available, which simplifies integrating with Pulse significantly. The Pulse SDK defines a strict and simple communication protocol, allowing developers to quickly build simple event driven integrations. The Pulse SDK automatically manages:

  • ad tracking,
  • error handling,
  • and prompting the video player to play ads.

 

The Android Pulse 2.x SDK is available for download on the Mobile and Client SDKs page, under the Ad Products heading.

A sample integration is found on github.com/ooyala.

 

 

Documentation Releases

This release includes the following documentation updates:

More information about the AD_ERROR_EVENT is located at: http://pulse-sdks.ooyala.com/flash/latest/

 

The Android Pulse SDK documentation is located at: http://pulse-sdks.ooyala.com/android_2/latest/

Please show your appreciation to others. If someone helps you, don't forget to give them Kudos by clicking the star button next to their post. If a post answers your question, please mark it as an "Accepted Solution."




Check out our latest Ooyala Engineering Blog!