applovin playable ad specs.

Last checked October 16, 2026 against AppLovin's creative specs and Playable Preview

AppLovin playable specs at a glance

Required code

AppLovin's SDK provides the mraid object. Don't touch MRAID or size the layout until it's ready, then send every install tap through mraid.open():

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 start() {
  layout();          // size for the current orientation
  installButton.addEventListener("click", function () {
    mraid.open(STORE_URL);
  });
}

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

AppLovin doesn't say whether to include a <script src="mraid.js"></script> tag. Most AppLovin playables include it in the head; the SDK supplies the file either way.

Gameplay and sound rules

• The first tap plays. It must never open the store. Only a deliberate tap on an install button or the end screen should.
• No auto-redirect. The playable can't open the store or a landing page on its own, on load or on a timer.
• Timers start at the first interaction, not when the ad loads.
• Sound stays muted until the first interaction, and stops when the ad is closed or hidden.
• Load fast. AppLovin says the ad must become interactive “in a reasonable time frame”. Inlining everything helps; keep the first frame light.
• WebGL needs a fallback. If the context fails or is lost, show a UI fallback instead of a black screen.

Optional: AppLovin playable analytics

AppLovin can report how far players get if the playable sends events. It's optional; if you use it, DISPLAYED is required:

function track(name) {
  if (typeof window.ALPlayableAnalytics !== "undefined") {
    window.ALPlayableAnalytics.trackEvent(name);
  }
}

track("DISPLAYED");
track("CHALLENGE_STARTED");
track("CHALLENGE_PASS_50");
track("CHALLENGE_SOLVED");
track("CTA_CLICKED");
track("ENDCARD_SHOWN");

AppLovin says the events aren't meant for playables with fewer than three interactions or no challenge. COMPLETED is deprecated.

How to test an AppLovin playable

1. Open AppLovin Playable Preview and upload the HTML file, or paste a URL to a hosted copy.
2. Play it, rotate it with the Rotate control, and tap install. You should see “You have successfully clicked.”
3. Scan the QR code with the Playable Preview app (iOS, Android) and play it on a real phone. Redirects there only confirm that one happens when expected.

Why AppLovin rejects playables

AppLovin reviews creatives automatically; a failing one shows Rejected in the Media Library and can't be added to a creative set. It doesn't publish a list of reasons, but its spec makes the usual ones clear:

• Over 5 MB, or more than one file.
• A web font, CDN library, analytics call or any other network request.
• The CTA uses window.open or a link instead of mraid.open().
• The first tap opens the store, or the ad redirects on its own.
• Sound before the first tap.
• Broken or cropped in one orientation.
• MRAID calls before ready, which can leave a blank ad on some devices.
• Misleading designs and other breaches of AppLovin's demand partner policies.

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.

• AppLovin: Creative specs and guidelines
• AppLovin Playable Preview
• AppLovin: Playable analytics integration
• AppLovin: ORTB creative types (programmatic buyers)
• AppLovin: Can't add a creative to a set
• AppLovin: Demand partner policies