Investor reports
Limited access and comparative benchmarks.
Quick start
- 1The header shows public root-place servers before Playing now. The count uses the complete Roblox list, includes full servers and refreshes in the background at most once every five minutes, with a fifteen-minute pause after failure. Private and reserved servers are outside that API list. Missing or incomplete lists are never estimated from CCU or replaced with zero. Observations older than fifteen minutes display as a dash. Observation time is in the tooltip, not a separate row.
- 2Share copies one public report link for every investor, without personalization. Each card's game value, P50, P90 and percentile come from one official snapshot for the selected period. A historical day/7d pair no longer prevents the daily fresh-scorecard check. Gauge colors follow the percentile: low values are orange, the 22nd–27th are yellow, near-median values are lime and above-median values are green. Missing percentiles are not invented.
- 3The owner opens Investor Analytics from My games and copies the permanent common link or creates a temporary expiring link.
- 4An investor opens the link without registration and chooses a report topic.
- 5Switch between Daily and 7-day average; a benchmark tile opens the corresponding chart.
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.
Automatic percentile boundaries
During daily sync, MARPLA separately requests the first-party Creator Dashboard benchmark scorecard. In one snapshot Roblox returns the current value, the experience's exact percentile, P50, P90, trend, and metric date for both daily and seven-day windows. Scorecard access uses the experience owner's permission; when it is missing, the benchmark block shows a Connect Roblox action. When exact cards are initially missing, the queue prioritizes them ahead of ordinary charts. A temporary empty response retries after 30 minutes, a partial response or 429 after one hour, and 401/403 after six hours; a complete snapshot refreshes daily. These fields are stored with their date and window, so a new response no longer removes the exact scorecard from the previous day. When the calendar moves, MARPLA uses only the selected date's snapshot and never mixes it with a neighbouring date. Owned analytics never substitutes approximate P50/P90 values or a computed gauge position. The historical P50–P90 range is also retained for daily charts; a cohort change or missing date creates a gap. The editor accepts a separate official date for each metric and can exclude a row Roblox did not return.
Which benchmarks are available
The automatic gray band is supported for metrics Roblox benchmarks across experiences: retention, playtime and sessions, ARPDAU, ARPPU, payer conversion and Home recommendation play-through. The main Analytics Query API supplies the game's line; a separate Creator Dashboard service supplies P50 and P90. MARPLA does not infer these boundaries from one game's history and does not bridge missing dates. An empty band means the exact source has not returned comparable values yet. Charts and cards appear directly, without repeated source notices or a separate empty panel while points are unavailable; sync remains available from the heading button, while actual Roblox errors are still shown separately.
P50, P90, dates & gauges
The six primary benchmarks share one compact row on wide screens. The Daily / 7-day average switch selects the window, while the shared calendar selects its end date. Daily shows the selected day; 7-day average shows the range from six days before the end date through the selected date. The arrows shift either window by one calendar day. Every card uses only points from the selected date. The metric value comes from Analytics Query API, while the exact percentile, P50, P90, and trend come from the stored Creator Dashboard response for that same date and window. Scorecard history is retained by date. The coloured gauge ends exactly at currentPercentile; without an exact scorecard for the selected date, the gauge stays neutral with no invented position or colouring.
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. On the country chart, the total of all returned countries and the top 10 start enabled and can be disabled individually. 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.
Links & restrictions
A link grants read-only access to the report. It does not grant ownership or permission to change keys, prices or ads. The permanent common link is stable for the experience, has no expiry and can be reused for different investors. For limited access, create a separate temporary link whose expiry and revocation are preserved. Do not forward links to anyone who should not see the report.