Map the connected path before you commission another funnel board
A polished funnel on untagged hops only accelerates the wrong debate.
Teams under pressure often skip journey ids and jump to a new conversion board. Weeks later, growth and engineering argue over different drop-off totals for the same path because every hop still invents its own vocabulary.
Prefer shared journey and step tags over UI widget names. Keep environment out of the event alias and in a property. Write allowed values the same day a new cloud-connected surface ships—or the path becomes a free-form dump.
In a Connected Journey Audit we spend early days on the inventory, not on chart cosmetics. Boards get sharper only after the journey map stops arguing with itself.