SDK 6.8 Changes & Enhancements for Buyers

Exciting features and enhancements are available to our buyers using Oath SDK 6.8

Most Recent Changes and Enhancements

VAST 3.0: SSP supports VAST 3.0, which provides buyers with new creative opportunities and opens up more video-enabled inventory on the marketplace.

End Cards: With VAST 3.0, we support the use of companion ads as end cards. 

Native: SSP’s approach to native ads effectively marries supply and demand without sacrificing quantity of inventory or quality of ad experience.

Feature Overview

Recognizing Requests from the SDK

The SDK version will be passed on the bid request in the displaymanagerver' attribute. Requests coming from SDK 6.0.0+ will be displayed as 6.8.0-commithash (where commithash is a short string of characters). Future SDK releases will follow the same format.

HTML Creative Formatting

SDK 6.8 does not center align HTML creatives within webviews as doing so could potentially interfere with the intended functionality of the creative. You must format creatives as they are to appear. 

In addition, we do not apply styling to HTML creatives. You must format creatives exactly as they are to appear in the full screen ad space.


SSP does not block iFrames. Due to the complexity of delivering iFrames in mobile environments we recommend you avoid using them. If iFrames cannot be avoided, follow the best practices listed below when using them with SDK 6.8.

  • SDK 6.8 will not inject the mraid namespace into the iframe, only the top-level window will have the mraid namespace. Therefore, if you want to access mraid from within your iframe, the iframe must be on the same domain as the top level window and you will need to access mraid using “”. Your iframe will be on the same domain as the top level window unless you set the src attribute on the iframe.
  • Use mraid.expand() to expand the creative’s container to full size. For example, if the creative is in a 320x50 placement and the user taps the banner to expand, simply resizing the iframe to the full size of the screen without calling mraid.expand() will result in only a 320x50 portion of the creative being visible to the user.

MRAID Viewable Flag 

Oath's SDK 6.8 supports VAST 3.0 which is backward compatible with VAST 2. The SDK 6.8 updates related to VAST are

Valid Video Formats - The only valid video format for SDK 6.8 is MP4. No other video formats will be considered.

Bitrate Logic - The valid bitrate range is 400-1200 kbps for wifi and 400-800 kbps for cellular networks. Our SDK will pick the highest bitrate video within a given range. We recommend having a video that falls within the 400-800 and 800-1200 range for the best end-user experience.

End Cards - SSP supports end cards on the marketplace. Supported companion ads for the end card include: static resource (image), iframe, and HTML content. The minimum size static resource companion ad is 300px x 250px.

Static resource companion ads may (optionally) use a background color for letterboxing. The custom extension, in the form of XML attribute "backgroundcolor=", allows the VAST to dictate a background color.

In SDK 6.8 ad markup and resources are pre-fetched (most common for interstitial placements) and will fire off a traditional tracking pixel on each occurrence. Ensure accurate tracking of display-counts and matching of marketplace delivery counts by utilizing the MRAID viewable status to determine when an ad has been delivered.


 <script src="mraid.js"></script>
   <script type="text/javascript">
    var ts_displayed = false;

    function ts_init() {
        if (window.mraid && window.mraid.getState && window.mraid.addEventListener) {
            if (window.mraid.getState() === 'loading') {
               window.mraid.addEventListener('ready', ts_ready)
           } else {
       } else {

   function ts_ready() {
       if (window.mraid.isViewable()) {
       } else {
           window.mraid.addEventListener('viewableChange', ts_view)

   function ts_view(viewable) {
       if (viewable == true || 'true') {

   function ts_callDisplay() {
       if (!ts_displayed) {
           ts_displayed = true;
           var displayUrl = "";
           var xhr = ts_getXMLHttpRequest();
 "GET", displayUrl, false);

   function ts_getXMLHttpRequest() {
       if (window.XMLHttpRequest) return new XMLHttpRequest();
       else return new ActiveXObject("Microsoft.XMLHTTP")
Have more questions? Submit a request