HKT cohorts and tool adoption ghosts

Day-one adoption can move when clocks and user IDs move—not when the tool does.

Person working on a laptop at a desk

Teams serving users in Hong Kong often mix UTC warehouse timestamps with HKT product calendars. A cohort day that spans the wrong midnight shifts every adoption cell without anyone shipping a feature.

SDK upgrades that change anonymous-to-known stitching create similar ghosts: returning users appear as new cohorts, and week-four rates look healthier or worse depending on merge rules.

Before celebrating a tool-adoption lift, list SDK versions, identity rules, and timezone settings beside the chart. If those moved, treat the chart as suspect until you rebuild the cohort from raw events.

All notes Talk through a similar issue