Application analytics debt often looks like messy property names. The deeper issue is that nobody mapped which product paths those properties belong to.
Start with three journeys that create value — signup to activation, first paid action, invite or share. List the events that prove each step happened. Only then rename or prune properties.
Teams in Seoul that reverse this order usually dual-write for months and still lose historical comparisons. A path map shortens the dual-write window because everyone knows which events are load-bearing.
Keep the path map next to the dictionary. When a feature launches, engineers check both: which path changed, and which events must fire for that path to stay trustworthy.