Data & methodology

MARPLA CCU history essentials

The CCU chart is a history of points MARPLA actually observed. The collector has scheduled opportunities, but a five-minute bucket is a target for parts of the system, not a promise that every game receives a point every five minutes. Rotation, request limits, rate limiting, partial upstream responses, and new discoveries can leave gaps.

MARPLA team · Published 2026-09-18 · 2 min read

Action essentials

The full topicObserved CCU history for Roblox games Knowledge sectionData & methodology →

Original conceptual diagram. Not a product interface or measured results.

Treat missingness as part of the evidence

Check the latest timestamp, interval spacing, and coverage before using a peak, trough, or percentage change. Do not interpolate a long gap and present it as observed behavior. Compare games over the intersection of their covered windows, or clearly label unequal coverage.

CCU measures concurrency at each snapshot. Its area over time can support a cautious public session estimate when paired with Visits increments, but the result remains derived and can be distorted by delayed counters. It does not turn into DAU, retention, or revenue. Use authorized owner analytics when the decision requires those measures.

When the line is sparse, the correct next step is another observation or a wider supported window, not a smoother curve drawn from assumptions.

Confirm the last observed time.
Mark gaps and exclude unsupported intervals.
Compare matching covered windows.
Carry the limitation into the final decision note.

Primary sources

Put this into practice in MARPLA

Open CCU history and set its range and interval. Check observation dates and gaps before concluding that the game declined or an update had an effect.

Open the tool →