> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Top Exit Event, Mixpanel > Top Exit Event for Mixpanel stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Flows](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Top Exit Event** names the event after which users most often leave, the last event recorded in their session path before they go. Read through Mixpanel Flows, it answers a simple but valuable question: what were people doing right before they abandoned the journey? A shift in the top exit event is one of the earliest signs of a new friction point, a broken step, or a confusing screen. The card lists the leading exit events by volume so you can see at a glance where sessions are ending. | | | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The number of sessions whose final recorded event was a given event, ranked to surface the event with the most exits after it. | | **Sample type** | Backend API data from Mixpanel Flows, derived from the terminal event of each reconstructed session path. | | **Why it matters** | The event users leave on points straight at where the journey breaks down. A changing top exit event flags a new or worsening friction point before conversion metrics fully react. | | **Reading the value** | The card is a table broken down by row, one row per exit event, ordered by how many sessions ended there. The top row is where you lose the most people. | | **Currency** | count | | **Time window** | `30D` | | **Alert trigger** | `-` | | **Sentiment key** | `mix_flows_top_exit_event` | | **Roles** | owner, marketing | ## Calculation Vortex IQ reads the Mixpanel Flows report and, for each session, identifies the terminal event, the last event before the session ended without a further action. It tallies how many sessions ended on each event over the rolling 30-day window and ranks them so the event with the most exits after it sits at the top. Because the calculation works from reconstructed event sequences rather than fixed pages, it captures exits at any point in the journey, not just on a small set of predefined steps. The card presents the ranked list rather than a single scalar, so you can compare the leading exit events side by side. ## Worked example *A representative reading of **Top Exit Event** for a typical merchant on Mixpanel.* Say that for the 30 days to 14 Jun 26 the table shows Shipping Method Selected as the top exit event with 3,180 sessions ending there, ahead of Product Viewed at 2,440 and Add to Cart at 1,910. A month earlier the top exit was Product Viewed, so the leader has shifted deeper into the funnel toward checkout. You open Flows, anchor on Shipping Method Selected, and notice exits spiked right after a courier rate change pushed shipping costs up. The Conversion-Path Share card confirms fewer paths now reach purchase. You introduce a free-shipping threshold banner at the cart, and over the next fortnight Shipping Method Selected drops back down the exit ranking. 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`](/nerve-centre/kpi-cards/mixpanel/top-user-path-flows) | Shows the dominant route into the exit, so you can see what led people to leave. | | [`mix_flows_conversion_path_share`](/nerve-centre/kpi-cards/mixpanel/conversion-path-share) | Tells you how many paths still reach purchase despite the exits. | | [`mix_funnel_dropoff`](/nerve-centre/kpi-cards/mixpanel/biggest-funnel-step-drop-off) | Quantifies the single worst step, often the same place the top exit event sits. | | [`mix_bounce_rate`](/nerve-centre/kpi-cards/mixpanel/bounce-rate) | Confirms whether exits are early single-event bounces or deeper mid-journey drop-offs. | | [`mix_funnel_conversion`](/nerve-centre/kpi-cards/mixpanel/primary-funnel-conversion) | Shows the end-to-end impact of the exits on overall conversion. | ## Reconciling against Mixpanel **Where to look in Mixpanel's own dashboard:** Open the Flows report and look at the rightmost column of each path, where Mixpanel marks sessions that ended. Group by the final event over the last 30 days and the ranking should mirror the card. You can also build an Insights report that counts sessions by their last event to get the same list in table form, which is handy for exporting or sharing. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | ----------------------------------------------------------------------------------------------------- | ------------------------------ | --------------------------------------------------------------- | | **Session timeout definition.** What counts as the end of a session depends on the inactivity window. | Shifts which event is terminal | Align the session timeout between the card and your Flows view. | | **Starting event choice.** Flows exits are relative to the configured entry point. | Reorders the ranking | Confirm both use the same starting event. | | **Late events.** Events that arrive after the session is judged ended can move the terminal event. | Small reordering | Allow for ingestion lag before comparing exact counts. | **Cross-connector reconciliation:** if your ecommerce platform shows orders coming from sessions Mixpanel marks as exited at the cart, some checkouts are completing in a flow Mixpanel is not tracking as a continued session. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Top Exit Event update?** It recomputes over a rolling 30-day window on the Nerve Centre's regular sync cadence, so the ranking reflects sustained behaviour rather than a single noisy day. **Q: Why is a high-volume event near the top of the exits?** Popular events naturally accumulate more exits simply because more sessions pass through them. Read the exit table alongside the path-share and drop-off cards to tell a genuine friction point apart from a high-traffic step that people pass through fine. **Q: The top exit event is my thank-you or order-confirmation event. Is that bad?** No. Ending on a confirmation event is a successful exit, the user finished what they came to do. Treat exits on pre-purchase events as the ones worth investigating. **Q: Can I customise the alert threshold?** This card surfaces a ranked list rather than firing a fixed numeric alert, so there is no default trigger. You can still set watch conditions and tune which events are tracked per profile in the Sensitivity tab to be notified when a specific event climbs the exit ranking. *** ### Tracked live in Vortex IQ Nerve Centre *Top Exit Event* is one of hundreds of KPI pulses Vortex IQ tracks across Mixpanel and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.