At a glance
Conversion-Path Share % measures the share of sessions whose Mixpanel Flows path actually reaches the purchase event. It tells you how many shoppers stay on the happy path from a starting event through to checkout, versus how many drift off into side routes, dead ends, or exits. A healthy number means most journeys follow the route you designed; a falling number means users are wandering or getting stuck somewhere upstream of purchase. Because Flows reconstructs real event sequences rather than fixed funnel steps, this card catches drift that a rigid funnel report can miss.
| What it counts | The percentage of analysed Flows sessions that include the purchase event somewhere along their path, out of all sessions that began the journey. |
| Sample type | Backend API data from Mixpanel Flows, computed over reconstructed event sequences for the window. |
| Why it matters | When the share of paths reaching purchase falls, users are drifting off the route to checkout before revenue is captured, often a sign of a new friction point or a broken link. |
| Reading the value | A higher percentage is better. Compare the current window against the prior period; a downward move means fewer journeys are completing the happy path. |
| Currency | percent |
| Time window | 30D vsP |
| Alert trigger | drop >10pp |
| Sentiment key | mix_flows_conversion_path_share |
| Roles | owner, marketing |
Calculation
Vortex IQ reads the Mixpanel Flows report that starts from your primary entry event and reconstructs the ordered sequence of events each session travels through. It then counts how many of those sessions include the designated purchase event anywhere along their path, and divides by the total number of sessions that entered the flow. The result is expressed as a percentage over a rolling 30-day window and compared against the previous 30 days. Because Flows follows the actual event order users took rather than a fixed funnel template, the share reflects every legitimate route to purchase, not just one prescribed sequence.Worked example
A representative reading of Conversion-Path Share % for a typical merchant on Mixpanel. Say that over the 30 days to 14 Jun 26, 42% of Flows sessions starting at Product Viewed eventually reached Purchase, against 51% in the prior 30 days. That 9pp slide sits just under the alert line but is clearly directional. You open Flows and see a growing branch where users go from Add to Cart back to Product Viewed instead of forward to Begin Checkout, suggesting a new doubt or friction at the cart step. The Top Exit Event card confirms more sessions now end on the cart page. You ship a shipping-cost clarification on the cart, and the path share recovers toward the prior baseline over the next two weeks. For deeper investigation, use Vortex Mind to trace upstream causes; for natural-language exploration, ask Ask Viq.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
mix_flows_top_path | Shows the single most-travelled route, the natural companion to seeing how many paths reach purchase. |
mix_flows_top_exit_event | Reveals where drifting users leave, explaining why the path share fell. |
mix_funnel_conversion | The fixed-funnel view of the same journey, useful for cross-checking the flexible Flows number. |
mix_funnel_dropoff | Pinpoints the single worst step, often the reason paths stop reaching purchase. |
mix_funnel_conversion_by_segment | Breaks the same conversion picture down by segment to see who is drifting off the path. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Open the Flows report, set the starting event to your primary entry point and the window to the last 30 days, then trace how many of the branching paths terminate at or pass through Purchase. Mixpanel renders these as proportional flow widths, so the visual share of paths reaching checkout should track the card. If you prefer a single number, build an Insights report dividing purchasing sessions by entering sessions over the same range. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Different starting event. Flows results shift depending on which entry event anchors the report. | Either direction | Confirm the card and your Flows view use the same starting event. |
| Path-length cap. Flows truncates very long sessions, so some late purchases fall outside the visible path. | Vortex IQ slightly lower | Lengthen the path depth in Flows when comparing. |
| Window edges. Sessions that span the boundary of the 30-day window count differently across tools. | Small either-way gap | Align the exact date range before comparing. |