At a glance
Top 10 Events by Volume ranks your most frequently fired Amplitude events over the window, from the highest count down. It is the quickest way to see what your tracking is actually capturing and in what proportion: page views and session starts usually dominate, with add-to-cart, checkout, and purchase further down the list. Merchants use this card both to confirm the right events are present in the expected order and to spot anomalies, like a core commerce event sliding down the ranking or a rogue event suddenly appearing near the top.
| What it counts | The ten most frequently recorded Amplitude event types over the window, each with its total event count, ranked highest to lowest. |
| Sample type | Backend API data from Amplitude, refreshed on the standard data refresh. |
| Why it matters | It shows the composition of your event volume at a glance. A core commerce event dropping in rank, or an unexpected event surging, is an early sign of a tracking or behaviour change. |
| Reading the value | Read the ranking and the relative counts. Confirm expected events (views, add-to-cart, purchase) appear in sensible positions and watch for sudden reordering. |
| Currency | count |
| Time window | 30D |
| Alert trigger | - |
| Sentiment key | amp_top_events |
| Roles | owner, marketing |
Calculation
Top 10 Events by Volume counts every tracked event by type over the window and returns the ten with the highest totals, ranked in descending order. Counts are raw event totals with no per-user deduplication, so a single heavily active user can lift an event’s rank. Vortex IQ reads this from the Amplitude integration for the current window. 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 Top 10 Events by Volume for a typical merchant on Amplitude. Imagine the list reads, in order: Page Viewed at 620,000, Session Start at 410,000, Product Viewed at 180,000, Add to Cart at 52,000, Begin Checkout at 21,000, and Purchase at 9,000, followed by a few custom events. That shape is healthy: a wide top funnel narrowing toward purchase. Now suppose next month Add to Cart slips below a newly appeared event called “promo_modal_view” that wasn’t in last month’s list. That reordering is worth a look, it may mean a new popup is firing aggressively while the add-to-cart event lost coverage on a template. Vortex Mind compares the ranking against the prior period to flag which events rose, fell, or are brand new, and Ask Viq lets you ask, in plain English, “which events changed rank this month and is add-to-cart still firing normally” without opening Event Segmentation.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
amp_event_volume | Total Event Volume is the sum this ranking breaks down into its top contributors. |
amp_core_events_firing | Core Events Firing confirms the commerce events on this list are still reporting. |
amp_event_taxonomy_drift | Event Taxonomy Drift flags new or unexpected events appearing in the ranking. |
amp_platform_split | Event Volume by Platform shows whether a top event skews to one device or channel. |
amp_alert_event_volume_drop | Event Volume Drop alert fires when a key event in this list collapses. |
Reconciling against Amplitude
Where to look in Amplitude’s own dashboard: Use Event Segmentation in Amplitude with the “totals” measure and group by event type, then sort by count to see the same ranking. The Data section’s event list and volume views also show per-event throughput and are useful for confirming an event’s count and whether it is still active. Match the date range, interval, and any event or segment filters to the Vortex IQ profile before comparing positions. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ uses a 30-day rolling window; Amplitude charts may use calendar months or custom ranges, which can shuffle borderline ranks. | 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 change which events qualify for the top ten. | Variable | Align the event and segment filters. |