View a game report
The report brings together game metrics, charts and audience information.
How to use it
- Open Investor analytics on the game card.
- Choose a range and the metric you need.
- In Demographics, switch audience dimensions and compare the chart with the table below.
Advice and practical context
One report, several layers
The overview combines owner KPIs, charts, audience data, and available public facts. Do not compare cards without checking ranges: live CCU, daily DAU, and cohort D1 have different time meanings. The demographic table supplies volume that a line can hide.
History over point
Revenue growth should be read beside DAU, payer conversion, and ARPPU. If only traffic increased, efficiency may be unchanged. Do not present an aggregate as the causal result of an update or hide that the current period is incomplete.
Show the boundary when a metric covers only part of the selected range and never fill earlier dates with zero. For audience composition, pair segment percentage with absolute MAU because a changing total can create misleading share movement.
Technical detailsCalculations, permissions and behavior
Internal and external modes
When an owner or teammate opens Investor analytics from their own analytics, the report stays inside MARPLA with the sidebar, game header and other analytics tabs available. Report topics use a separate URL parameter and cannot switch the service's main section. A permanent common or temporary investor link opens the same authorized dataset on a standalone page without MARPLA's sidebar or work areas, keeping the recipient focused on the selected game.
Investor View in the internal mode lets the owner verify that external presentation in a new tab.
Demographics snapshot and history
Demographics opens with Countries, followed by gender, age, platform and operating system. The selected dimension's history chart sits immediately below the tabs, followed by the latest daily Monthly Active Users snapshot table. The first line, All, uses the official unsplit MAU from Roblox and starts disabled.
All, the top 10 and other countries are initially disabled; your line selection is saved in your account separately from other teammates. Other countries live in a collapsed group; expand it to enable or disable the entire group or one country. Countries use a flag and their full name in the selected interface language instead of a two-letter code.
The same block is used without divergence in internal analytics and investor analytics. Values from different dates are never added, missing points are not replaced with zeros, unknown categories remain explicit, and Region is omitted because the documented Analytics Query API does not return it as a separate dimension.
Stored breakdowns and fresh sync
Supported daily breakdowns are collected in the background without opening charts: countries, age, gender, platforms, operating systems, languages and other groups available for each metric. Received observations stay in MARPLA's database without age-based deletion. The queue refreshes daily data approximately every six hours and backfills history gradually; initial population is not instant.
Switching charts reads the database without waiting for a Roblox query to finish. Manual sync prioritizes the selected query and starts up to two jobs after returning the saved response; remaining work continues in the minute queue. For 30 seconds, the open chart polls only our database more frequently.
Identical clicks are limited to once per minute, with one manual batch at a time per game. Rate-limit and permission backoffs remain enforced; pending operations resume without being recreated. Partial responses never clear saved points.
Countries are unavailable for RFYPlayThroughRate (Home play-through conversion): the official API supports only AgeGroupV2 and Gender. ItemMonetizationRevenue supports products and sales locations, but not countries; use DailyRevenue for revenue by country. Technical metrics also have their own dimension lists.
Unsupported choices are marked, and missing data is never replaced with zero. Daily metrics and delayed cohorts appear only when Roblox makes them available. Server and player counters share the same live dots; primary chart values and Robux use large primary-color figures with inline trends.