What causes analytics dashboard numbers off from timezone bucketing?

Different queries floor timestamps to a day in different timezones, so the same data produces shifted daily totals across reports.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix Analytics Dashboard Numbers Off From Timezone Bucketing

Quick answer: Pick one canonical timezone (usually UTC) for all day/week bucketing, convert in the query layer, and document the choice so every dashboard agrees.

Your install dashboard and revenue dashboard show different daily totals because one buckets in UTC and the other in local time. Standardizing the bucketing timezone makes them reconcile.

How to fix it

1. Bucket in one timezone

Convert every timestamp to a single canonical zone before flooring to day or week. Mixing local and UTC bucketing is what shifts totals by a day.

2. Centralize the date logic

Put the day-bucketing expression in a shared view or macro so every dashboard inherits the same definition. Copy-pasted ad-hoc date math drifts apart over time.

3. Document the convention

State clearly that 'day' means a UTC calendar day (or whichever zone you chose) so analysts do not silently reintroduce local-time buckets. Ambiguity here is the root of the mismatch.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Most of the time the fix is small. Seeing the failure clearly is the part that actually costs you.