unity ads playable specs.

Last checked October 16, 2026 against Unity's Grow (Unity Ads user acquisition) documentation

Unity Ads playable specs at a glance

Required code

This follows the bootstrap in Unity's best-practices guide: wait for MRAID, then start only once the ad is actually on screen:

var STORE_URL = /iPhone|iPad|iPod/.test(navigator.userAgent)
  ? "https://apps.apple.com/app/id000000000"
  : "https://play.google.com/store/apps/details?id=com.your.game";

function onViewable(viewable) {
  if (viewable) startGame(); else pauseGame();
}

function onReady() {
  mraid.addEventListener("viewableChange", onViewable);
  if (mraid.isViewable()) startGame();
}

if (mraid.getState() === "loading") {
  mraid.addEventListener("ready", onReady);
} else {
  onReady();
}

installButton.addEventListener("click", function () {
  mraid.open(STORE_URL);
});

Unity attributes starts, views and clicks on its servers, so you don't need tracking calls. Unity's docs don't ask for a mraid.js script tag, since the webview injects MRAID.

Standalone playable or playable end card

• Playable: the whole ad is the interactive demo.
• Video and playable end card: a 15–60 second video, then the playable as its end card. Unity says the playable can start loading with the video, and it must respect isViewable so it doesn't run hidden.

Both run through Unity's rewarded and interstitial ad units and use the same single-file spec.

Moderation checks

Every new creative pack is reviewed by a person at Unity, and packs stay Pending until the organization has added funds. Moderators check that:

• the content scales to the screen and doesn't break when the device rotates
• the install button is easy to reach, not covered, and goes to the right store
• the iOS mute switch turns sound off, and locking the screen stops it
• the code is minified and there are no errors in the console
• it runs smoothly, without stutter or pixelated art
• it plays for a reasonable length before the end screen and isn't too hard for its audience
• it makes no unnecessary network requests

It also needs to run on Android 4.4+ and iOS 9+.

How to test a Unity playable

1. Host the HTML at a URL ending in .html (HTTPS for iOS), or upload it to a playable creative pack in the Unity dashboard.
2. Install Ad Testing for Unity Ads (iOS, Android).
3. Use Show QR code in the dashboard, scan it, and play the ad in Unity's own webview. Rotate the phone, flip the mute switch and lock the screen while it plays.

Why Unity rejects playables

Unity's “Rejected” status page names these as the common causes:

• The ad doesn't work properly when switching between portrait and landscape.
• Sound doesn't stop when the screen locks, or doesn't come back on unlock.
• Sound ignores the iOS mute switch.
• The content breaks Unity's advertising content policies.

Failing the moderation checks above (file size, unminified code, console errors, an obstructed install button) also gets packs rejected. Hover over a rejected pack's name in the dashboard to see why.

Common questions

Sources

Networks change their specs without notice. These are the pages this summary was checked against. If anything here disagrees with them, follow the network.

• Unity Grow: Playable asset specifications
• Unity Grow: Playable best practices
• Unity Grow: Playable end cards
• Unity Grow: Test creative packs
• Unity Grow: Moderation checks
• Unity Grow: Rejected creatives
• Unity Grow: Ad format references