Skip to main content

Compare Plan statistics using consistent dates and timezones

Applies to: Plan; match the linked maintainer documentation to your installed platform and release.
Documentation checked .

Two Plan screenshots can disagree because they cover different dates, timezones or server scopes. Before treating a graph difference as missing data, make the comparison explicit. A network total and one backend's session list do not necessarily measure the same population.

Record the starting point

Choose the question first, such as how many sessions occurred during one scheduled event. Record the event's start and end with its timezone. Note which server or network view each staff member opened and whether a player or date filter remains active.

Work through the change

  1. Open the intended Plan view and set the same date range on both comparisons. Check the displayed timezone and the release's documented time settings before changing server configuration.
  2. Select the same server scope and player filters. Keep network-wide movement separate from a single backend's activity when players transfer during the event.
  3. Inspect a known test session near the time boundary. Compare its timestamp with the server log to determine whether the apparent shift is a display-time difference.
  4. Save the final comparison with the date range, timezone and scope visible or written in its caption. Explain what metric is being compared rather than reporting an unlabelled percentage.

Check the result

The two views should refer to the same period and population. Differences that remain after alignment are worth investigating through collection and storage logs. Keep the original screenshots privately so staff can explain the initial discrepancy without changing historical records.

If the result differs

If a boundary session moves between days as the timezone changes, that is a grouping difference rather than evidence of deletion. If the same session is absent from every relevant range, investigate collection separately. Avoid changing the machine clock to make a graph match a screenshot.

Restore the previous display preference if a trial setting confuses other staff. Record any intentional timezone change in reporting notes. Keep analytics records intact; comparison work does not require database edits or deletion of sessions outside the selected period.

References and related help

No comments to display