Try for free
Learn/Strategy

Your playable is fatiguing: how to iterate a winning playable

How long playables last, what to change first when performance drops, and the 70/30 split top studios use between variations and new concepts.

Written by Yonathan Avivi, Head of Marketing, Genie Labs

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

Every winner
wears out. How to iterate before it does.

When a winning playable starts to fatigue, don't replace it. Change one thing at a time, starting with the parts players see first: the hook, then the tutorial hint, then difficulty, then the win or fail moment, the end card, and the skin. Leading studios spend about 70% of their playable output on variations of what's already winning and about 30% on new concepts. On the fastest networks, a playable often gets one to two weeks before performance slides, so the next version should be ready before you need it.

Key takeaways
Fatigue is normal. Practitioners report seven to ten good days on the fastest channels and one to two weeks on Meta.
Iterate the winner before you invent a new concept. Only about 5% of creatives become real winners.
Change one variable per version so you know what moved the number.
Work from the outside in: hook, tutorial, difficulty, win or fail, end card, skin, then a new mechanic.
With Genie Playable, your team makes the next version from the last one. The next version, not a new brief.

How long does a playable ad last before it fatigues?

There's no official number, and no network publishes one. What practitioners report is consistent enough to plan around:

ChannelWhat practitioners reportSource
Fastest in-app networksAbout seven to ten solid days before performance slidesAppSamurai
MetaFatigue within about one to two weeksAppAgent
Meta and TikTok, high spendDecline can start in three to seven days; rotate every seven to tenSegwise

A UA lead at a large studio described the other side of this to us: they now produce more playables than UA can absorb, and the goal has moved from quantity to better metrics. Volume alone doesn't fix fatigue. The right next version does.

Should I make a new playable or iterate the winner?

Iterate first. Winners are rare, and a proven concept already carries most of what made it work. Sett's analysis of top studios shows the pattern clearly:

·At one studio, 70% to 75% of playables were deliberate variations of a winning concept. The other 25% to 30% explored new directions.
·Whiteout Survival ran 42 playables on AppLovin in October 2025: 15 concepts and 27 variations. The winning concept alone got 11 variations.
·The top 20 grossing games shipped a median of 64 new playables a month.

The real question isn't "new or old". It's which single change will buy the winner another two weeks.

What should I change first when a playable fatigues?

Test one variable at a time. Change the hook and the end card together, and you won't know which one worked. Start with what players see first, because that's where most of them leave. Sett's data from 3.5 million sessions shows median drop-off of about 47% in the first three seconds when there's no guided interaction.

StepWhat to changeWhat it testsSignal to watch
1. HookThe first two to three seconds: lead-in video, opening frame, the problem on screenWhether players start at allEngagement and first-three-second drop-off
2. Tutorial hintThe hand, arrow or prompt that shows the first moveWhether players understand what to doTime to first interaction
3. DifficultyHow hard the challenge is, how fast it resolvesWhether players keep goingCompletion and mid-game drop-off
4. Win or failLet them win, let them nearly win, or stop mid-gameWhich ending drives the installCTA click rate after win vs after fail
5. End cardCopy, button, character, offerWhether interest turns into a clickEnd card to CTA rate
6. SkinCharacter, theme, current live eventWhether a fresh look resets fatigueIPM against the previous version
7. MechanicA different core interactionThis is a new concept, not a variationTreat it as part of your 30% exploration budget

A note on mechanics. Combining two mechanics in one playable "looks clever and almost always tests worse", in Segwise's words. If you want to try a second mechanic, ship it as its own version.

You knew on day three. Ship the fix on day four. Genie Playable lets your UA or creative team change the hook, the difficulty, the end card or the event skin on the last version and export it again for every network. No dev queue, no new brief.

Try it free on your game

How do I know a variation actually worked?

Give it enough data. A common rule of thumb is about 50 conversions per creative in four days, or 100 in seven, before you call it. On AppLovin, don't pause creatives by hand too early; the algorithm shifts spend on its own.

Judge on the metric that pays the bills. Senior UA people are blunt about this: CPI on its own is misleading, and D7 ROAS and retention are what matter. In one public test of 360 creatives, the playable with the best IPM wasn't the one that paid back best. Use in-playable signals (engagement, completion, time to first tap) to decide what to change next, and ROAS to decide what stays live.

How do I keep a steady flow of variations?

·Keep a variation backlog for every live winner: three hooks, two difficulty levels, two end cards, the next event skin.
·Tie skins to your LiveOps calendar. A playable wearing this week's event looks fresh and matches what new players find in the game.
·Set a cadence. AppAgent suggests three to six new playables a month for Meta. AppSamurai suggests two to three concepts plus six to ten variants a week per title at higher spend.
·Log every change with its result, so the next person doesn't retest what already failed.

The bottleneck is rarely ideas. A marketing lead at a mid-size studio told us: "The idea is the easiest part. We have too many ideas." The bottleneck is how long each change takes to become a playable you can upload.

Where does Genie fit?

Genie Playable is built around the next version. Your team builds a playable 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 scratch from a brief. When it fatigues, you change one thing on the last version and export it again for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral, with Moloco coming soon. Genie Core keeps every variation on brand, so version twelve still looks like your game. Try it free on your game.

Where to go next

Before you change anything, confirm the read: how to know if your playable ad is working. Then test each change cleanly with how to A/B test playable ads, and check the playable ad best practices checklist for the advanced iteration habits.

FAQ

Sources

  1. 01Sett, Playable Ads Complete Guide
  2. 02Sett, State of Playables Q4-25
  3. 03AppSamurai, playable ads creative testing
  4. 04AppAgent, what are playable ads
  5. 05AppAgent, State of Playable Ads 2025
  6. 06Segwise, creative fatigue
  7. 07Playio, creative fatigue in mobile game ads
  8. 08Matej Lancaric, finding a winning creative
  9. 09RocketshipHQ, testing creatives on AppLovin

Keep reading

All articles →
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

Ship more.
Learn faster. Monthly volume by budget and stage.
Playable ads · 6 min read

How many playables should you test a month?

Hook,tutorial,end card.
Playable ads · 7 min read

Anatomy of a playable ad: hook, tutorial, fail state, end card

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?