One journey id across many surfaces beats ten clever names
Renaming events without a shared journey contract only relocates the blindness.
Application teams serving Hong Kong clients often inherit event catalogs that pre-date the current multi-surface product. Every new hop inherits that fragmentation.
Separating environments is table stakes. Carrying a journey id and step index across surfaces is what lets journey intelligence survive the next launch. Path Attribution Design starts there.
Before celebrating a conversion lift, list which properties and surfaces changed beside the chart. Pipeline hygiene and product thrift look identical until you can tell them apart.