At a glance
Funnel Conversion Drop (>5pp in 24h) is a real-time alert built on top of your Mixpanel funnel report. It fires when the conversion rate of your primary purchase funnel falls by more than five percentage points inside a rolling 24-hour window. A sudden drop of that size is rarely organic, it usually points to a broken step (checkout error, payment gateway failure, JavaScript regression) or a tracking break that makes a step look empty. This is one of the fastest ways to catch a revenue leak before it shows up in the day’s sales figures.
| What it counts | The day-over-day change, in percentage points, of your Primary Funnel Conversion rate. The alert latches when the most recent 24h reading is more than 5pp below the prior 24h reading. |
| Sample type | Backend API data from Mixpanel funnel reports, evaluated in real time against the rolling baseline. |
| Why it matters | A 5pp swing on a funnel that normally converts in the low single digits can mean a large share of in-progress buyers are now stalling. The alert turns a slow-moving funnel report into an immediate signal. |
| Reading the value | The card lists each active alert with the funnel name, the prior rate, the current rate, and the gap. Treat any open alert as a checkout or tracking incident until proven otherwise. |
| Currency | count |
| Time window | RT |
| Alert trigger | primary funnel conversion down >5pp in 24h |
| Sentiment key | mix_alert_conversion_drop |
| Roles | owner, marketing |
Calculation
Vortex IQ pulls the conversion rate of your designated primary funnel from Mixpanel on a rolling basis and compares the latest 24-hour reading against the immediately preceding 24-hour reading. When the absolute fall exceeds the configured threshold (five percentage points by default), the alert latches and surfaces on the card. The comparison is in percentage points, not percent change, so a move from 4.0% to 1.5% counts as a 2.5pp drop, not a 62% drop.Worked example
A representative reading of Funnel Conversion Drop (>5pp in 24h) for a typical merchant on Mixpanel. Suppose your primary funnel (View Product, Add to Cart, Begin Checkout, Purchase) normally converts end to end at around 8.4%. Overnight a payment provider starts rejecting one card type, and the next 24-hour reading lands at 2.9%. That is a 5.5pp fall, past the threshold, so the alert fires. The card shows the funnel name, 8.4% prior, 2.9% current, and the offending step. You open the funnel in Mixpanel, confirm the Begin Checkout to Purchase step is where the floor dropped out, and route the incident to engineering. 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_funnel_conversion | The underlying rate this alert watches. Open it to see the full stage-by-stage funnel. |
mix_funnel_dropoff | Tells you which step lost the most users, the usual culprit behind a sudden drop. |
mix_alert_event_volume_drop | A parallel alert: if event volume also fell, the cause is likely tracking, not checkout. |
mix_alert_tracking_broken | Rules in or out a broken event as the reason a funnel step looks empty. |
mix_xc_funnel_vs_ecom_conversion | Confirms whether the platform’s own checkout numbers fell in step with Mixpanel. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Open the saved Funnels report for your primary funnel and switch the date range to the last 48 hours, broken down by day. The single-day conversion rates Mixpanel shows should bracket the prior and current figures on the card. If you use a conversion window (for example, 7-day completion), make sure the same window is set, since a shorter window will under-report conversions for the most recent day. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Conversion window. Recent conversions may still be completing inside Mixpanel’s attribution window. | Vortex IQ may read lower for the latest day | Allow the window to close, then re-check before declaring an incident. |
| Counting basis. Unique vs total conversion counting changes the rate. | Variable | Match the uniqueness setting used by the alert. |
| Time zone. Day boundaries differ between the project time zone and your reporting time zone. | Marginal | Confirm both use the same zone. |