Try for free
Learn/Strategy

How many playables should you test a month?

How many new playables to ship a month by budget and stage, the 70/30 split between variations and new concepts, and how much data each test needs.

Written by Yonathan Avivi, Head of Marketing, Genie Labs

Technical review by Yotam Wolf, CTO · Published Oct 26, 2026 · 6 min read

Ship more.
Learn faster. Monthly volume by budget and stage.

Most studios should plan for three to six new playables a month to start, then scale toward weekly releases as spend grows. AppAgent suggests three to six a month for Meta. At higher spend, practitioners recommend two to three new concepts plus six to ten variations a week per title. The top 20 grossing games ship a median of 64 new playables a month. Whatever the number, split it roughly 70% variations of winners and 30% new concepts, and give each playable enough data before you judge it: about 50 conversions in four days, or 100 in seven.

Key takeaways
Starting point: three to six new playables a month. Scale from there.
Top-grossing games ship a median of 64 a month. That's the ceiling, not the target.
Split output about 70% variations, 30% new concepts. Only about 5% of creatives become winners.
Your budget sets the pace. Each test needs about 50 conversions in four days to read.
Genie Playable makes each variation from the last version, so volume stops being a production problem.

How many playables do top studios run?

WhoVolumeSource
Top 20 grossing gamesMedian of 64 new playables a monthSett, Q4 2025
Whiteout Survival42 playables on AppLovin in one month: 15 concepts, 27 variationsSett, October 2025
Leading games on AppLovin30 to 35 new creatives a week, 10 to 15 of them playablesM&C Saatchi Performance
SocialpointFive to eight playables a month across three gamesAppAgent
Typical recommendation for MetaThree to six new playables a monthAppAgent

How many should I test at my stage?

StageNew playablesMix
First campaignOne or two to launch, one new one by week twoSame hook as your best video
Scaling on one networkThree to six a monthOne or two concepts, the rest variations
Multi-network, steady spendTwo to three a weekAbout 70% variations, 30% concepts
Top-grossing scaleTen or more a weekStructured variation programmes around each winner

A mid-size studio told us they run around 60 playables and 90 videos on one title and still feel they need far more creative volume. Volume grows faster than most teams plan for.

Why the 70/30 split?

Because winners are rare and worth stretching. Playio estimates only about 5% of tested creatives produce meaningful results. Once you have one, variations on it are cheaper and more likely to work than a new idea. Sett found one studio putting 70% to 75% of its playables into deliberate variations of a winning concept and 25% to 30% into new directions. Whiteout Survival gave one winning concept 11 variations in a single month.

The 30% matters too. Without new concepts, every variation eventually fatigues and there's nothing to replace the winner.

Volume without the queue. Genie Playable makes each variation from the last version of your playable: new hook, new ending, new event skin, exported for eight networks. Your team sets the pace, not the dev backlog.

Try it free on your game

How much data does each playable need?

Enough to separate signal from noise. A common rule of thumb is about 50 conversions per creative in four days, or 100 in seven (AppAgent). On AppLovin, practitioners report three to seven days of learning per creative, and advise against pausing by hand too early.

That rule is what links volume to budget. If each test needs 50 conversions and your cost per conversion is $20, each playable needs about $1,000 of spend to read. Ten tests a month means $10,000 of test budget before scaling anything. Run more playables than your budget can read, and you learn nothing from any of them.

How do I keep up with the volume?

·Keep a backlog per winner: three hooks, two difficulty levels, two end cards, the next event skin.
·Tie skins to your LiveOps calendar. Every new event is a ready-made variation.
·Change one thing per version, so each result teaches you something.
·Log results by version, so nobody retests what already failed.
·Fix the bottleneck, not the ideas. "The idea is the easiest part. We have too many ideas," a marketing lead told us. The constraint is how long each version takes to build.

Where does Genie fit?

Genie Playable builds playables from your game (your APK or HTML build plus the assets, narrative and live events in Genie), from a format that's already working, or from a brief. When you need the next variation, your team changes one thing on the last version and exports it again for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral, with Moloco coming soon. Genie Core keeps every version on brand, so the fiftieth still looks like your game. Try it free on your game.

Where to go next

For how to set each test up and how much data it needs, see how to A/B test playable ads. For when to cut, iterate or scale once results are in, see how do you know a playable ad is working.

FAQ

Sources

  1. 01Sett, State of Playables Q4-25
  2. 02Sett, Playable Ads Complete Guide
  3. 03AppAgent, what are playable ads
  4. 04AppAgent, State of Playable Ads 2025
  5. 05AppSamurai, playable ads creative testing
  6. 06M&C Saatchi Performance, AppLovin creative best practice
  7. 07RocketshipHQ, testing creatives on AppLovin
  8. 08Playio, creative fatigue

Keep reading

All articles →
Every winner
wears out. How to iterate before it does.
Playable ads · 8 min read

Your playable is fatiguing: how to iterate a winning playable

Track the tap,
not just the install. The events worth measuring inside a playable.
Playable ads · 8 min read

What to track inside a playable ad

one playable, priced.then come
the variants.
Playable ads · 8 min read

How much does a playable ad cost in 2026?

Ready to ship playables from your game?

Try for freeBook a demo

How to make a playable ad from your own game (without rebuilding it)

Three ways to turn your game into a playable ad: engine export, HTML5 rebuild, or building from your APK. Steps, specs, testing and mistakes to avoid.

Written by Yonathan Avivi, Head of Marketing, Genie Labs

Technical review by Yotam Wolf, CTO · Published Sep 26, 2026 · Updated Sep 26, 2026 · 11 min read

A playable ad from your own game is a 30 to 90 second interactive slice of your game: your characters, your art and one clear mechanic, packaged as a small HTML5 file an ad network can run. You can't ship your game build as it is. Networks cap playables at about 5 MB in a single HTML file or ZIP, with strict rules on code and clicks. So you have three options: export a stripped-down scene from your engine, rebuild the moment in an HTML5 framework, or use a tool that builds the playable from your game's build and assets. This guide walks through all three.

Key takeaways
{{ k }}

What does "a playable ad from your own game" actually mean?

It means the player sees your game, not a generic template with your logo on top. Studios that do this well keep three things fixed and treat the rest as open.

Keep fixedOpen to change
{{ r.ak }} {{ r.av }}{{ r.bk }} {{ r.bv }}

This matches what UA and creative leads tell us. Brand fidelity is non-negotiable. Gameplay is often borrowed from whatever is trending. The catch is policy. The UK ASA now treats even a genuine but non-core mechanic as potentially misleading, and Google Play bans ads that don't represent the app. The closer your playable is to what players actually get, the safer it is, and the better it tends to retain.

Why can't I just ship my game build as a playable?

Ad networks run playables inside their own ad containers, not as apps. Every playable has to fit this box:

SizeAbout 5 MB on every major network (AppLovin, Meta, Google, TikTok, Unity, Mintegral, Moloco, Snapchat). A WebGL export of a real game is usually far bigger. An empty Godot export is already over the limit.
FormatOne self-contained HTML file with every asset inlined (AppLovin, Unity, Moloco), or a ZIP with an index.html (Google, TikTok, Mintegral, Snapchat). Meta accepts both.
No external callsNothing loads from your servers at runtime.
Click-out callmraid.open() on AppLovin and Unity, FbPlayableAd.onCTAClick() on Meta and Moloco, ExitApi.exit() on Google, window.openAppStore() on TikTok, window.install() on Mintegral.
Behavior rulesMuted until the first interaction, no store redirect on the first tap, no auto-redirects, works in portrait and landscape.

The full list lives in our Playable ad specs by network (2026).

What are the three ways to turn my game into a playable?

1. Engine export 2. HTML5 rebuild 3. Build from your APK or HTML and assets
{{ r.k }} {{ r.a }} {{ r.b }} {{ r.c }}

Most studios mix routes: a hand-built hero playable for a launch, and faster tooling for the weekly variations that keep a campaign alive.

What buyers expect to pay and wait: roughly $3,000 to $8,000 and two to four weeks per new playable from an external studio, and roughly $600 to $2,000 in-house once the setup exists. Nobody has a clean source for these numbers, so treat them as market expectations. One mid-size studio we spoke to put it simply: the market norm is "two weeks onwards", and their target is under a week.

Your game is already the brief.

Upload your APK or HTML build. Genie Playable turns it into a playable ad with your own art, characters and live events, ready for 10 ad networks.

Try it free on your game

How do I make a playable ad from my game, step by step?

01\Pick the moment worth playing

Choose one mechanic a stranger understands in three seconds. Good sources: your core loop at its most satisfying, the live event running now, or a format already converting in your genre. If you can't explain the moment in one sentence, it's too complex. One mechanic beats two.

“Merge plus puzzle looks clever and almost always tests worse.”
Segwise

02\Script the arc

Almost every playable follows the same shape:

{{ a.n }} {{ a.k }} {{ a.v }}

03\Prepare your assets

Export characters, backgrounds, UI and sounds from your game, then cut hard. Compress images, use sprite sheets, trim audio to short loops and subset fonts. Base64 inlining adds about a third to file size, so aim for 2 to 3 MB in total and treat 5 MB as the ceiling.

04\Build it

Whatever route you use, keep the logic in plain HTML and JavaScript, make the layout work in 9:16 and 16:9, and keep sound off until the first tap.

05\Package it for each network

This is where engineer time quietly disappears. "A unit that passes on AppLovin can bounce on Unity," as Segwise puts it. Each network needs the right file format, the right click-out call and any required hooks. Mintegral, for example, expects gameReady() and gameEnd() calls. Build once and generate network variants from one source. Hand-editing copies is how bugs creep in.

06\Test before you upload

{{ t.k }}{{ t.v }}

Then test on a real low-end Android phone. A desktop browser hides most of the problems.

07\Launch and measure

Give each playable enough data before you judge it. A common rule of thumb is about 50 conversions in four days, or 100 in seven. Judge on D7 ROAS and retention, not CPI alone. If you can, add events inside the playable (start, first interaction, win or lose, CTA tap, drop-off point), because network dashboards only show the last step.

08\Plan the next version before this one fatigues

Top-grossing games ship dozens of new playables a month, and most of that volume is variations of a winner. Leading teams put roughly 70% of output into variations and 30% into new concepts. Decide now which single thing you'll change next: the hook, the fail state, the character, the event skin or the end card.

What should I keep from my game, and what can I borrow?

Keep everything that helps a player recognise your game after install: art, characters, UI language, sound. Borrow structure freely, whether that's a proven hook, a pacing pattern or a format working in another genre. Racing and narrative studios often tell us their game "isn't playable". The honest read: a playable doesn't need your full core loop. It needs one true moment from your world.

What are the most common mistakes?

Mistake What happens Fix
{{ m.a }}{{ m.b }}{{ m.c }}
The next version, not a new brief.

When a playable fatigues, Genie Playable lets your UA or creative team change the hook, the character or the event skin on the last version and ship it again. No dev queue.

Book a demo

Where does Genie fit?

Genie Playable takes the third route, and adds two more ways in. You can build from your game: your APK or HTML build together with the assets, narrative, mechanics and live events already in Genie. You can start from a format that's already working and rebuild it with your game inside. Or you can start from scratch and describe the playable to Genie Agent.

Genie Core keeps every version on brand, and Genie Playable exports network-ready variants for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral from one source, with Moloco coming soon. No developer is needed at any step, and your team makes the final call on every version. Sign-up is free and covers your first two playables. Try it on your game.

Where to go next

First playable? Follow how to make a playable ad step by step, then run it through the playable ad best practices checklist. Once it's live, read how to know if your playable ad is working and how to A/B test playable ads.

FAQ

{{ f.a }}

Sources

  1. {{ s.n }}{{ s.name }}

{{ a.h1a }} {{ a.h1b }}

{{ a.desc }}

Written by {{ a.author }}

{{ a.meta }}

Ready to ship playables from your game?