mintegral playable ad specs.

Last checked October 16, 2026 against Mintegral's help center and the Mindworks playable guideline

Mintegral playable specs at a glance

Required code

Mintegral injects its functions into the page, so guard every call with window.x &&. That keeps the file working in a plain browser too:

// once every asset has loaded
window.gameReady && window.gameReady();

// every install button, including the one on the end screen
installButton.addEventListener("click", function () {
  window.install && window.install();
});

// when the player wins or loses
function showEndScreen() {
  window.gameEnd && window.gameEnd();
  // ...
}

// Mintegral calls these two itself
function gameStart() { /* start the timer and the music */ }
function gameClose() { /* stop the music */ }

// only if the playable has a replay
function replay() {
  window.gameRetry && window.gameRetry();
}

The HTML needs html, head and body tags and a UTF-8 charset. Mintegral's guideline recommends this viewport:

<meta name="viewport" content="width=device-width,user-scalable=no,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0">

For custom tracking, add an action.json at the root and call window.HttpAPI.sendPoint("action&action=" + n) for up to five actions.

The naming rule that fails most uploads

The zip, the folder inside it and the HTML file must have exactly the same name:

tiles_v2.zip
└── tiles_v2/
    ├── tiles_v2.html
    └── game.js        (JS may stay separate; everything else is base64)

Use only letters, numbers and underscores. A hyphen or a space in any of the three fails the test tool with “The names of html, folder and the zip file need to be the same.”

Design rules

• Keep an install button visible for the whole playable, and show one on the end screen with an effect that draws the tap.
• Every link to the store or a web page goes through window.install(). The playable must never redirect on its own, on load or on a timer.
• Build an end screen. The game has to finish, and gameEnd() must fire on every path a player can take.
• Make it work with a mouse. The test tool runs in a desktop browser, so swipes and taps must also work as clicks and drags.
• No fake close buttons, fake progress bars, misleading countdowns or audio designed to startle. These break Mintegral's creative policy.

How to test a Mintegral playable

1. Open the Mindworks Playable Test Tool (mindworks-creative.com/review redirects there). No login needed.
2. Upload the zip and play it all the way to the end, then tap the install button.
3. Every row (HTML requirements, CTA, Game Ready, Game End and the rest) must turn green. “Undetected” on Game End usually means you didn't reach the end, or one path skips the call.
4. Check the portrait and landscape previews, and the in-app test via the QR code.

After you submit, Mintegral's QA takes 3–5 business days. Auto-redirects aren't caught by the tool, so they surface here.

Why Mintegral rejects playables

• The zip, folder and HTML names don't match, or use characters other than letters, numbers and underscores.
• The zip is over 5 MB, or the upload isn't a zip.
• window.install(), gameReady() or gameEnd() is never called.
• Images, audio or fonts are loaded as files or from the web instead of base64.
• The playable redirects without a tap.
• A touch-only control the desktop test tool can't trigger.
• A custom close button or loading screen, or code that overrides console.

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.

• Mintegral help center: Playable test guide
• Mintegral help center: Asset specs
• Mintegral help center: Creative policies
• Mindworks playable guideline
• Mindworks Playable Test Tool