Quick answer: Anchor each user's cohort to a fixed install timestamp, compute return days as whole-day offsets in a single timezone (usually UTC), and define D1 as a return on calendar-day install+1.

Retention curves look noisy or impossible (D7 higher than D1) when device clocks and timezones drift the day boundaries. Pinning everything to UTC day offsets stabilizes the cohorts.

How to fix it

1. Pin the cohort timestamp

Store each user's first-seen time once and treat it as immutable. All retention offsets are measured relative to that single anchor.

2. Compute day offsets in one timezone

Convert event timestamps to a single zone (UTC) before flooring to a day, then subtract install day. Mixing local zones is what scatters returns into adjacent buckets.

3. Define D-N consistently

Decide whether D1 means return on install_day+1 (classic) or within 24-48h, and apply it identically across cohorts. An inconsistent definition is what makes D7 exceed D1.

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.