> For the complete documentation index, see [llms.txt](https://docs.digitalturbine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digitalturbine.com/dt-ads-demand/ad-creative-types/playables.md).

# 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](https://www.iab.com/wp-content/uploads/2015/08/IAB_MRAID_v2_FINAL.pdf) 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`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#object-imp): A value of `1` denotes interstitial or fullscreen ads.
* [`banner.battr`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#object-banner): A value of `13` denotes OMITTED, which allows interactive and embedded games.
* [`banner.API`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#object-banner): A value of `5` denotes support for MRAID 2.0.

{% hint style="info" %}
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.
{% endhint %}

### Specifying Playables in a Bid Response

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

* [`bid.ext.crtype`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#bid.ext.crtype): To indicate your ad is a Playable creative type, use `Playable`.
* [`seatbid.bid.attr`](https://gitlab.com/digitalturbine/dt-developer-portal/gitbook/-/blob/main/14_exchange_dsp/dt-exchange-openrtb-2.5-specs#object-seatbid): To indicate that your ad is user-interactive or supports embedded games, use `13`.

### Closing Playables

After <code class="expression">space.vars.CloseDisplayTime</code>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](https://www.iab.com/wp-content/uploads/2015/08/IAB_MRAID_v2_FINAL.pdf) `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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digitalturbine.com/dt-ads-demand/ad-creative-types/playables.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.