BC-0112 · CORE GUIDE
Editorial review 2026-09-26
Roblox Build Analytics Management
If an app summary and a Creator Dashboard report appear to disagree, reconcile their scope before using either value to change the game. At RDC, Roblox described reviewing analytics from the app as part of the developing Build and Studio connection. That announcement does not establish identical reports across surfaces.
Objective
Reconcile an apparent cross-surface analytics discrepancy before using it for a gameplay decision.
Before you start
- Identify the actual surfaces and game destinations being compared.
- Use only reports the account is authorized to view.
- Accept an unresolved comparison when definitions or settings are absent.
Steps
- Record both game identities and metric definitions where shown.
- Compare aggregation, interval, timezone and filters without filling missing fields.
- Note update timestamps only when supplied by the report.
- Classify the pair as comparable, different-scope, unavailable or unresolved.
- Resolve the scope question before using the values in the separate gameplay analytics workflow.
Verification
- A total and an average are not treated as the same quantity.
- Unavailable report data is not replaced with zero.
- Matching labels do not silently supply missing definitions.
- The final record has a comparison class and no invented corrected value.
Limitations
- This page does not retrieve private account analytics.
- No specific inline Build metric or synchronization interval is promised.
- Aligned report scope still does not prove that a game change caused a measured difference.
Working notes
Make a side-by-side record of the actual surfaces, not an assumed Build dashboard. For each value, copy the game identity, metric label and definition if supplied, aggregation, interval, timezone, filter and update time only when shown. An absent field remains unknown rather than inheriting the other report's setting.
Check identity and definition before comparing values. Similar game titles can refer to different destinations, and a total over an interval is not the same quantity as an average or latest value. A label match alone does not establish compatible definitions.
Classify the comparison before interpreting the difference. Use comparable when the relevant scope aligns, different-scope when a known field differs, unavailable when a report cannot be accessed, and unresolved when the necessary definition is missing. Do not average the values or choose the more favorable one as a correction.
Only a comparable record can move to the separate analytics guide's gameplay diagnosis. Even then, a difference is not a causal explanation. If scope remains unresolved, the useful output is a precise question about the report, not a prompt edit based on an invented reconciled metric.
Examples
- Hypothetical mismatch: an app summary shows a period total while a Hub chart shows a daily average for the same game. Classification = different-scope. Next action = find genuinely matching definitions and intervals if the controls allow it, not divide or multiply by a guessed duration.
- Unresolved example: both labels look similar, but the app surface does not show the aggregation or update time. Record those fields as unknown and postpone the comparison rather than assuming the values refreshed together.
- Reconciliation output: left surface and game / right surface and game / definition match / aggregation match / time and filter match / missing fields / comparison class / next documentation question. An inaccessible right-hand report is unavailable, not a measured zero.