> ## 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. # Total Event Volume, Amplitude > Total Event Volume for Amplitude stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it. **Card class:** [Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## 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. | | | | --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | The total number of tracked events Amplitude recorded across all event types and users during the selected window. | | **Sample type** | Backend API data from Amplitude, refreshed on the standard data refresh. | | **Why it matters** | Event volume is the foundation every other Amplitude metric is computed from. A steep, broad drop almost always means the SDK or a core event stopped firing, not that demand vanished. | | **Reading the value** | Watch the trend across today, 7-day, and 30-day windows. Steady or growing volume that tracks your active users is healthy; an abrupt fall well past the alert is a tracking emergency. | | **Currency** | count | | **Time window** | `T/7D/30D vsP` | | **Alert trigger** | `drop >25% vsP (= tracking broken)` | | **Sentiment key** | `amp_event_volume` | | **Roles** | owner, marketing | ## 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 | Card | Why merchants reach for it | | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | [`amp_top_events`](/nerve-centre/kpi-cards/amplitude/top-10-events-by-volume) | Top 10 Events by Volume shows which event types make up the total and which one dropped. | | [`amp_alert_event_volume_drop`](/nerve-centre/kpi-cards/amplitude/event-volume-drop-25-vs-baseline) | Event Volume Drop alert is the dedicated tripwire for this card's failure mode. | | [`amp_core_events_firing`](/nerve-centre/kpi-cards/amplitude/core-events-firing-purchase-add-to-cart) | Core Events Firing confirms whether purchase and add-to-cart are still reporting. | | [`amp_platform_split`](/nerve-centre/kpi-cards/amplitude/event-volume-by-platform) | Event Volume by Platform isolates whether a drop is web, iOS, or Android only. | | [`amp_dau`](/nerve-centre/kpi-cards/amplitude/daily-active-users) | Daily Active Users tells you whether a volume drop is tracking or genuine audience loss. | ## 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:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------ | | **Period boundary.** Vortex IQ uses today, 7-day, and 30-day rolling windows; Amplitude charts may use calendar periods or custom ranges. | Variable | Match the date range and interval. | | **Time zone.** Amplitude buckets events by the project time zone; Vortex IQ aligns to the merchant reporting time zone. | Marginal | Confirm both use the same time zone. | | **Filter or event scope.** Profile-level filters or excluded event types may narrow the Vortex IQ view versus an all-events Amplitude chart. | Variable | Align the event and segment filters. | **Cross-connector reconciliation:** complement with sibling cards in the same category for the full diagnostic picture. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Total Event Volume update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals during a suspected tracking break, force a manual refresh from the dashboard. **Q: Why does my Amplitude dashboard show a different number?** The most common reasons are period-boundary differences (Vortex IQ uses rolling windows vs Amplitude's calendar or custom ranges), time-zone alignment, and event-scope differences (profile-level filters or excluded event types vs an all-events Amplitude chart). Match these settings before assuming a real divergence. **Q: How does Total Event Volume relate to other engagement metrics?** Event volume is the raw input behind active users, events per user, and funnels. Read it next to Daily Active Users to separate tracking breaks from demand changes, and next to Top 10 Events by Volume to see exactly which event types moved. **Q: Can I customise the alert threshold?** Yes, sensitivity thresholds are configurable per profile in the Sensitivity tab. The default treats a drop greater than 25% versus the prior period as a likely tracking break; adjust it to match your store's normal day-to-day variance. *** ### Tracked live in Vortex IQ Nerve Centre *Total Event Volume* is one of hundreds of KPI pulses Vortex IQ tracks across Amplitude 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.