Roblox Home recommendations: action plan

Seven actions in priority order

Use one diagnostic question per cycle. Save the date, metric definition, and available breakdowns. If the dashboard cannot provide a joint breakdown, keep that as a limitation instead of filling the gap with an assumption.

Do not use a universal waiting period or fixed impression threshold: Roblox publishes no such ladder. When a blended metric changes after expansion, inspect results inside old and new segments. If the required joint breakdown is unavailable, narrow the wording to an observed coincidence instead of claiming that a new country harmed the game.

End the cycle with one decision: retain the set, repair entry, localize one step, or keep observing. State what new evidence would cause the team to reconsider that decision.

1. Separate Home, Sponsored, Search, Friends, and other sources before explaining a blended average.
2. Check impressions, PTR, first-play bounce, and post-join behavior over matching windows.
3. Prepare the first loop, analytics, and stability before scaling inflow.
4. Compare countries as mature cohorts without inventing a market ladder.
5. Decompose the average into mix and within-segment performance.
6. Fix localization or performance only where evidence points.
7. Record the decision and next bounded test, preserving unknowns.

Primary sources

• Roblox Creator Hub — Discovery