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.
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
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:
Cross-connector reconciliation: if your ecommerce platform reports more completed orders than the Flows path share implies, some purchases are happening outside the tracked event sequence, for example through a guest or express checkout. For divergence investigations, use Vortex Mind.