Launch & promotion
Roblox Experiments results: decide without chasing green metrics
An experiment result supports a decision within the prewritten question. One favorable secondary measure does not override an inconclusive primary metric or harm to a guardrail.
Focused deep dive
Reading order
Check integrity first: the test ran as planned, variants delivered, and no critical release or outage compromised it. Then read the primary metric, effect direction, MDE or uncertainty, and maturity. Next review D1, D7, playtime, ARPU, ARPPU, payer conversion, and session time as predeclared guardrails or explanatory measures.
Inspecting many measures creates an opportunity to select one random green result. Do not replace the primary metric after seeing data. D7 needs time, cumulative monetization can be sensitive to outliers, and an average hides the distribution.
| Outcome | Decision | Wording |
|---|---|---|
| Primary improves; guardrails safe | Consider rollout | Effect supported under test conditions |
| Primary inconclusive | Do not declare a winner | Test did not distinguish a useful effect |
| Primary improves; guardrail worsens | Stop or study tradeoff | Improvement carries a cost |
| Integrity broken | No causal conclusion | Result is invalid |
Hypothetical example
A variant improves D1, session time falls, and D7 is not mature. The team does not roll out immediately. It checks whether session time was a guardrail and whether the decline represents product harm. If D1 was primary, the result supports early return but does not establish long-term value.
MARPLA can mark the date and describe aggregate background and acquisition source. Its overall chart does not replace randomized participant comparison in Creator Hub. Save hypothesis, configuration, window, result, limits, and next question.
- Verify integrity and the plan.
- Read the primary metric before secondary measures.
- Review guardrails and maturity.
- Do not redefine success after inspection.
- Record rollout, rerun, or rejection with its reason.
Primary sources
Put this into practice in MARPLA
Locate early drop-off using retention and connected events. After changing onboarding, compare new cohorts to check whether more players reach their first meaningful action and return.
- Compare your game with benchmarksBenchmark scales show how your game performs alongside other projects.Step-by-step guide →
- View custom eventsCustom events track in-game actions, such as completing stages.Step-by-step guide →

Discussion0
Loading comments…