11 March 2026 · Aisha Rahman
Stop naming events button_click
If the name describes the control, not the action, the funnel dies the moment the designer moves the control.
A product designer in Bukit Bintang moved the checkout confirmation from a green bar at the bottom of the screen to a card in the middle. Engineering kept the old tracker call. Analytics kept a funnel named checkout_button_click. For six weeks the report showed a collapse. Nobody had stopped paying.
button_click, cta_tap, and submit_success describe the control. They do not describe the business action. When the control changes, the name becomes a lie, and the lie is expensive because people trust the chart before they trust the designer.
We ask teams to name the action the person meant. checkout_started, payment_method_selected, order_placed. The control can move. The action still has a sentence in the dictionary.
There is a place for UI detail: a property, not the event name. component: sticky_bar is useful when you are testing layouts. It is not useful as the only label the company will ever search.
If your export is full of clicks and taps, do not add more of them this sprint. Pick one flow, rename the rows to the action, and put the control in a property. The next design change will not require a forensic investigation.