Welcome Kit · Studio Workspace

Your game is one of millions.
Know exactly why it wins.

Player telemetry, the live Roblox market, and the controls to act on both. This is where a hunch becomes a decision you can defend to whoever signs off on the next build.
02
Scopes
28
Views & tools
01
Day to live data
Inside this guide

One picker, two workspaces

The control at the top of your sidebar is not a filter. It swaps the entire navigation. Miss it and half the product stays invisible, which is the single most common way a new studio underuses ROLearn.

01
Studio scope
What is my studio, and the market, doing?
11tools
02
Experience scope
What is this one game doing?
17views
Studio scope needs nothing from you
None of the eleven studio-scope tools ask which game you mean, so all of them work on your first day with no SDK installed and no experience linked. If your workspace looks empty, you are almost certainly in experience scope. Flip the picker.
Studio scope · Your portfolio

Command Center

Every game you run, on one screen.

Overview
Portfolio health at a glance.

Totals and deltas across every linked experience, health cards per game, your biggest movers and the ones needing attention. The Monday morning screen for whoever runs the studio rather than a single title.

Metrics
The same portfolio, as trend lines.

Active players or revenue over 7, 30 or 90 days, with your experiences side by side.

Reports
Every report your studio has generated.

The same library the per-experience Report page shows, unfiltered.

Studio scope · The market

Market Intelligence

Six reads on the whole of Roblox, none of which need a game of your own.

MP
Market Pulse
A briefing: what deserves your attention this week.
OM
Opportunity Map
Demand against saturation, so you see an open market before it closes.
BR
Breakout Radar
Which games are growing faster than the platform right now.
BL
Benchmark Landscape
What realistic success looks like for a game like yours.
CP
Copy Pressure
Whether a space is becoming crowded, dimension by dimension.
RR
Risk Radar
Five risk signals for a genre you are considering.
This data is the market's, not yours
Every figure here describes Roblox and is identical for every ROLearn customer. Nothing you send us feeds it, and nothing another studio sends us reaches you.
Studio scope · Before you build

Concepts

Turn a pitch into a decision with its reasons attached.

Concept Validator
Nine axes, one named verdict.

Write a brief, and get it scored on demand, momentum, saturation, durability, differentiation, monetization fit, discovery difficulty, production fit and portfolio fit. The output is not a number out of a hundred, it is an instruction: Build, Prototype First, Watch The Market, Reposition, or Do Not Pursue, with the reason it landed there and what would have to change to move it.

Saved Concepts
Your library, and its history.

Every brief keeps its validation runs, so you can see how a concept scored before and after you changed it.

Experience scope · One game at a time

Eight views on your players

ViewWhat it tells you
OverviewHeadline performance, and whether anything moved.
MetricsThe time series behind the headlines: players, sessions, playtime.
RetentionD1, D7 and D30, plus a cohort matrix for when the average hides the story.
MonetizationRevenue, products and spending behaviour, as your game reported it.
ProductsYour catalog as Roblox sees it, with the prices you can edit from here.
AudienceWho plays, where they are, and the hours they are actually online.
Player dataPlayer-level questions, answered the cheapest way that works.
ReportA shareable summary for anyone who will not open the dashboard.
Experience scope · Growth

Getting found

Two surfaces that do not just measure, they act. Both write to your live Roblox experience, so both need an Open Cloud key granted for actions.

Advertising
Run and steer your Roblox ad campaigns.

Create campaigns, upload creatives, change budgets, pause and resume, all without leaving ROLearn. Reads come from our cache so opening the page costs you nothing, and every figure tells you how old it is.

Thumbnails
Test what actually makes people click.

Upload variants, split traffic between them, and promote the one that wins. It weighs conversion against what happens after the click, so a thumbnail that pulls players in and loses them is not treated as a winner.

Experience scope · Development

Keeping it healthy

Live events
The raw stream, as it arrives.

Every event your game sends, within seconds. Where you confirm an integration works.

Errors
Events we rejected, and why.

Nothing is ever silently dropped. Anything rejected is held here with a reason and a retry button, so this is a to-do list rather than lost data.

Performance
Frame rate, crashes and stability.

How your experience runs on the machines your players own, not on yours.

Releases
What each build did to your numbers.

A verdict per release, against the baselines from before it shipped.

Experience scope · LiveOps

Running the live game

Two surfaces for the machine, one for the human.

Live config and Commands
What your running servers poll.

Configuration your game reads at runtime, and the command queue it acknowledges. These are plumbing: you set them up once and your game consumes them.

Command Center
Where a person decides something.

Your event timeline, whether your servers are actually listening, and the controls to publish a message or restart. It shares its machinery with the two pages above and deliberately does not share their shape, because scheduling an event and editing a config are different jobs.

Experience scope · The operating layer

What we will and will not do to your game

Eight of the seventeen experience-scope views can change something real: your ad spend, your prices, your live servers. We are deliberate about the boundary, and it is worth knowing before you grant a key.

We will
Create and steer ad campaigns, split thumbnail traffic, change a product price, schedule and publish events, restart servers, and take a pre-release backup.
We will not
Publish your game, roll back a build, run arbitrary code in your experience, or write to your player data stores beyond a restore point.
Reading and acting are two separate keys
Everything above needs an Open Cloud key granted specifically for actions. It is a different slot from the one that powers your charts, on purpose, so revoking the ability to act never blanks a single dashboard. Every action is recorded before it is sent, and you can read that ledger yourself in Settings.
How to read this product

A dash is not a zero

Most dashboards show a number or nothing. ROLearn separates three situations that look identical everywhere else, because what you should do about them differs.

What you seeWhat it meansWhose move
A numberWe measured it. This includes a zero: a measured zero is a finding, not an absence.Yours, if you dislike it
Not set upThe instrument is not attached yet. No key, no SDK events, a scope you have not granted.Yours, and we say which step
UnavailableWe tried and failed. A job stalled, a query timed out, Roblox refused us.Ours
Why this matters more than it sounds
A crash rate of zero and a crash rate we could not measure look the same on every other dashboard, and one of them is the most flattering possible way to be wrong. When ROLearn cannot measure something it says so rather than showing you a confident zero.
Getting set up

Live on day one

Two things to connect, and they are independent. Either one alone gives you a working workspace.

The SDK
Your own players, your own numbers.

Register your experience in Settings, mint an ingest key, and either install the SDK yourself or let the Roblox Studio plugin do it for you. Events appear on Live events within seconds. The pages built on nightly rollups fill in the following morning.

An Open Cloud key
What Roblox knows, and the ability to act.

One key from your Roblox account, pasted once, with you telling us what it is for. Reading powers the platform-official numbers. Acting unlocks the operating layer. Player data is consented separately again, so you can grant one without the others.

Getting set up

Your first week

WhenWhat happens
Day 1Register your experience and mint an ingest key, in Settings → Experiences.
Day 1Install the SDK, or Activate straight from the Roblox Studio plugin.
Day 1Confirm events are arriving on Live events. Seconds, not hours.
Day 1Open Market Intelligence. It needs nothing from you and works from a standing start.
Day 2Your first rollup-backed pages fill in, after the nightly run at 09:00 UTC.
Day 3Connect an Open Cloud key for reading, then press "Check what this key can do".
Day 5Generate your first Studio Report and share it with your team.

Welcome aboard.

Flip the scope picker. Half of this works before you send us anything.

For click-by-click detail on any screen, open the How-To Guide.

1 / 14
Use ← → to move