At a glance
Total Event Volume is the raw count of every event Mixpanel ingested for your project in the period. It is the broadest possible health signal for your tracking, if events are flowing, your reports have data; if volume collapses, everything downstream is at risk. A large, sudden fall in total event volume is the single clearest sign that tracking is broken: a removed SDK, a failed deploy, a blocked snippet, or a tag-manager misconfiguration. Because it aggregates across all events, it catches breaks that a single-event check might miss, which is why a sharp drop here is treated as a tracking-broken signal rather than a quiet business slowdown.
| What it counts | The total number of all events ingested in the period across every event type, with no de-duplication by user. |
| Sample type | Backend API data from Mixpanel, an aggregate event count over the project’s full event stream. |
| Why it matters | It is the broadest tracking-health signal you have. A steep fall almost always means instrumentation broke, putting every downstream report at risk. |
| Reading the value | Watch the trend against the prior period. Steady or rising volume is healthy, a sharp drop is the alert and should be read as a tracking incident. |
| Currency | count |
| Time window | T/7D/30D vsP |
| Alert trigger | drop >25% vsP (= tracking broken) |
| Sentiment key | mix_event_volume |
| Roles | owner, marketing |
Calculation
Vortex IQ asks Mixpanel for the total number of events ingested across all event types and presents the figure for today, the last 7 days, and the last 30 days, each compared against the prior equivalent period. Unlike Daily Active Users, this is a raw event count, so a single user firing many events contributes many times. The alert latches when the current reading falls more than 25% below the prior comparable period, a threshold chosen because a drop of that size across the entire event stream is almost never organic and is treated as a tracking-broken signal.Worked example
A representative reading of Total Event Volume for a typical merchant on Mixpanel. Suppose your store typically ingests around 220,000 events a day across pageviews, product views, cart actions, and purchases. On 14 Jun 26 the daily figure reads 224,000, well within range, so no alert fires. On 15 Jun 26 a release accidentally strips the analytics initialisation from a major template, and volume falls to 158,000. That is roughly a 28% drop versus the prior comparable day, past the 25% threshold, so the alert latches and the card flags a likely tracking break. You cross-check Daily Active Users and Core Events Firing, see them fall in step, confirm the missing initialisation, and ship a fix. Volume returns to baseline the next day. 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_alert_event_volume_drop | The dedicated alert that fires on a 25% volume drop, with incident detail. |
mix_top_events | Breaks total volume down by event so you can see which event collapsed. |
mix_core_events_firing | Confirms whether the drop is one core event or the whole stream. |
mix_events_per_user | Splits volume into users versus depth, helping locate where the change sits. |
mix_dau | Daily Active Users tells you whether fewer users or fewer events caused the fall. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Open an Insights report, choose a total event count across all events, and group by day. The daily totals should match the card’s today and trailing figures. If you have filtered the report to specific events, remove the filter, the card counts the full event stream, so a filtered report will read lower. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Event scope. The report is filtered to a subset of events. | Vortex IQ reads higher because it counts all events | Remove report filters before comparing. |
| Ingestion lag. Today’s events are still arriving from the SDK. | Vortex IQ may read lower for the current day | Allow late events to land, then re-check. |
| Time zone. Day boundaries differ between the project zone and your reporting zone. | Marginal | Confirm both use the same zone. |