What is MRAID 2.0?

Mobile Rich Media Ad Interface Definitions (MRAID) is the common API (Application Programming Interface) for mobile rich media ads running in mobile apps. This is a standardized set of commands, designed to work with HTML5 and JavaScript, used by developers creating rich media ads to communicate further functionalities to occur within the apps into which they are being served (expand, resize, access device functionalities such as the accelerometer, swipe, etc.).

In terms of displaying HTML Ads, the Ad View Container, an MRAID-compatible container, must display any HTML ad. The container invokes an HTML with JavaScript rendering engine for rendering ads. The engine is called the "web view". Whenever possible, the web view does not define ad sizes (dimensions) or how ads move or change in response to user interaction.

DT SDK supports MRAID 2.0 according to the IAB MRAID 2.0 specification.

MRAID 2.0 in Bid Request and Bid Response

  • How to identify if MRAID 2.0 is supported based on the Bid Request?
    “banner.api” : 5 when MRAID 2.0 is supported.
  • How should a demand partner respond with an MRAID 2.0 ad in the bid response?
    The bid response should include “bid.ext.crtype” : “MRAID 2.0”.

Media File Limits

  • For interstitial MRAID 2.0 ads, it is best to only return an ad markup with an ad size of 320x480 or 480x320.
  • If the ad size is not 320x480, DT scales up or down to 320x480 and center on the screen. The same applies for 480x320.

How is a Click Event tracked on MRAID 2.0?

  • The click tracking URL is fired (triggers the JS click event) upon event.
  • The creator of the MRAID 2.0 ad markup determines when the event is triggered.

Close Button

DT's close button appears on the top right corner immediately, unless the DSP leverages the useCustomClose() method. 

MRAID Support Methods

To ensure the user experience flow renders as expected, please test your creatives with our test app. 

  • SMS - If the device supports using the SMS: protocol to send an SMS message, DT will support this
  • Calendar - DT's SDK will try to open the calendar.
  • storePicture - This feature has been removed. 

Best Practices on useCustomClose()

  • DT supports useCustomClose() on all MRAID 2.0 inventory, when initiated by the partner.
  • To initiate custom close, partner must useCustomClose() per MRAID 2.0 spec.
  • Partners are allowed to delay the close button show for up to 5 seconds with customClose.

Does Digital Turbine Support MRAID Video?

Not currently, but this is on our product roadmap. 

Back to Top ⇧