Add properties before you invent another event
Most “missing” signals are already present—buried under vague names and empty property bags.
- instrumentation
- properties
Teams reach for a new event whenever a dashboard question goes unanswered. Often the click already exists; the context does not. Plan, surface, and cohort belong in properties—not in five near-duplicate event names.
Keep verbs short and stable. Put experiment, plan, and entry point in properties so release archaeology stays readable after the next rebrand.
In signal inventories we run from Daegu, collapsing duplicates usually beats inventing a sixth checkout event.
Store the dictionary where engineering already looks. A slide from last quarter’s offsite will not survive the next sprint.