At a glance
Top 10 Events by Volume is a horizontal bar chart of the ten highest-frequency events Mixpanel received over the period. It is the fastest way to see the shape of what your tracking actually captures: which events dominate, in what order, and whether that ranking matches what you expect. When tracking is healthy, the leaders are stable from one period to the next. When a familiar event vanishes from the list, slides down the ranking, or an unexpected event muscles to the top, that is usually a tag change, a duplicate firing, or a broken instrument worth checking before it distorts your reports.
| What it counts | The ten event names with the highest total occurrence count over the period, ranked by volume. |
| Sample type | Backend API data from Mixpanel event counts, aggregated by event name over the window. |
| Why it matters | The ranking is a quick integrity check on your instrumentation. A familiar event dropping off or an odd one surging often means a tracking change rather than a behaviour change. |
| Reading the value | Read the bars top to bottom by volume. Compare the order and the names against the previous period; surprises in either are the signal worth chasing. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | mix_top_events |
| Roles | owner, marketing |
Calculation
Vortex IQ aggregates total event counts by event name from Mixpanel over the trailing 30 days, ranks them, and renders the top ten as horizontal bars. Each bar is the total number of times that named event was received in the window, so the chart reflects raw frequency rather than unique users. The composition is as informative as the counts: a stable set of leaders in a stable order indicates healthy tracking, while a newcomer in the top ten or a familiar event falling out of it points to an instrumentation change. The chart pairs naturally with total event volume, which gives the grand total these bars sum toward.Worked example
A representative reading of Top 10 Events by Volume for a typical merchant on Mixpanel. Imagine your usual top five over the last 30 days reads Page Viewed at 4.1M, Product Viewed at 1.8M, Add to Cart at 520K, Search at 410K, and Checkout Started at 190K. After a tag-manager change on 14 Jun 26, the next period shows a new event, Banner Impression, leaping to second place at 2.4M while Product Viewed slips and the totals look inflated. The surge is not new shopper behaviour; it is a newly added, very chatty event double-counting impressions. You spot it instantly from the ranking, confirm the duplicate firing, and fix the tag before it skews your funnels. 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_event_volume | The grand total these top events sum toward; read them together to see composition versus scale. |
mix_core_events_firing | Confirms your named core events are present and healthy, not just the noisiest ones. |
mix_events_per_user | Shows whether high volume reflects more users or each user firing more events. |
mix_ingestion_lag | Explains a temporary dip in the ranking when events are arriving late. |
mix_health_score | Rolls event health into one number when the ranking looks off. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Build an Insights report counting all events, grouped by event name, over the last 30 days, and sort descending. The top ten names and their counts should match the bars on the card. The Events view also lists your tracked events and their recent volume, which is handy for confirming whether a name that dropped off the chart has genuinely gone quiet or simply fallen below tenth place. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Excluded or filtered events. Project data views can hide events from the total. | Ranking differs | Match the event set and any data-view filters used by the card. |
| Late-arriving events. Batched SDK data can understate the newest part of the window. | Counts read low transiently | Re-check after the SDK flush interval before reading the order. |
| Merged or renamed events. A renamed event splits its volume across two names. | A familiar event drops in rank | Account for recent event renames when comparing periods. |