Playables

Playables are full‑screen ads showing interactive content that allow users to preview and interact with app content. Playables should include a call to action to encourage users to download or further engage with your app. Playables can also be a key way to discover high-intent users who are interested in your app.

DT Exchange allows Playables that use MRAID 2.0 or HTML ad protocols along with the following features:

• Playables can appear as Interstitial ads in either portrait or landscape orientation.

• End cards can follow Playables. The end card should be part of the ad itself and not require any SDK control.

• For optimal performance, the recommended file size for Playables is 2 MB.

Identifying Playable Inventory

In a bid request, the following attributes specify Playable inventory:

• imp.instl: A value of 1 denotes interstitial or fullscreen ads.

• banner.battr: A value of 13 denotes OMITTED, which allows interactive and embedded games.

• banner.API: A value of 5 denotes support for MRAID 2.0.

Playables do not need to be MRAID. However, if you use MRAID for Playables, use the useCustomClose method to present a Close button within five seconds.

Specifying Playables in a Bid Response

To respond with a Playable ad, include the following values in the bid response:

• bid.ext.crtype: To indicate your ad is a Playable creative type, use Playable.

• seatbid.bid.attr: To indicate that your ad is user-interactive or supports embedded games, use 13.

Closing Playables

After two seconds, DT presents a Close button (for iOS devices) or a Back button (for Android devices). The DSP can override the DT close function by using a custom close function (MRAID 2.0 useCustomClose method) to appear after five seconds. If DT detects the custom close function and it does not display, DT enables fail-safe close functions to appear after 15 seconds.