Writing session rules that survive feature releases
How to keep session definitions stable when product teams ship new screens every sprint.
Feature releases rearrange screens, but session analytics still need a steady backbone. Without a written rule set, every new modal or deep link invents another way to start or end a visit.
Begin with idle timeout and backgrounding behaviour. Decide whether a phone app that sits unused for twenty minutes should close the session, and whether desktop tabs left overnight count as one long visit or many. Write the answer once, then test it after each major release.
Name journey steps independently of UI chrome. If ‘checkout_start’ only fires on a button that designers later rename, your history breaks. Prefer intent-based names tied to business moments: request submitted, payment authorised, support chat opened.
Cross-device session analytics depend on that discipline. When mobile and desktop teams ship on different calendars, a shared dictionary keeps comparative reports honest.
Review the dictionary quarterly with product and analytics together. The meeting is short when the rules are short; the cost of skipping it appears as unexplained spikes after every launch.