Notes ·
Identity Before Dashboards
Pretty charts lie when anonymous and logged-in sessions refuse to meet. Fix stitching first.
Teams rush to retention curves and wonder why week-one numbers wobble every release. More often than not, identity is the quiet culprit: device IDs that reset, server IDs that arrive late, and guest sessions that never merge.
Before commissioning a dashboard pack, verify three joins: anonymous to known user, web to native if you ship both, and server-side events to client timelines. Write the expected join keys in plain language.
When joins fail, fix the pipeline or accept that some charts must stay labeled provisional. Shipping a polished board on broken identity trains the organization to distrust analytics later.
Our cohort readiness work exists for this reason—so charts arrive only after the joins they depend on have been proven.