> ## 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, Mixpanel > Avg Events per User for Mixpanel 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:** [Engagement](/nerve-centre/connectors#connectors-by-type) ## At a glance > **Avg Events per User** is the average number of events fired by each active user in the period, a simple but revealing proxy for how deeply people engage with your store. Where Daily Active Users counts how many people showed up, this card tells you how much they actually did once they arrived. A rising average suggests users are browsing more products, exploring more pages, and progressing further through funnels; a falling average can signal shallower visits, a friction point, or a tracking change that dropped some events. Read alongside stickiness and total volume, it helps you tell a story about depth of engagement rather than just reach. | | | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Total events in the period divided by the number of active users in the same period, giving the mean events per active user. | | **Sample type** | Backend API data from Mixpanel, derived from the event count and the unique active-user count. | | **Why it matters** | It measures depth of engagement, not just reach. It distinguishes a store full of quick bouncers from one where users explore and progress. | | **Reading the value** | Higher generally means deeper engagement, but read it in context, a sudden change up or down usually reflects behaviour or tracking, not noise. | | **Currency** | count | | **Time window** | `30D vsP` | | **Alert trigger** | `-` | | **Sentiment key** | `mix_events_per_user` | | **Roles** | owner, marketing | ## Calculation Vortex IQ takes the total number of events ingested over the period and divides it by the number of distinct active users in that same period, producing the mean events per active user. The figure is shown for the trailing 30 days and compared against the prior equivalent period. Because it is a ratio of two underlying numbers, a change can come from either side: more events per visit, or a shift in how many users were active. There is no fixed alert threshold on this card, it is a context and trend metric rather than an incident trigger, so you read its direction alongside DAU and total volume. ## Worked example *A representative reading of **Avg Events per User** for a typical merchant on Mixpanel.* Suppose over the 30 days to 14 Jun 26 your store ingested 6,000,000 events from 250,000 active users, giving an average of 24 events per user. In the prior 30 days the figure was 21, so engagement deepened, perhaps a new recommendations widget is prompting more product views per visit. Now imagine the next period reads 17 with users roughly flat. That fall could mean shallower sessions after a navigation change, or it could mean a secondary event stopped firing and is no longer counted. You compare against Total Event Volume and Core Events Firing to decide which story is true before acting. 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_stickiness`](/nerve-centre/kpi-cards/mixpanel/stickiness-daumau) | DAU/MAU stickiness pairs habit frequency with the depth this card measures. | | [`mix_event_volume`](/nerve-centre/kpi-cards/mixpanel/total-event-volume) | Total event volume is the numerator, useful for seeing whether a change came from events or users. | | [`mix_dau`](/nerve-centre/kpi-cards/mixpanel/daily-active-users) | Daily Active Users is the user side of the ratio, confirming whether reach or depth moved. | | [`mix_pageviews_per_session`](/nerve-centre/kpi-cards/mixpanel/pageviews-per-session) | A web-analytics view of the same depth idea, expressed per session. | | [`mix_avg_session_duration`](/nerve-centre/kpi-cards/mixpanel/avg-session-duration) | Session duration adds a time dimension to the engagement-depth picture. | ## Reconciling against Mixpanel **Where to look in Mixpanel's own dashboard:** Build an Insights report with total events over the period and a second with unique active users over the same period and event set, then divide one by the other. The result should match the card. Make sure both reports use the same date range and the same activity event definition, because a mismatch on either side will move the ratio. **Why the Vortex IQ value may legitimately differ:** | Reason | Direction | What to do | | -------------------------------------------------------------------------------------------- | ---------------------------------------------- | ------------------------------------------------- | | **Event scope.** The events counted in the numerator differ between the report and the card. | Variable | Align the event set on both sides of the ratio. | | **Active-user definition.** What counts as an active user differs between views. | Variable | Match the activity event set used to count users. | | **Ingestion lag.** Recent events have not all landed yet. | Vortex IQ may read lower for the latest period | Allow late events to land, then re-check. | **Cross-connector reconciliation:** compare this depth signal against pages per session in your web-analytics connector to confirm the two tell a consistent engagement story. For divergence investigations, use Vortex Mind. ## Known limitations / merchant FAQs **Q: How often does Avg Events per User update?** It refreshes on the card's regular cycle for the trailing 30-day window. Because it depends on both event and user counts, late-arriving events can nudge the figure until ingestion settles. **Q: Why did the average drop when nothing about my store changed?** A common cause is a tracking change that quietly removed a frequently fired event, which lowers the numerator without any real behaviour change. Check Total Event Volume and Core Events Firing before concluding that engagement actually fell. **Q: A few power users fire huge numbers of events. Do they skew the average?** Yes, because this is a mean, a small group of very active users can pull it up. If you suspect skew, look at the distribution in Mixpanel and consider reading stickiness and retention alongside it for a fuller picture. **Q: Can I customise the alert threshold?** This card ships without a fixed threshold because it is a trend and context metric, but you can configure a threshold or watch condition per profile in the Sensitivity tab if you want it to alert on large swings for your store. *** ### Tracked live in Vortex IQ Nerve Centre *Avg Events per User* is one of hundreds of KPI pulses Vortex IQ tracks across Mixpanel 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.