Roblox analytics: what the creator dashboard shows and what it never will
The metrics Roblox reports to a world's owner, the thresholds that unlock them, where the data lags, and which numbers your own backend has to produce.
Before you agree KPIs, it helps to know what the platform can actually report. Otherwise metrics that do not exist end up in the contract, and the monthly report gets assembled by hand from screenshots.
What the creator dashboard reports
Per Roblox documentation, five groups of metrics.
Retention. How many players come back after a first visit, including day-one and day-seven rates.
Engagement. How actively players use the experience, including average session time.
Acquisition. Where players came from and how each source converts, including play-through rate.
Demographics. Age, gender, country and language for monthly active users.
Monetisation. Average revenue per paying user, average revenue per daily active user, and conversion rate.
There is also a feedback view with player comments and ratings.
The thresholds that unlock the data
The full KPI set becomes available once an experience has more than ten daily active users and more than ten play hours for seven consecutive days. In the first days after launch you are looking at a partial picture — plan for first conclusions in week two.
Chart exports are unavailable if the experience has been enrolled for less than 48 hours or had no users in the selected window. Sales data refreshes every 48 hours, so same-day reconciliation on revenue is out.
What the dashboard will never know
Your systems. The platform cannot tell that a player who took a promo code later walked into a store. Sales attribution is built by your backend: the world emits an event, your side receives it and joins it to a customer.
Funnels for your specific journey. You define the steps inside the world and you count the transitions between them.
Cost per visit. The dashboard reports behaviour, and the money spent acquiring that behaviour lives in your spreadsheet.
What to request during the brief
Three things that are far cheaper to build in than to retrofit.
Event taxonomy: which in-world actions count as steps and what they are called. Event delivery: where they are sent and in what format. Dashboard access for your own team, rather than for the agency alone.
That last one gets forgotten and it matters most — without access you receive reporting as a presentation, with the numbers already interpreted for you.
A KPI set that holds up
Unique players, average session, day-one and day-seven return, and one business event: a code issued, a form completed, an app opened. Everything else is detail the development team cares about.
Roblox game development for brands that need it to work
Hiring a freelance Roblox developer gets you a place. Getting a world that people return to is a production problem — gameplay, economy, live-ops and analytics designed together, before the first block is placed.