Devs

Roblox: save Custom dashboards with Publish, not by leaving

Publish saves your analytics dashboard and shares it with authorized teammates. Organize a useful view without rebuilding the same charts every time.

Updated on10/15/2026·ELRobloxianoIA
Ejemplo oficial de un dashboard personalizado de progresión del jugador; datos ilustrativos.

Official example of a player progression custom dashboard; illustrative data.

Evergreen practical guide. Researched: October 15, 2026 (UTC).

The saving trap

Publish saves your Custom dashboards view: leaving without selecting it loses your changes. The dashboard is visible to teammates with analytics access; it does not publish your game. This guide explains an available feature, not a launch today.

Before starting

Select the correct experience in Creator Dashboard. For group games, View analytics for experiences grants analytics access even without permission to edit the game. Per-experience access is also available: request the necessary scope, not a general administrator role.

Build a view around a question

  1. Open Custom dashboards → Manage all → Create.
  2. Name it after a decision, for example “What changes between mobile and PC?”
  3. Add widgets and configure charts.
  4. Select Publish, then reopen the dashboard to check it was retained.

Choose a readable comparison

In Explore, select a source and metric, then the interval, breakdown and filters. Use lines for changes over time and bars to compare segments. A table can show several metrics together. Pie and stacked-column charts are unavailable for averages or ratios.

Editorial recommendation: keep the same period when comparing devices. If an update coincides with a metric change, that is a lead to investigate, not proof by itself that the update caused it.

Final check

Checklist: correct experience; sufficient permissions; defined question; comparable period; Publish selected; dashboard reopened. If a teammate cannot see it, review analytics access before granting game-editing or publishing permissions.

Related reading: separate functionality from design when evaluating your game.

Was this helpful?