Compare countries and other segments
A breakdown divides a metric into lines, for example by country or device.
How to use it
- Choose an option in Breakdown by.
- With more than ten lines, use All, the top 10 and collapsed Others. All lines start disabled. Within Others, enable individual lines or the entire group.
- Compare segments over the same range and interval.
What you can compare
- No breakdown
- Total audience with one line.
- Age group
- Roblox age groups.
- Platform
- Computer, phone, tablet, console and VR.
- Operating system
- Android, iOS, Windows, macOS and other OSes.
- Gender
- Available Roblox gender categories.
- Main countries
- Countries with the largest audience.
- Main languages
- Languages with the largest audience.
- Age 18+
- Age eligibility as classified by Roblox.
- First play
- Time since the first launch of the experience.
- Experience activity
- New, active, churned and reactivated players.
- Engagement
- Number of active days in the past week.
- Experience spending
- Spending segments within the experience.
- Roblox activity
- Player activity on the Roblox platform.
- Roblox spending
- Spending status on the Roblox platform.
- New and returning
- New players and already familiar with the game.
- Acquisition source
- Home, Search, Sponsored Ads and other sources.
- Product
- Individual developer products, passes, and other Roblox products.
- Type of product
- Developer product, pass, subscription, and other product types.
- Place of sale
- The location inside the experience where the purchase was made.
- Product SKU
- Products reported by the experience in AnalyticsService events.
Advice and practical context
Share and absolute value
A breakdown shows parts of one metric. A country's rising line can mean more users there or merely a changed total audience; percentage share and absolute count answer different questions. Device and OS populations can overlap when a user plays on several platforms.
Comparing segments
If mobile share rises, inspect mobile MAU and total MAU as absolute values, then compare retention or session time over the same period. Do not label a small segment problematic from a noisy percentage without adequate sample size.
Even when segment lines appear to sum to the total, verify the table because rounding and hidden categories can defeat manual addition. With many segments, keep the key lines and overall metric visible so color noise does not replace comparison.
Technical detailsCalculations, permissions and behavior
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.