Open game analytics
The game card is the starting point for analytics, products, advertising and chats.
How to use it
- In My games, select a project's artwork or name to open All analytics.
- Choose Acquisition, Engagement, Retention or Monetization.
- Set a range on the chart you need. Use its refresh button to update it.
Advice and practical context
Card as context
A game card brings together links to several modules for one game. Its summary metrics are useful orientation, but the detailed chart carries the range, breakdown, and data state needed for interpretation. One live KPI cannot replace history.
Verify the selected game
Check the name and Universe ID before opening products, ads, or analytics, especially for similarly named group games. Avoid analyzing one card and then saving an action to another game after the global selection changes.
Live summary metrics can have a different freshness time from daily reports inside analytics. If values differ, inspect source and range rather than forcing an arithmetic reconciliation. The card is navigation and quick status, not one unified report.
Technical detailsCalculations, permissions and behavior
Game cards, chats & current players
Each connected game has its own card with connection status, current players, DAU, D1 retention and revenue with a large light Robux symbol. The artwork and title open All analytics; the three KPIs are links too: DAU opens engagement, D1 opens retention and revenue opens monetization. After Charts, Marketplace opens this game's listing and highlights received buyer offers.
The price banner is removed from the card. Actions are ordered as all analytics, advertising, payments, events, charts, marketplace, investor analytics, access, chats and contacts. Teammate invitations live inside Access.
Replace key, SDK and disconnect are grouped under the final gear button. The red Chats badge shows the number of authors with unread messages for that game and updates immediately through a protected event stream. The Current players block appears both on the card and in the analytics header.
Select it to open player history. Player counts are rounded to whole people; zero means no players and a dash means data has not been received yet.
Analytics topics
Benchmarks, engagement, demographics, retention, monetization, hourly revenue, Creator Rewards, acquisition, thumbnails, funnels, events, economy, safety and performance. A detailed retention metric also shows separate D1, D7, D30 and Stickiness (DAU/MAU) charts together, so return and audience regularity can be reviewed in one section. Chart availability depends on Roblox data and permissions, not merely a metric name.
The dictionary below uses the same catalog as the interface.
Internal analytics header & sync
The internal analytics header keeps the game and the whole-number Playing now block, with no separate CSV button. A square icon-only sync button sits at the right of the current section title row. It refreshes that section in the background, preserves the selected range and keeps loaded charts visible; the icon spins during the request and repeat clicks are disabled.
Servers and event freshness
Before Current players, the card shows public root-place server count from the shared complete observation, without an additional Roblox request on opening. Private servers are excluded; an observation older than 15 minutes is shown as a dash. Revenue and its Robux icon match adjacent KPIs.
Events show saved data immediately on entry and check for updates in the background. The next and ongoing events have a subtle green background; past events are red and collapsed. Dimmed counters are awaiting a fresh Roblox response.
Failed requests preserve and dim saved counts. Background refresh follows existing per-source schedules; manual refresh checks the selected game or the first two games in the all-games view, while the queue handles the rest.
24-hour player statistics
The player-history header shows current CCU, minimum, maximum and mean of real public observations in the last 24 hours, total visits, server capacity and update time. Selecting an hourly or monthly chart does not shorten the daily sample. Analytics daily peaks do not replace daily observations.
With only one observation the statistics remain unknown; missing hours are never counted as zero.