At a glance
Mixpanel Tracking Health Score is a single 0-100 read that rolls up the health of your event pipeline into one number. It blends whether event volume is holding against its baseline, whether your named core events are still firing, and whether ingestion is arriving promptly. The idea is simple: every funnel, retention curve, and DAU count in Mixpanel is only as trustworthy as the events feeding it, so this score tells you at a glance whether the data underneath your reports can be relied on today. A high score means tracking is healthy; a falling score is your cue to look before you trust the numbers.
| What it counts | A composite 0-100 quality score that combines event-volume health, core-event firing status, and ingestion timeliness into one tracking-quality read. |
| Sample type | Backend API data from Mixpanel, derived from event counts, core-event status, and ingestion timing rather than a single raw metric. |
| Why it matters | It is the fastest way to know whether your Mixpanel data is sound before you act on any individual report. One number replaces three separate checks. |
| Reading the value | Higher is better. A score near 100 means tracking is healthy; a dip toward the alert threshold means one of the inputs (volume, core events, or lag) has degraded. |
| Currency | count |
| Time window | RT/7D |
| Alert trigger | <70 |
| Sentiment key | mix_health_score |
| Roles | owner, marketing |
Calculation
Vortex IQ derives the health score by combining several tracking signals from Mixpanel into one normalised 0-100 figure. The inputs are the current event volume measured against its recent baseline, the firing status of your designated core events, and the freshness of ingestion. A real-time read is blended with a trailing 7-day view so a brief blip does not crater the score while a sustained problem clearly does. The exact weighting is tuned to surface genuine tracking faults rather than noise, and the alert latches when the composite falls below the configured threshold. Because it is a roll-up, the score tells you that something is wrong; the sibling cards tell you which input drove it.Worked example
A representative reading of Mixpanel Tracking Health Score for a typical merchant on Mixpanel. Imagine your store normally sits at a score of about 96, with volume on baseline, all core events firing, and ingestion arriving within minutes. On 14 Jun 26 a mobile release ships with a misconfigured SDK flush, so events start arriving in large delayed batches. Volume reads low in the live window and ingestion lag climbs, dragging the composite down to roughly 64, which crosses the alert threshold. The card shows the score falling and you open the siblings to see ingestion lag spiking while core events are technically still firing, just late. That points you to the SDK release rather than a removed tag. 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_core_events_firing | Confirms which named events are still arriving, one of the score’s core inputs. |
mix_event_volume | The raw volume trend the score watches against its baseline. |
mix_ingestion_lag | Shows ingestion timeliness, the freshness input that pulls the score down when events arrive late. |
mix_alert_tracking_broken | Fires when a specific core event stops, often the cause of a sudden score drop. |
mix_alert_event_volume_drop | The real-time volume alert; a fire here usually shows up in the score too. |
Reconciling against Mixpanel
Where to look in Mixpanel’s own dashboard: Mixpanel does not publish a single health score, so reconcile against its parts. Build an Insights report on total event volume for the last 7 days to confirm the volume input, check your core events in the Events view to confirm they are still firing, and look at the data-management or ingestion view for arrival timing. When all three look healthy, the score should sit high; when one degrades, the score should reflect it. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Composite weighting. The score blends three inputs, so no single Mixpanel report equals it. | Score moves before any one report looks bad | Read all three sibling inputs to see which one moved the score. |
| Real-time versus 7-day blend. A brief blip is softened by the trailing view. | Score steadier than a live raw metric | Allow for the smoothing when comparing to a real-time chart. |
| Late-arriving events. Batched SDK data lowers the live volume and lag inputs temporarily. | Score reads lower momentarily | Re-check after the SDK flush interval before treating it as a fault. |