Priority 1
Acquisition packaging
33
Players are seeing the game, but the page promise may not be earning enough clicks.
Run one title/icon/thumbnail test. Keep gameplay unchanged while measuring play-through rate.
Watch: Play-through rate
Analytics diagnosis
Roblox Analytics Action Planner
Paste a few current metrics and decide whether to fix acquisition, first session, retention, monetization, or update cadence first.
Priority 2
Retention loop
38
Players need a clearer reason to return after the first win.
Add one daily reward, one collection target, and one week-one update teaser.
Watch: D1 retention
Priority 3
First session clarity
44
Players may click in, then fail to understand the first goal, first action, or first reward.
Move the core promise to spawn, make the first action obvious, and pay out a visible reward quickly.
Watch: Average session length
Priority 4
Monetization offer
52
Paid value may be unclear, too early, or not trusted because the free loop is weak.
Move paid offers after the first win and lead with cosmetic, VIP, or convenience value.
Watch: Payer conversion
Priority 5
Update cadence
56
The game needs a smaller repeatable update loop before bigger content bets.
Ship one small update tied to the weakest metric instead of adding broad new systems.
Watch: D1 retention and average session
Turn the diagnosis into one controlled change
Plan a soft launch experimentConvert the top issue into a 7-day test with one changed variable.Check game page clicksIf acquisition is weak, diagnose title, icon, thumbnail, and description.Check first session funnelIf retention is weak, find the likely first-session drop-off.Build Launch PackRebuild the launch plan around the highest priority fix.
Method and evidence
How the planner prioritizes a metric
The planner reads acquisition, first session, retention, monetization, and updates as a funnel. Its bands are conservative internal heuristics used only to rank the next question; they are not official Roblox benchmarks and do not account for statistical confidence.
Acquisition
Uses impressions and play-through rate to distinguish reach from game-page packaging.
Boundary: Audience source, eligibility, device mix, and test duration still need manual context.
First session
Uses play-through, average session, and D1 signals to flag a likely promise-to-opening mismatch.
Boundary: Aggregate metrics cannot identify the exact onboarding step without a funnel or observation.
Retention
Uses D1 and session length as prompts to inspect return reasons, visible progress, and update hooks.
Boundary: Genre and audience baselines vary; compare against your own stable periods.
Monetization and updates
Delays paid optimization when free-loop signals are weak and suggests small metric-linked updates.
Boundary: Payer conversion alone cannot measure fairness, trust, or long-term value.
Reference definitions
How to decide what to improve first
Many creators see weak numbers and change the thumbnail, tutorial, update, and game passes at the same time. That makes the result unreadable.
How to use it
- + Start with the biggest bottleneck, not the newest idea.
- + Change one variable for one metric.
- + Wait long enough to compare before changing the next thing.
Example outputs
- + Low play-through rate: test title, icon, thumbnail, or description first.
- + Low average session: fix spawn, first action, and first reward.
- + Low D1 retention: add return hooks and a small week-one update reason.
Common mistakes
- + Fixing monetization before players understand the free loop.
- + Calling a full page and gameplay rewrite a test.
- + Ignoring page packaging when impressions are already present.
It is a lightweight tool for turning acquisition, retention, session, and monetization numbers into one next action instead of changing everything at once.