In this video
- A single HTML file or a ZIP — and what we actually export
- The 5 MB ceiling from Mintegral’s creative asset specs
- window.install(): the store exit, instead of MRAID
- gameReady() and gameEnd(), and why a missing gameEnd gets creatives rejected
- Building and exporting a Mintegral archive end to end
- Opening the ZIP and reading both files
- Uploading in the Mintegral dashboard
About this video
Mintegral does not use MRAID. Its playables exit through window.install(), and the creative is expected to report its own lifecycle with gameReady() and gameEnd() — a missing gameEnd on the win is one of the most common rejections. This tutorial builds a creative, exports it for Mintegral, opens the archive and reads both files, then covers the upload. Every specification quoted is Mintegral’s own, with the source on screen.
Playable Ads Maker — build playable ads and end cards, export to 13 ad networks.
Transcript
Captions in 18 languages on YouTube
In this video you'll build a playable ad for Mintegral - the packaging, the size, and the three JavaScript calls it expects - without writing a line of code.
Mintegral is a mobile ad platform with especially deep publisher inventory across Asia-Pacific, and it is one of the networks that does not use MRAID at all.
It takes either a single HTML file or a ZIP with your resources, up to 5 MB. We export the ZIP: index.html and main.js, with every image already inlined.
Read the full transcriptShow less
5 MB is the ceiling their creative specs publish for a playable.
Now the part that is unlike the others: three JavaScript calls, and your creative is expected to make all three.
The store exit is window.install(). Not mraid.open(), not a redirect.
gameReady() tells Mintegral your playable has finished loading and can be touched.
And gameEnd() fires once, when the round is over.
The Mintegral preset wires all three for you, so the thing to check is that your ad really does end - that something in it reaches a win or a finish, rather than looping forever.
So let's build one. I'll keep it deliberately simple, because the packaging is the subject.
Open Export and pick Mintegral. Your App Store and Play links go here; they are the fallback the creative uses if the container has not provided the install call.
Build it, and what lands is a ZIP with index.html and main.js.
index.html carries your styles and loads the script. main.js is the playable itself.
Uploading happens in the Mintegral dashboard, under creative management. That is their platform rather than ours, so here it is in outline.
Two mistakes to avoid. Exporting another network's file - an MRAID creative has a CTA here that silently does nothing, because Mintegral is not listening for that call.
And shipping a playable that never ends. If nothing in your ad fires game end, Mintegral has no idea the round finished, and that is a rejection you can prevent in the editor.
Build one, unzip it, read both files. Once you know what a compliant creative contains, every network gets easier.
That is Mintegral, end to end. See you in the next video!