At a glance
Daily Active Users is the count of unique users who fired at least one event in a given day. It is the heartbeat of your store’s engagement, the single number an owner can glance at to know whether traffic and activity are holding, growing, or slipping. In Mixpanel terms, DAU is a unique-user count over the events you treat as activity, read per day. Because it is sensitive and fast-moving, a sharp drop in DAU is often the first sign of a tracking break, a marketing pause, a site outage, or a seasonal dip. Read together with Monthly Active Users it also gives you stickiness, the ratio that tells you how habit-forming your store really is.
| What it counts | The number of distinct users who triggered at least one qualifying event during the day. Each user is counted once regardless of how many events they fired. |
| Sample type | Backend API data from Mixpanel, computed as a unique-user count over the activity event set. |
| Why it matters | DAU is the fastest top-line read on engagement. A sudden fall flags an outage, a tracking break, or a marketing change before it reaches revenue. |
| Reading the value | Higher is generally better, but read the trend, not the single day. Compare today against the prior period to separate normal weekday rhythm from a real drop. |
| Currency | count |
| Time window | T/7D/30D vsP |
| Alert trigger | drop >15% vsP |
| Sentiment key | mix_dau |
| Roles | owner, marketing |
Calculation
Vortex IQ asks Mixpanel for the count of unique users who fired at least one qualifying event on each day and presents the figure for today, the last 7 days, and the last 30 days, each compared against the prior equivalent period. A user who returns multiple times in a day is still counted once, because DAU is a distinct-user measure, not an event count. The alert latches when the current reading falls more than 15% below the prior comparable period, which filters out ordinary day-to-day noise while still catching genuine collapses in activity.Worked example
A representative reading of Daily Active Users for a typical merchant on Mixpanel. Suppose your store normally sees around 4,200 daily active users on a weekday. On 14 Jun 26 the figure reads 4,310, comfortably in range, so no alert fires. On 15 Jun 26 a tag-manager change accidentally drops the analytics snippet from the product pages, and DAU falls to 3,180. That is roughly a 26% drop versus the prior comparable day, well past the 15% threshold, so the alert latches. You see that Total Event Volume fell at the same time and in the same proportion, which points to a tracking break rather than a real loss of shoppers. You restore the snippet, confirm DAU recovers the next day, and close the incident. 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_users | Monthly Active Users gives the longer-horizon base that DAU is measured against. |
mix_stickiness | DAU/MAU stickiness turns these two counts into a single habit ratio. |
mix_event_volume | Total event volume confirms whether a DAU drop is real or a tracking break. |
mix_new_users | New users shows how much of today’s activity is first-time versus returning. |
mix_sessions | Sessions adds visit frequency on top of the unique-user count. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Open an Insights report, choose a unique-user measure over your activity event set, and group by day. The daily values should match the card’s today and trailing figures. Confirm you are using uniques rather than totals, and that the activity event set in the report matches the one the card uses, since a narrower or wider event set will move the count. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Activity event set. The events that qualify as activity differ between the report and the card. | Variable | Align the event set used in both views. |
| Ingestion lag. Today’s events are still arriving from the SDK. | Vortex IQ may read lower for the current day | Allow late events to land, then re-check before declaring a drop. |
| Time zone. Day boundaries differ between the project zone and your reporting zone. | Marginal | Confirm both use the same zone. |