Upstream contribution · retentioneering/retentioneering-tools
retentioneering-tools · Making Retentioneering calendar-day metrics independent of the host
Problem
DuckDB resolved timezone-aware timestamps to calendar dates in the session timezone. Identical events around UTC midnight could count as one or two active days on different machines.
Engineering response
The SQL expression now converts timezone-aware inputs through UTC before taking the date. The same rule serves metrics, daily states and conditional event collapse, and naive timestamps use their direct date cast.
Evidence and scope
The PR records a two-event fixture under four host timezones. Three previously reported one active day and all four reported two after the correction.