Rewarded Playables

Rewarded Playables are full‑screen ads showing interactive app content that users can try before downloading. Users must agree or opt in to the reward terms in order to view and interact with the ad. Rewarded Playables should always include a clear call to action (CTA) that encourages users to download or further engage with the app. Rewarded Playables can be a way to discover high-intent users interested in your app.

Playables on DT Exchange follow MRAID 2.0 or HTML ad protocols with the following additional specifications:

• Placement Type: Rewarded Playables use the Rewarded placement type.

• Playables can appear in either portrait or landscape orientation.

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

• VAST and MRAID 3.0 are not currently supported.

Identifying Rewarded Playable Inventory

In a bid request, the following attributes indicate a request for a Rewarded Playable ad:

• imp.instl: A value of 1 indicates that the ad is interstitial or fullscreen, which may be a suitable placement for Rewarded Playables.

• banner.battr: A value of 13 indicates OMITTED, and therefore Interactive/Embedded Games are allowed, suggesting support for Rewarded Playables.

• banner.api: A value of 5 indicates support for MRAID 2.0. While Rewarded Playables do not necessarily need to follow MRAID protocol, this is a potential indicator of support for interactive ad formats.

• banner.ext.rewarded: A custom extension flag. A value of 1 indicates that the inventory supports Rewarded Playables.

Specifying Rewarded Playables in a Bid Response

To ensure your Rewarded Playable is served, include the following values in your 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.

If your bid response does not contain these values, DT does not serve your ad as a Rewarded Playable.

Rewarding Users

DT facilitates rewards for completing Rewarded Playables in the following ways:

• When the user closes the ad, the DT SDK sends a completion event, and the publisher is responsible for rewarding the user. For more information, see Closing Rewarded Playables.

• DT reports completion events as part of the Rewarded Completions and Completion Rate metrics in the DT Dynamic Reports. Use these metrics to track and analyze your ad performance. For more information, see Reporting for Buyers.

Closing Rewarded Playables

After 30 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). If DT detects the custom close function and it does not display, DT enables fail-safe close functions that appear after 30 seconds.

Rewarded Playables FAQ

Is there a difference between the bid request for Rewarded Video and Rewarded Playables?

Yes. DT sends separate bid requests for Rewarded Video and Rewarded Playables. For more information, see Identifying Rewarded Video Inventory and Identifying Rewarded Playable Inventory.

Can sever-to-server demand partners run Rewarded Playables?

Generally, no. Server-to-server demand partners do not receive the necessary data in the bid request to understand when a request is eligible for Rewarded Playables.

Does DT show a countdown timer on the Rewarded Playables?

No. A countdown timer is not displayed.

What happens when the user returns to the app after visiting the landing page?

The user is returned to the Rewarded Playable ad for the remaining duration.