Try for free
Learn/Strategy

What to track inside a playable ad

The in-playable events UA teams should track, what AppLovin, Mintegral and Unity allow, and how in-ad events connect to campaign metrics like IPM and D7 ROAS.

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

Track the tap,
not just the install. The events worth measuring inside a playable.

Inside a playable ad, track six moments: the ad displayed, the first interaction, progress through the challenge, the pass or fail, the end card shown, and the CTA clicked. These in-ad events explain why a playable wins or loses; campaign metrics like IPM, CPI and D7 ROAS, which come from the network and your MMP, decide whether it stays live.

This page covers the in-ad layer. For the campaign layer and the full cut, iterate or scale method, start with how do you know a playable ad is working.

Key takeaways
Network dashboards show impressions, clicks and installs. They do not show what happened between the first tap and the CTA.
Six events cover most decisions: displayed, first interaction, progress, pass or fail, end card shown, CTA clicked.
AppLovin has an official in-playable analytics API with a fixed list of predefined events. Mintegral supports a small number of tracking points. Unity allows anonymous analytics calls. Most other networks give you only standard ad reporting.
Use in-ad events to decide what to change. Use IPM and D7 ROAS to decide what stays live.
Genie Playable builds each version from the last one, without a developer, so event names and what you learned carry from version to version.

How are in-ad events different from campaign metrics?

They answer different questions, come from different systems, and should drive different decisions.

AspectIn-ad eventsCampaign metrics
ExamplesDisplayed, first interaction, challenge passed or failed, end card shown, CTA clickedImpressions, CTR, IPM, CVR, CPI, D1 and D7 retention, ROAS
Where they come fromCode inside the playable, reported by networks that support itNetwork reporting and your MMP
Question answeredWhy did players drop off or tap through?Did the playable bring valuable players at a good price?
DecisionWhat to change in the next versionCut, iterate or scale
Available onSome networks (AppLovin, Mintegral, Unity, plus Luna Playable Insights for Luna builds)Every network

Teams we talk to often have plenty of playables live and still cannot say why one beats another. A creative lead at a large studio described their playable data as "all over the room." That is what happens when you only have the campaign layer.

Which events should every playable track?

Use AppLovin's event names as a common language, even on other networks. They map cleanly onto how a playable is built (see anatomy of a playable ad).

MomentWhat it tells youAppLovin event name
DisplayedThe playable actually rendered for the playerDISPLAYED (required); LOADING and LOADED optional, used as a pair
First interactionThe player understood the hook and started. Time from display to here is your time to engageCHALLENGE_STARTED, fired on the first real move
ProgressHow far players get before they stopCHALLENGE_PASS_25, CHALLENGE_PASS_50, CHALLENGE_PASS_75
Pass or failWhich ending the player reachedCHALLENGE_SOLVED, CHALLENGE_FAILED, CHALLENGE_RETRY
End card shownThe player reached your pitch inside the playableENDCARD_SHOWN
CTA clickedInterest turned into intentCTA_CLICKED

AppLovin's rules worth knowing, from its documentation:

·Only predefined events work. AppLovin does not track custom events.
·Do not use CHALLENGE_FAILED for crashes, JavaScript errors, load failures or timeouts. Fail means the player lost, not that the ad broke.
·Skip analytics for very short HTML ads, such as those with fewer than three interactions or that redirect within five seconds of the first interaction, and for playables with no win or lose state.
·ENDCARD_SHOWN means an end card or summary screen inside your playable, not AppLovin's own post-playable end card.
·Wrap every call in a check that the analytics object exists, and do not define it yourself. The SDK provides it.

Which metrics come out of those events?

MetricHow to calculate itReference point
Engagement rateFirst interaction ÷ displayedVendor claim (Sett, no method published): median drop-off in the first three seconds is 46.7% without guided interaction, 28.6% with a strong first-time experience
Time to first interactionSeconds from displayed to first interactionGoogle's goal for HTML5 ads: interaction within 3 or 4 seconds. Vendor claim (Sett): median 8.76 seconds
Drop-off pointWhere the progress events stopCompare versions against each other, not a market average
Completion rateSolved or failed ÷ first interactionVendor claim (Sett): average play 35 to 40 seconds; successful playables 70 to 80 seconds
Win CTR vs fail CTRCTA clicks after solved vs after failedTest both endings; there is no universal winner
End card conversionCTA clicked ÷ end card shownCompare end card variations

Treat the vendor figures as direction, not benchmarks. Your own previous versions are the reference that matters. More context on where these numbers come from is on our playable ad statistics page.

Know why it won, then build the next one. Genie Playable builds each version from the last, so the hook or ending that worked carries forward instead of getting lost in a spreadsheet. No developer needed.

Try Genie

What does each network let you track?

NetworkIn-playable analytics
AppLovinOfficial API: window.ALPlayableAnalytics.trackEvent('EVENT'), wrapped in a check that the object exists. Predefined events only; each appears as its own report column
MintegralSupports up to five action (tracking) points, configured in an action.json file packaged with the playable, per third-party build tool documentation
Unity AdsNo network requests for content, but Unity can permit analytics calls that collect player interaction data, with no personal data such as user or device identifiers. Unity handles start, view and click attribution server-side
Unity Playworks (Luna)Playable Insights collects standard events automatically, supports custom events, and breaks results down by playable, creative, ad network, OS and country. All data is anonymous
TikTokNo in-playable analytics API documented. When an ad group mixes video and playables, results are reported at ad group level only
Meta, Google Ads and othersPublic specs do not document an in-playable analytics API. You get standard ad reporting

Privacy applies everywhere. No user or device identifiers, no personal data. Track what the player did in the ad, not who they are. Packaging and size rules for each network are in our playable ad specs hub and the AppLovin specs page.

How do you connect in-ad events to ROAS?

Keep the two layers separate, then read them together. In-ad events explain behavior: whether the hook worked, whether the tutorial was clear, which ending drove the click. Network and MMP data tell you whether those players paid back.

The gap between the layers is real. UA consultant Matej Lancaric reviewed about 360 creatives for one game in an analysis published in August 2026 and found the creative that converted most efficiently was not the one that paid back best. Strong engagement does not guarantee strong D7.

A workable loop:

01Pick the live version with the best D7 ROAS.
02Look at its in-ad funnel and find the step with the biggest drop.
03Change only that step in the next version.
04Test it against the current version with a planned sample, as described in how to A/B test playable ads.

Our guide to iterating a winning playable covers what to change at each step.

What should UA teams ask for from whoever builds their playables?

·The six core events on every playable, named the same way across versions.
·Native AppLovin analytics events on every AppLovin build, and Mintegral tracking points where you run Mintegral.
·A version ID on every build, so results map to the exact change you made.
·A short report per version: engagement, time to first interaction, drop-off point, win vs fail CTR, end card conversion.
·No personal data, ever.

Where does Genie Playable fit?

Genie Playable builds playables from your APK or HTML build plus the assets in Genie, from a format that is already working, or from scratch from a brief with Genie Agent. It exports optimized builds for Meta, AppLovin, Unity Ads, Liftoff, Google Ads, TikTok Ads, Pangle and Mintegral, with Moloco coming soon. Because every version comes from the one before it, what you learn from the data stays attached to the playable.

Genie Playable is not an analytics platform or an MMP, and it does not replace network reporting. If you need a dashboard that pulls creative performance across networks, that is a different tool. It is also not the right fit if your in-house team already ships instrumented variants as fast as you can test them.

Self-serve starts at $490 a month, or $249 a month for startups, with a free sign-up that covers your first two playables. The custom plan, usually for larger companies, is a full one-month pilot where the Genie team onboards you and helps you build the playables you want. The product is moving fast, and we will keep this page current.

Build the next version from what you learned. Track the six moments. Change one thing. Genie Playable builds the next version from your game, without a developer.

Try Genie

FAQ

Sources

  1. 01AppLovin, Playable analytics integration
  2. 02Unity Grow, Playable specifications
  3. 03Unity Playworks (Luna), Playable Insights overview
  4. 04TikTok Ads Help, How to create Playable ads on TikTok Ads Manager
  5. 05Google Ads Help, Make better creative assets for App campaigns
  6. 06Needle Engine, Mintegral playable deployment (third-party build tool documentation)
  7. 07Matej Lancaric, How to find a winning creative, August 2026
  8. 08Sett, Playable ads complete guide (vendor claims)

Keep reading

All articles →
Cut, iterate
or scale. The metrics that decide.
Playable ads · 11 min read

How do you know a playable ad is working?

One change
per test. Test design in plain language.
Playable ads · 11 min read

How do you A/B test playable ads?

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

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?