Set up, in this order

Studio scope works immediately and needs none of this. Everything experience-scope stays empty until these steps are done.

There is no Settings row in the sidebar, by design. Reach it from your avatar in the top right, or from any "Complete setup" prompt on a page. Everything below lives under Settings.

1. Your studio profile

Settings, then Studio profile. Two minutes, and it only affects how your studio is labelled.

1. Set your studio name. This is what appears at the top of the sidebar and on reports you share.
2. Optionally add your public domain and location, and upload a logo.

2. Register each experience

Settings, then Experiences. The page calls itself Key Setup.

1. Pick the platform: Roblox, Steam, Fortnite or Unity.
2. Enter the id for that platform. On Roblox that is your place id.
3. Add a display name so you can tell your experiences apart later.
4. Click Register experience.

3. Mint an ingest key

1. Expand the experience you just registered.
2. Click + Add environment and name it: prod, staging, qa.
3. The key appears in a one-time reveal. Copy it now.

4. Get the SDK into your game

Two routes. The plugin is faster; the manual install is what you want in a real build pipeline.

1. Install ROLearn from the Creator Store and open its panel.
2. Click Connect. It shows a code; enter that code at rolearn.dev/link in your browser and approve.
3. Open the place you want to instrument and click Activate. The plugin writes the scripts and injects the key for you.
4. Publish.

Follow the engine guide for Roblox, Unity or Steamworks in the SDK documentation. That is where the code lives; this guide deliberately does not duplicate it.

Four ways the plugin quietly fails

All four report success, or nothing at all, and produce no telemetry. They are worth reading before you debug your own code.

• Two Studio settings must be on. Allow HTTP Requests and Enable Studio Access to API Services, both under Game Settings → Security. They are set per place and reset for every new place you create. The plugin checks and warns; a manual install has no such guard.
• The pairing code lasts ten minutes. Past that, approving it fails and you restart from Connect.
• An unpublished place cannot be activated. Roblox reports its id as zero until you publish it once.
• The plugin link belongs to your Studio install, not your workspace. If you linked with one account and later work in another studio's workspace, keys provision into the first account's team and the second shows "not installed" forever. The panel prints which account and team you are connected as, precisely so you can catch this.

5. Connect an Open Cloud key

Optional, and it unlocks a different half of the product: what Roblox itself knows, plus the ability to act. Settings, then Integrations.

1. Create a key in the Roblox Creator Hub with the scopes you want to grant.
2. Paste it once, and tick what it is for: Reading data, Taking actions, Player data.
3. Press Check what this key can do. This is the step people skip.

Reading the capability matrix

After you probe a key, every module shows a state. They mean different things and only one is your problem.

Command Center

Flip the scope picker at the top of the sidebar to your studio name. The nav changes completely.

• Overview is your portfolio: totals with deltas, a health card per experience, top movers, and what needs attention. The nav calls it Overview and the page calls itself Dashboard.
• Metrics is the same data as trend lines. Range 7, 30 or 90 days; switch the series between active players and revenue.
• Reports is every report your studio has generated, filterable by drafts, shared and archived.

Market Pulse, Opportunity Map, Breakout Radar

Benchmark Landscape, Copy Pressure, Risk Radar

Four things to know before you quote these

• Higher means worse on Risk Radar and better on the Concept Validator. They are the two pages most often open together and they run opposite conventions. Check which one you are reading before you screenshot it.
• "Day-30 stability" is not retention. It is what share of peak concurrent players a game holds. Roblox publishes no retention figure for a game you do not own, and we refuse to estimate one.
• Copy Pressure measures overlap, not plagiarism. Nothing here says anyone copied anyone. Some dimensions come back unmeasured and say so rather than scoring zero.
• A thin sample refuses to score. Across all six tools, too little data produces a stated reason instead of a number nobody should act on. The weights and the formula behind every score are printed on the page, so you can reconstruct any figure you doubt.

Concept Validator

1. Write a brief: the genre, reference games, and your production timeline.
2. Run the validation. Nine axes are scored and a verdict is named.
3. Read the counterfactual panel: it tells you which axis to move, and how far, to change the verdict.
4. Save it. Every run is kept, so you can re-validate after changing the concept and compare.

Overview and Metrics

Flip the scope picker to an experience. These two are where you start.

• Overview is the headline set for one game, with a live player count and today's figures. Today's numbers refresh hourly; everything longer comes from the nightly run.
• Metrics is the time series underneath: active players, sessions and playtime over the window you choose.

Retention

D1, D7 and D30 as headlines, plus a daily cohort matrix underneath.

Read the matrix rather than the headline whenever you have shipped something. A single D1 number averages across every cohort in the window, so a good update and a bad one three days apart cancel each other out. The matrix shows you the day the line moved.

Monetization and Products

Two money pages, two different sources. This confuses people, and the difference is the useful part.

Editing your catalog

Products is titled Monetization Control Center on screen. Three tabs: Catalog, Performance and Subscriptions, the last two chipped Optional because the catalog works without either.

1. Filter to Developer products or Passes.
2. Open a product to edit its name, description, price, or whether it is for sale.
3. A price change asks for an explicit confirmation before it is sent.

Audience

Who plays, where they are, and when they are online. The old Geography page was folded in here; if a walkthrough still says Geography, this is it.

• Countries with players, sessions and revenue. Click a row to drill in.
• The hour-of-day heatmap, and the best windows it derives, for scheduling an event or a drop.
• Demographics, switchable between local time and UTC.

Player data

Three ways to answer a player-level question, listed cheapest first. The page leads with the one that reads no profiles at all.

Report

A shareable summary for the people who will never open the dashboard.

1. Generate a report for the period you want.
2. It appears in the library and fills in as it composes. The page updates itself; there is nothing to refresh.
3. Download it, or share it with named recipients.

The studio-scope Reports page is the same library with no experience filter, so a report generated here shows up there too.

Advertising

Needs an Open Cloud key granted for actions. Titled Advertising Command Center on screen.

1. Pick the experience, and a window from 1 to 90 days.
2. Create campaign: name, billing account, up to 25 creative assets, budget, start time and duration.
3. Set the time zone explicitly. Roblox schedules against your billing account's zone, not yours.
4. Pause, resume, rename or change budget from the campaign row. One field per change.

Thumbnails

Needs an actions key. Titled Thumbnail Experimentation Lab on screen.

1. Upload variants, up to 8 MB each.
2. Set the split explicitly, or promote one variant to a target share.
3. Read the verdict once there is enough traffic to call it.

Live events

The raw stream, within seconds. Titled Live event log on screen.

This is the first place to look when you have just installed the SDK and want to know whether anything is arriving, and the first place to look when a downstream number seems wrong. If events are here but a chart is empty, the problem is downstream of ingest and usually a timing one: most pages are built from the nightly run.

Errors

Titled Rejected events on screen. If your data is missing, read this page before you read your own code.

Events we could not accept are held here with a reason, never discarded. The most common by far is game not linked: your SDK is sending correctly, to an id you never registered. Those requests return success to your game, so nothing in your logs looks wrong.

1. Read the grouped reason cards. Each names the problem in plain English.
2. Fix the cause first. Retrying an unlinked game before you link it just fails again.
3. Then Retry a row, or retry the batch.

Performance and Releases

Live config, Commands, Command Center

The first two are what your servers poll. The third is where a person decides something.

1. Pick the experience and a window from 1 to 90 days.
2. Schedule events on the timeline, and edit or delete them.
3. Publish a message to your running servers, choosing the kind your game listens for.
4. Restart servers, which needs an admin and a typed confirmation.

Workspace Settings

Reached from your avatar in the top right. There is no Settings row in the sidebar.

The Integrations tab

Where every "Connect a key" link in the product lands, and the one tab worth knowing in detail.