How to find where buyers drop out
Build a conversion funnel of two to six steps, see where buyers drop out between them, and open the people who stopped. Counted by person or by visit.
Action
An action is a named definition of the events that matter, such as Added to cart or Started checkout, used the same way in every report.
Raw event names are written for code: add_to_cart, checkout_step_1, order_completed. An action gives the events that matter a name the whole team uses, with a rule for which events count. The same action can then appear in a filter, a chart or a goal and mean the same thing each time.
Actions also absorb change. When a developer renames an event or a second checkout page goes live, the definition is updated in one place and every report that uses it follows.
In MIRA FIVE
Actions name what people do. Goals lists every action, with your goals on top and the rest under Other actions. People can be filtered by an action they took, and a goal is an action with a role: Purchase, Conversion or Intent. Claude and other agents can create actions over the Model Context Protocol (MCP), once you switch on “May change setup” for that connection.
Example
A shop that rebuilt its checkout sends begin_checkout from the old page and checkout_started from the new one. One action, Started checkout, counts both, so the goal and the reports built on it stay continuous across the switch.