# Use Roblox Analytics to Improve Your Game

Turn player data into a focused improvement. Start with a question about the experience, inspect the relevant report, and test the change you make.

## Open the right reports

Select your experience in Creator Dashboard and open Analytics. Available reports depend on your permissions and the data available for the experience.

Choose a clear time period. Retention, engagement, acquisition, and monetization describe different parts of the experience; a rise in one does not explain every other result.

## Start with a player question

Pair a report with something you can observe:

- Players leave early: can a newcomer find and complete the first activity?
- Players do not return: is there a meaningful next goal after the first session?
- Friends struggle together: can each person join and understand the shared objective?
- A shop gets complaints: does the described benefit arrive and remain available as promised?

For a courier game, completing the first delivery is a more useful debugging target than simply adding more buildings.

## Compare like with like

Record update dates and compare similar periods and acquisition sources. A promotion can bring a different audience, which can change results independently of a gameplay repair.

Benchmarks can highlight questions, but they are not guarantees. Read our [discovery guide](/guides/roblox-discovery) for acquisition context or [monetization guide](/guides/roblox-monetization) for purchase design.

## Make one focused revision

Write the expected result before asking PromptBlox for the change. Keep unrelated systems stable so the next test is easier to interpret.

```text
New players in my courier game cannot find the first delivery destination. Add a readable world marker and one short objective hint after pickup.

Preserve the existing route, city, rewards, inventory, and movement controls. Make the hint fit a phone-sized screen without covering steering controls. Remove or update the marker when the delivery completes.

Provide a test sequence from pickup through delivery and a second attempt after respawning. Do not redesign the rest of the progression.
```

## Verify before interpreting

Complete the revised loop in [Studio](/guides/customize-in-studio), then observe the published version over a defined period. Write down both what improved and what remains uncertain.

If you need a custom event for a specific action, request and verify that instrumentation separately. Check that the event represents the intended action and is not emitted repeatedly by accident. A visible counter in a generated HUD is not proof of analytics tracking.

Keep private player information out of debugging prompts and shared notes.

## Official reference

[Roblox's analytics documentation](https://create.roblox.com/docs/production/analytics) explains available reports and current access requirements. This PromptBlox walkthrough offers an approach to interpreting them, not a promise of growth.