The studio's own games have two kinds of numbers. Public numbers (players now, visits, favorites, likes) come from the collector like any market game's. Owned numbers are what Roblox reports only to a game's owner, read once a day with the key of the Roblox group that owns the game. This page defines the owned ones.
Owned numbers at a glance
Every owned number is stored one value per UTC day (game_daily_metrics), read daily from Roblox's Analytics Query API; a tile shows the latest stored day, never today. Each is empty with a reason when no key covers the game or Roblox declined it (below).
- DAU (DailyActiveUsers)players
Window: one UTC day. Distinct players that day.
- MAU (MonthlyActiveUsers)players
Window: the 30 days up to each day.
- D1, D7, D30 retention (ForwardD1Retention, ...)ratio
Window: the players who first played on a day, measured 1, 7 or 30 days later; so the newest D1 is a day older than the newest DAU, D30 at least 30 days old.
- ARPDAU (AverageRevenuePerUser)Robux per player
Window: one UTC day. Roblox's own figure.
- ARPPU (AverageRevenuePerPayingUser)Robux per paying player
Window: one UTC day.
- Payer conversion (PayingUsersCVR)ratio
Window: one UTC day. The share of daily players who spent Robux.
- Revenue, 24 hours (DailyRevenue)Robux
Window: the latest complete UTC day stored, not the last 24 hours on the clock.
- Revenue, 30 daysRobux
Window: every stored day from 30 days ago to the latest stored day, added up. Null: no day stored.
- Hours played (TotalPlayTimeHours)hours
Window: one UTC day, every player's time added up.
- Peak concurrent players (PeakConcurrentPlayers)players
Window: one UTC day, as Roblox counts it.
The formulas the panel itself applies (everything else is Roblox's own figure, stored as given):
stickiness = DAU / MAU (Roblox's DauMauStickiness)
revenue, 30 days = sum of DailyRevenue over the stored days in the last 30
revenue, 24h = DailyRevenue of the latest stored day
(or the sum of its per-source rows when only those are stored)
studio-wide = sum of each game's daily counts and Robux; rates are never addedWhere owned numbers come from
The worker reads each studio game's numbers from Roblox's Analytics Query API (Open Cloud) with the Open Cloud key of the studio group that owns the game, stored by an owner under Admin, Groups (see Roblox groups and keys). A key covers a game when its group owns the game on Roblox; a game owned by a person, or by a group with no key, has no owned numbers. The key needs universe.analytics:read; developer products, game passes and bans need their own permissions.
Values are stored one per UTC day, metric and slice (game_daily_metrics), under Roblox's quality flag (Valid, Projected, or not statistically significant). Market games never have owned numbers.
When owned numbers are read
Once a day, on the worker's own queue, and once more a minute after the worker starts.
The first read of a metric goes back 90 complete UTC days (28 for performance metrics and for breakdowns, which Roblox keeps no longer).
Every later read re-reads the last 7 complete UTC days and replaces them, because Roblox revises recent days (Projected values firm up).
Today is never read, so the newest day is yesterday at best. The hub says how far the numbers go: "Roblox's numbers through 2026-10-22, UTC; CCU is live."
Why an owned number is missing (needs the group's key)
An owned stat with no value says why in its place:
| Shown | Means |
|---|---|
| Needs the group's key | No stored key covers this game (status Not configured) |
| Waiting for the first read | A key covers it; the daily read has not run for it yet |
| Key refused | Roblox refused the key |
| Missing permission | The key lacks the permission for this game, or the request came from outside its allowed addresses |
| Read failed | Roblox could not be reached or answered something unexpected |
| Not reported by Roblox | Roblox declined this metric for this game (ad revenue for a game without ads) |
| Not reported by Roblox yet | The read works, but no day of this metric is stored yet |
Stored numbers stay after a key is removed; the "through" day says how old they are.
DAU (daily active users)
The number of distinct players who played the game on a UTC day, as Roblox counts it (DailyActiveUsers). The DAU tile on a game's hub and the studio's games list shows the latest stored day. Charts show it day by day; Players by platform, country, age group and acquisition source split it.
MAU (monthly active users)
Distinct players in the 30 days up to each day (MonthlyActiveUsers). Added up across games on the Players page, a player of two games counts twice.
Stickiness (DAU / MAU)
Daily active users over monthly active users (DauMauStickiness): how many of the month's players came back that day. A ratio.
D1 retention (day-1 retention)
Of the players who first played on a day, the share who came back the next day (ForwardD1Retention), shown as a percentage. The D1 tile shows the latest stored day. A day's D1 is only known a day later, so the newest D1 day is a day older than the newest DAU day. It is also split by platform.
D7 retention (day-7 retention)
The same, for players who came back 7 days later (ForwardD7Retention). Its newest day is at least a week old.
D30 retention (day-30 retention)
The same, 30 days later (ForwardD30Retention). A day's D30 is known only 30 days later, so the list reads 62 days back to find its latest stored day.
How rates are shown
Retention, payer conversion, stickiness and the conversion rates are ratios shown as percentages. Whether Roblox sends them as fractions or percentages has not been seen on a live key yet, so a metric with any stored day above 1 is read as percentages. Rates are never added up across games.
ARPDAU (revenue per daily active user)
Robux per daily active user on a day (AverageRevenuePerUser), as Roblox computes it. The ARPDAU tile shows the latest stored day. Revenue per player charts it beside revenue per paying user.
ARPPU (revenue per paying user)
Robux per player who paid that day (AverageRevenuePerPayingUser).
Payer conversion (share of players who pay)
The share of daily active users who spent Robux in the game that day (PayingUsersCVR). The Payer conversion tile ("of daily users paid") shows the latest stored day.
Paying users
How many players spent Robux in the game that day (PayingUsers).
Revenue, 24 hours (the latest day)
The Robux Roblox reported for the latest complete UTC day stored (DailyRevenue), not the last 24 hours on the clock. The tile says "the latest full UTC day". When only per-source rows are stored, their sum.
Revenue, 30 days
The Robux Roblox reported for every stored day from 30 days ago up to the latest stored day, added up. Empty when no day is stored. It is the 30-day Robux column on the Studio games page.
This is revenue reported by Roblox, not money the studio has received.
Revenue by source
Revenue is also read split by where it came from (RevenueSource: game passes, developer products and so on), each source stored as its own row. By source on the Money tab adds up the range.
Ad revenue
Robux from ads shown in the game (AdsPublisherReportingTotalRevenueRobux). Roblox declines it for a game without ads, which shows "Not reported by Roblox".
Revenue by platform
The day's revenue split by the platform players paid on, one of the breakdowns, read 28 days back on the first read. Day-1 retention is split by platform the same way, and daily active users by platform, country (the 20 largest a day, the rest as Other), age group and acquisition source.
Playtime per active user
Average minutes played per daily active user that day (AveragePlayTimeMinutesPerDAU), shown in Time played beside session length.
Session length
Average length of one play session, in minutes (AverageSessionLengthMinutes).
Hours played (total playtime)
Every player's time in the game added up, in hours, per day (TotalPlayTimeHours). Hours played on the Players tab and the studio's Players page.
Players with a session
Distinct players who started a play session that day (UniqueUsersWithPlaySessions), in Players by day.
Peak concurrent players (owned)
The most players in the game at once on a day, as Roblox counts it (PeakConcurrentPlayers). It can be higher than the collector's observed peak, which only sees the moments it reads.
Visits (owned)
Visits on a day as Roblox reports them to the owner (Visits): a daily count, unlike the public running total of visits.
Acquisition: shown, opened, played
From the acquisition group:
Players shown the game (
UniqueUsersWithImpressions) and Players who opened its page (UniqueUsersWithClicks), daily distinct players.Shown to page opened (
ImpressionCVR), Page opened to played (ClickCVR) and Shown to played (EndToEndCVR), the conversion rates between those steps.Acquisition funnel adds up each step's daily players over the range.
Performance: frame rate and crashes
Client frame rate (fps), client crash rate over 15 minutes, server frame rate (fps) and server crashes, per day. Roblox keeps these 28 days, so the daily read is their only archive.
Abuse reports
How many abuse reports players filed about the game that day (TotalAbuseReports).
Developer products and game passes
Each product and pass with its price in Robux and whether it is on sale, as the group's key last read them, with a price history from the day the worker first read the game. An item a complete read no longer lists is marked unlisted, never deleted.
Bans
The game's bans as last read, with their reasons for owners and the game's lead, and how many bans were active each day.
Studio-wide players and revenue
The studio's Players and Revenue pages add the games' daily values together over 30, 90 or 365 days. Counts and Robux add up; rates do not. See Studio pages.
Related: Studio games page, Studio players page, Studio revenue page, Players and CCU, Freshness and empty numbers, Glossary.
Updated