Working with millrace
What Is a Playable Ad? Structure and Specs
A playable ad is a short, interactive demo of a mobile game or app that runs inside an ad. Instead of watching a video, the viewer plays a small piece of the product for a few seconds, then gets a button to install it. Technically, it is a self-contained HTML5 document that an ad network loads in its own container.
We build playable ads for a living, so this guide sticks to what holds up in production: how a playable is put together, where it runs, what the networks actually accept, and the problems that only show up once a real file meets a real container.
How a playable ad is structured
Almost every playable has the same three parts.
- The hook. The first seconds show what to do, usually with a hand or arrow prompt. We aim for the first meaningful interaction within 3 seconds: if nothing invites a touch by then, most people are gone.
- The play. One core mechanic, simplified from the real game: drag to aim, tap to match, swipe to sort. We recommend a single mechanic, because every extra one adds production time and makes the first seconds harder to read.
- The end card. A short result (“Level complete”) and the call to action that opens the store page.
The whole experience usually lasts 15 to 30 seconds. Those are creative targets rather than hard limits, but networks and buyers both reward short. A playable is not the full game. It recreates the moment that makes the game worth installing.
What a playable ad is, technically
A playable is a web page with strict rules:
- Self-contained. Code, images, sounds and fonts are packed into the file. AppLovin, for example, prohibits external resources: everything must be embedded.
- Small. Most networks cap a playable at around 5 MB. For scale, our Sneaksup brand demo is a canvas build authored at 540 × 960, and it comes to 4.5 MB. Image and audio budgets decide whether a concept fits.
- Wired to the network. The call to action is not an ordinary link. Each network gives the ad its own way to open the store, and the playable must call it, or the install button does nothing.
These are the delivery specs we work to today:
| Network | Format | Size cap | Call to action |
|---|---|---|---|
| AppLovin | Single HTML | 5 MB | mraid.open() |
| Unity (ironSource) | Single HTML | 5 MB | mraid.open() |
| ZIP | 5 MB | ExitApi.exit() |
|
| Meta | Single HTML or ZIP | 2 MB (HTML) / 5 MB (ZIP) | FbPlayableAd.onCTAClick() |
| Mintegral | ZIP | 5 MB | window.install() |
Networks revise these specs, so check the current version before production. We confirm the exact placement requirements for each project. MRAID, which appears in two rows, is the standard interface many in-app ad containers expose to the ad. AppLovin requires MRAID 2.0 support.
Most networks add behavior rules too. AppLovin’s are typical: sound stays muted until the first interaction, the ad must not send people to the store on their first tap, and it must work in both portrait and landscape.
Where playable ads run
Playables are built for app installs, so they appear wherever install campaigns buy space:
- Inside other apps and games. Interstitial and rewarded placements served by networks such as AppLovin, Unity (ironSource), Mintegral, Liftoff (Vungle) and Chartboost. Rewarded placements suit playables especially well, because the viewer has chosen to engage.
- Meta. On Facebook, a playable starts with a short lead-in video and a “Tap to try” prompt, then opens full screen. On Instagram, only the lead-in video is shown. On Audience Network there is no lead-in, and the playable runs in interstitial and rewarded slots.
- Google. In App campaigns, HTML5 and playable assets can serve on the Google Display Network, and they are billed per engagement: the first interaction with the ad.
Why advertisers use them
A video shows a game. A playable lets someone try it, and that changes who installs. Someone who has already played the core loop knows what they are getting, so installs from playables tend to come from people who liked the mechanic, not just the trailer. Playables are also good test material. Changing one variable, such as difficulty, the first prompt or the end card, gives a clear signal about what your audience responds to.
No format guarantees results, and we don’t promise CTR, CPI or ROAS figures for any creative. That’s why we start projects with several working concepts instead of one: you put real versions in front of your own audience, and the numbers pick the direction.
Three things that break playables, and what we changed
These came from our own builds, not from a spec sheet. They are the kind of problem that passes every local test and fails in a real container.
Fractional frame sizes create scrollbars. A container sized with CSS aspect-ratio can be fractional, for example 393.27 × 700.40 px. Inside the frame, window.innerWidth and innerHeight are whole numbers that round up, so the creative drew a 394 × 701 canvas into a 393 × 700 document. Two scrollbars appeared, the creative refitted to the smaller space, overflowed again, and settled at a 378 px play area with a scrollbar through the end card. Ad containers size from those same two properties, so treat this as normal and test at fractional sizes. On our own pages we fixed it with scrolling="no" on the iframe.
A sandboxed frame can break the store link. When a playable has no ad container around it, for example in a web preview, many creatives fall back to opening the store in a new window. A popup from a sandboxed iframe inherits the frame’s restrictions unless allow-popups-to-escape-sandbox is granted. Without it, the store opened in a tab where nothing could be tapped or submitted. If you preview playables on your own site, grant that token.
iOS cancels drags that aren’t perfectly straight. We first reasoned that touch-action: pan-y would keep a horizontal drag mechanic working on phones. It did on Android. On iPhone, WebKit reclassified any drag that drifted a few degrees as a page scroll and cancelled it within about a second, so the mechanic died mid-play. The fix was to take the whole gesture while a round is in progress. The lesson: test drag mechanics on a real iPhone before you sign anything off.
How to get a playable ad made
You need three things before production starts: the product (store link or build), the networks you will run on, and either an idea or the freedom to explore. If you know exactly what you want, a defined idea can be built directly. If you don’t, we develop several working concepts around your product, you play them and pick, and we finish the ones you choose for your networks.
- See the services and the network requirements on Services.
- See how a project runs, step by step, on Process.
- See what each package includes and costs on Packages.
- Play finished demos in your browser on Portfolio.
Sources
- AppLovin: Best practices & guidelines
- Meta for Developers: Playable Ads for Mobile Apps
- Google Ads Help: About HTML5/Playable ads for App campaigns