At a glance
Total Event Volume is the count of all tracked events Amplitude ingested for your store across the selected window, summed over every event type and every user. In product analytics this is the heartbeat of your instrumentation: page views, add-to-carts, purchases, custom events, all rolled into one number. Because almost every other Amplitude metric is built on these events, a sudden collapse in total volume is the single clearest early warning that tracking has broken, which is why this card carries a tracking-broken alert.
Calculation
Total Event Volume sums every tracked event Amplitude ingested for the store over the selected window, across all event types and all users, with no deduplication: a single user firing ten events contributes ten. Vortex IQ reads this from the Amplitude integration for the current window and compares it against the equivalent prior period. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A representative reading of Total Event Volume for a typical merchant on Amplitude. Suppose the card shows 1.20 million events for the current period against a prior-period baseline of roughly 1.18 million, a flat-to-slightly-up read that mirrors steady Daily Active Users. The next day the card reads 840,000, a fall of around 30% versus the prior period, comfortably past the tracking-broken alert. Crucially, DAU barely moved, so the audience did not shrink by a third overnight. That pattern, volume cratering while users hold, is the classic fingerprint of a broken event: a deploy that dropped the add-to-cart call, an analytics tag removed from a template, or an SDK that failed to initialise on mobile. Vortex Mind traces the drop to the specific event types that stopped firing and the platform they came from, and Ask Viq lets you ask, in plain English, “which events stopped firing yesterday and on which platform” so you can route the fix to the right team fast.Sibling cards merchants should reference together
Reconciling against Amplitude
Where to look in Amplitude’s own dashboard: Use Event Segmentation in Amplitude with the “totals” measure across all events to read total volume, or open a Dashboard tile that sums event counts. The Data section’s ingestion and event volume views show throughput over time and are the fastest place to confirm whether a drop is ingestion-wide or limited to specific events. Confirm the date range, interval, and whether any event filters are applied before comparing. Why the Vortex IQ value may legitimately differ:
Cross-connector reconciliation: complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind.