The Studio section covers the studio's own games. Its rail has five pages: Games, Players, Revenue, Points and Updates, and each game has its own hub. Every signed-in member can read every page, revenue included.
Where to see the studio's players and revenue
Players across the studio's games: Studio players page (
/studio/players).Revenue across the studio's games: Studio revenue page (
/studio/revenue).Every game side by side, players now, daily active users, retention and 30-day revenue per game: Studio games page (
/studio).One game's players and money: its hub's Players and Money tabs, see A studio game's pages.
Every studio game in one table, with filters, tiles and charts across the games.
Daily and monthly active users, retention, playtime and the audience, added up across the games.
Robux by game, source and platform, payers, ad revenue, and every product and pass.
Your points to spend, what expires, the games selling shares to you.
One game's hub and its tabs.
Where the Studio numbers come from
- Public numbers
Players now, visits, favorites and likes come from the collector, which reads each game on its tier's schedule, from every 5 minutes to once a day.
- Owned analytics
Daily active users, retention, playtime, revenue and their breakdowns, products and passes, and bans are Roblox's own daily numbers for a game, read once a day with the key of the Roblox group that owns it. Days are UTC; today is never there yet.
- The studio's own records
Projects, contracts, points, shares and the release log are read from the platform's database.
No Studio page asks Roblox anything itself. How a group key reaches a game's analytics, step by step, is on Admin Integrations.
What Not configured and the other analytics statuses mean
A dash on a Studio page is a number nobody has read, never a zero. Where a game's owned numbers are missing, the page says why, in the game's analytics status:
- Not configured
No registered Roblox group with a key owns the game. An owner adds the group and its key on Admin, Groups.
- Waiting for the first read
Its group's key covers the game; the daily read has not run for it yet.
- Missing permission
The key cannot read this game's analytics. An owner extends or replaces it.
- Key refused
Roblox refused the stored key. An owner replaces it.
- Read failed
The last daily read failed; the page shows what was read before, and it tries again on its own.
Owners also see the stored error, folded away, and Open groups where the key is the problem. The same statuses, as owners see them on Admin Integrations, carry the exact sentence to act on.
Updates page (/studio/updates)
The Updates page (/studio/updates) puts every studio game's updates log on one timeline, newest first, and shows what players did in the week after each release against the week before. Every signed-in member can read it. Releases are recorded on each game's Overview, in its Releases card, by owners and the game's lead; nothing is recorded here.
With no release recorded anywhere, the page says "No releases recorded" and links to the studio's games.
Filtering the Updates page to one game
The tabs in the header are Every game and one tab per game with at least one release (/studio/updates?game=<universe id>). Choosing a game narrows the tiles, the chart and the timeline to it.
Releases tile
How many releases are recorded, and how many in the last 30 days.
Players after a release tile
The middle (median) change in players across the releases that can be measured, and how many releases that is. "No release has readings on both sides yet" when none can.
Latest release tile
The newest release's title, its game and when it shipped.
Releases by game and month chart
How many releases each game shipped per calendar month over the last 12 months, stacked by game. A month with no bar shipped nothing.
The Updates timeline
Every release, newest first. Each entry shows its kind (Launch, Update, Hotfix or Live event), title, game (a link to the Releases card on the game's Overview), when it shipped, its place version and who recorded it when known, up to three lines of its notes, and its effect on players.
How the Updates page measures a release's effect
A release is compared over the 7 days after the day it shipped against the 7 days before; the day itself is in neither. The change is shown as a percentage with the two averages ("Daily active users: 1,200 → 1,450 a day").
It uses daily active users where owned analytics has days on both sides.
Otherwise it uses players online, the collector's hourly concurrent players averaged per day.
A release without readings on both sides (one made today, or for an untracked game) says "Not enough readings on both sides of it to compare".
A release whose week after is not over says how many of the 7 days are in so far.
See How the effect of an update is measured.
The Updates page on a phone
The game tabs sit in the header. The tiles sit two across with the latest release on its own row; from 640 px all three sit in one row. On a phone each timeline entry's effect is written under it; from 640 px it sits on the right.
Related: Projects, Games and releases.
Updated