Rewarded playable / interactive formats: current network support matrix

Editorial collage hero: change-log-rewarded-playable-network-support-matrix

Dated matrix of playable packaging rules from Unity Ads and TikTok help docs; rewarded placement notes where the vendor documents them.

Support matrices drift; midcore operators need a dated matrix before production. This change log reads Unity and TikTok/Pangle documentation only. It is not a full-industry survey of every mediation network.

Unity Ads User Acquisition — playable

Unity playable asset specifications require a single inlined, minified index.html, under 5 MB, MRAID 3.0, both orientations, no blocking of close UI, CTA via mraid.open, wait for MRAID viewableChange before starting content, and no automatic store redirect. Network XHR is generally disallowed except limited analytics without personal data.

TikTok / Pangle — playable

TikTok playable ads help requires a .zip under 5 MB, index.html at first level, config.json with playable_orientation 0/1/2, no mraid.js packaging, no external dynamic loads, no JS redirects, no HTTP requests from the playable, plus Pangle js-sdk access for store open. Pangle asset specifications list Playable as .zip / 5 MB for Interstitial and Rewarded ad formats — the clearest vendor statement that playable can sit in rewarded inventory on that stack.

Matrix (as of retrieve 20 Sep 2026)

Network / surfaceMax sizePackageRewarded noteOwner check
Unity Ads UA playable<5 MBSingle inlined index.html, MRAID 3.0Placement mix is campaign-side; specs are playable-widePlayable producer
TikTok playable<5 MB zipzip + index.html + config.jsonFollow TikTok playable helpUA + creative
TikTok Pangle playable5 MB zipPlayable rowDocumented for Interstitial **and Rewarded**Mediation lead
AppLovin / LevelPlay / othersNot read from the source here—Re-open vendor docs before productionMediation lead

Limits

No ironSource-legacy, AppLovin MAX, Meta or Mintegral pages were read from the source for this matrix edition. Re-check those docs before locking a midcore build. Packaging differences (single HTML vs zip) are breaking changes for production pipelines.

Download the evidence table.

Related posts

When midcore playables should stay out of a network: kill criteria

media buying

playable ads

·

1 min read

When midcore playables should stay out of a network: kill criteria

Rewarded placement map: session minute versus ad load

media buying

playable ads

·

1 min read

Rewarded placement map: session minute versus ad load

Midcore playable: one complete loop before CTA

creative strategy

playable ads

·

1 min read

Midcore playable: one complete loop before CTA