> ## 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. # Avg Events per User, Amplitude > Avg Events per User 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:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Analytics](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Avg Events per User** is the total number of tracked events divided by the number of active users over the window, a depth-of-engagement measure rather than a reach measure. Where active-user counts tell you how many people showed up, this card tells you how much each one did once they arrived: more events per user generally means more browsing, interacting, and progressing through funnels. It is a useful balance to raw audience size, because a store can grow its user count while each user does less, which often signals lower-intent traffic. | | | | --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Total tracked events divided by active users over the window, giving the average number of events each active user fired. | | **Sample type** | Backend API data from Amplitude, refreshed on the standard data refresh. | | **Why it matters** | It measures engagement depth per person, not just headcount. A falling average on rising users can mean lower-intent traffic; a rising average can mean deeper, more committed sessions. | | **Reading the value** | Compare the current 30-day window against the prior period. Read it together with active users so you can tell depth changes apart from reach changes. | | **Currency** | count | | **Time window** | `30D vsP` | | **Alert trigger** | `-` | | **Sentiment key** | `amp_events_per_user` | | **Roles** | owner, marketing | ## Calculation Avg Events per User divides total tracked event volume by the count of active users over the window, so it reflects how many events the average active person fired. Because both inputs are pulled from the same Amplitude window, the ratio moves when either engagement depth or audience composition changes. Vortex IQ reads the components from the Amplitude integration and compares the ratio 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 **Avg Events per User** for a typical merchant on Amplitude.* Suppose the card shows 14.2 events per user for the current 30-day window against a prior-period baseline of roughly 15.1, a dip of about 6%. On its own a small fall looks harmless, but pair it with a Daily Active Users card that rose over the same period and a clearer story emerges: the store pulled in more visitors, yet each new visitor is doing less, a common pattern when a broad awareness campaign brings in lower-intent traffic. Vortex Mind can confirm this by checking whether the new arrivals concentrate in shallow events like page views rather than add-to-carts, and Ask Viq lets you ask, in plain English, "did events per user drop because of new low-intent traffic or because existing users slowed down" and get the split without building a segmentation report. ## Sibling cards merchants should reference together | Card | Why merchants reach for it | | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | [`amp_avg_session_length`](/nerve-centre/kpi-cards/amplitude/avg-session-duration) | Avg Session Duration is the time-based partner to this event-based depth measure. | | [`amp_session_count`](/nerve-centre/kpi-cards/amplitude/sessions) | Sessions shows how the activity spreads across visits, not just per user. | | [`amp_event_volume`](/nerve-centre/kpi-cards/amplitude/total-event-volume) | Total Event Volume is the numerator; a volume shift drives this ratio directly. | | [`amp_dau`](/nerve-centre/kpi-cards/amplitude/daily-active-users) | Daily Active Users is the denominator context; reach changes move this average. | | [`amp_stickiness_dau_mau`](/nerve-centre/kpi-cards/amplitude/stickiness-daumau) | Stickiness (DAU/MAU) pairs depth with how habitually users return. | ## Reconciling against Amplitude **Where to look in Amplitude's own dashboard:** Use Event Segmentation in Amplitude with the "average" or "events per active user" style measure across all events to read this directly, or compute it by dividing a totals chart by a uniques chart over the same range. The Dashboards section may hold a saved engagement tile. Confirm the date range, interval, and any event or segment filters before comparing, since both the numerator and denominator must match the Vortex IQ profile. **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. | Variable | Match the date range on both inputs. | | **Time zone.** Amplitude buckets 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.** Different event sets in numerator or denominator (profile filters vs all events) change the ratio. | Variable | Align the event and segment filters on both charts. | **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 Avg Events per User update?** The card refreshes on the standard data refresh (typically every 30-60 minutes for live integrations). For real-time signals, force a manual refresh from the dashboard. **Q: Why does my Amplitude dashboard show a different number?** This ratio depends on which events count in the numerator and which users count in the denominator. Differences usually come from period boundaries (30-day rolling vs calendar months), time-zone alignment, or event and segment scope. Match those on both inputs before assuming a real divergence. **Q: How does Avg Events per User relate to other engagement metrics?** It measures depth per person, while active-user cards measure reach. Read it alongside Daily Active Users and Total Event Volume to tell whether a move is more people, more activity per person, or both, and alongside Avg Session Duration for the time-based view. **Q: Can I customise the alert threshold?** This card ships without a default alert trigger, but sensitivity thresholds are configurable per profile in the Sensitivity tab. You can add a custom threshold if you want alerts when engagement depth moves beyond your normal range. *** ### Tracked live in Vortex IQ Nerve Centre *Avg Events per User* 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.