mraid.open() call as a reasonable inference (see below) rather than a line quoted from Digital Turbine's spec — worth confirming with a DT Exchange contact before a large campaign.
DT Exchange's playable ad type, confirmed
Digital Turbine publishes an "Ad Types and Specification" reference at docs.digitalturbine.com that lists Rewarded Playable alongside Rewarded Video and Interstitial Display as a distinct creative type. Pulled directly from that page:
- Placement: Full Screen, delivered as a Modal placement.
- Duration cap: 30 seconds maximum.
- Content format: HTML / MRAID 2.0, VAST 2.0 — a standard MRAID 2.0 creative, not a proprietary DT wrapper.
- Close behavior: a DSP can call MRAID 2.0's
useCustomClose()to show its own close UI early. If that's detected, the DT SDK still forces a fail-safe Close button at the 30-second mark, so a user can never get stuck.
How DT Exchange compares to networks PlayableKit already supports
Every network PlayableKit ships to publishes its own click-through call, size expectation, and packaging convention. Seeing DT Exchange next to them is the fastest way to place it in context — and to see exactly where its public docs go quiet compared to the rest.
| Network | Click-through | Published size cap | Packaging rule |
|---|---|---|---|
| Google Ads | clickTag + ExitApi | Yes, published | Flat ZIP, orientation meta tag, <512 files |
| Meta | FbPlayableAd.onCTAClick() | Yes, published | Single self-contained HTML, no external requests |
| AppLovin | mraid.open() | Yes, published | Single self-contained HTML, no external requests |
| Mintegral | window.install() | Yes, published | Archive name, folder, and HTML filename must match |
| TikTok | openAppStore() (Playable SDK) | Yes, published | First-level index.html + config.json |
| Unity Ads | mraid.open() | Yes, published | Standard MRAID package |
| Vungle | postMessage('download','*'), MRAID fallback | Yes, published | Standard MRAID package |
| DT Exchange | Not named by Digital Turbine — PlayableKit uses the inferred mraid.open() | Not published | Single self-contained HTML (PlayableKit's default for unpublished packaging) |
The pattern across every other row is the same: a named CTA function, a stated size ceiling, and an explicit packaging convention, all pulled straight from that network's own spec page. DT Exchange is the outlier — its docs confirm the creative type and its runtime behavior, but stop short of a size limit or a packaging format, which every other network in the table states outright.
What's genuinely unconfirmed, and the reasonable inference
Two gaps are worth naming plainly rather than papering over with an invented number:
- Click-through function: DT's docs don't name a DT-specific CTA method the way Mintegral names
window.install()or TikTok namesopenAppStore(). Since the supported content is standard MRAID 2.0, the click-through almost certainly resolves to the standardmraid.open()call — that's the point of building to MRAID rather than a proprietary API — but that's an inference from what MRAID 2.0 support implies, not a line quoted from DT's spec page. - File size ceiling: no maximum is published for playables. With nothing to build against, the safer move is the general cross-network norm most exchanges converge on — well under 5 MB, ideally closer to 2 MB — and to confirm the real number with a DT Exchange account contact before a large campaign, rather than assume a figure that was never actually published.
For the full breakdown of these gaps alongside a step-by-step guide to adapting a Unity Playworks/Luna export for DT Exchange by hand, see Export Unity Playworks/Luna to DT Exchange — that page covers the workflow; this one is the network reference.
Why DT Exchange shows up in playable strategy at all
DT Exchange sits inside Digital Turbine's mobile ad stack, and for teams running mediation across several exchanges it's often one line item among many rather than the sole destination for a creative. The requirements above matter less as a one-off checklist and more as a baseline: a playable built to strict MRAID 2.0 discipline, with a conservative asset budget and no reliance on a network-proprietary global, tends to survive review on DT Exchange and on stricter, better-documented networks alike. That's the same discipline a Playworks/Luna export already needs for AppLovin or Unity Ads today.
What PlayableKit supports today
From one Playworks/Luna export ZIP, PlayableKit generates network-compliant packages for every network it supports — correct clickTag/MRAID/SDK wiring, asset encoding, and package shape handled per network's actual published rules, DT Exchange included. Its click-through is the one honest exception noted above: an inference from confirmed MRAID 2.0 support, not a function name Digital Turbine states outright, so it's worth verifying directly with a DT Exchange contact before a large campaign.