At a glance
Amplitude Tracking Health Score is a composite gauge that rolls four signals into one number: whether your core events are firing, whether funnel conversion is stable, whether retention looks healthy, and whether attribution shows no unexpected drift. Rather than asking merchants to watch a dozen instrumentation cards, this single score answers the question “can I trust my Amplitude data right now?” A high score means your analytics foundation is solid; a falling score is an early signal that something in tracking, conversion, or attribution has started to wobble before it shows up in revenue.
| What it counts | A composite of four health signals: core events firing, funnel conversion stable, retention healthy, and no attribution drift, combined into a single score. |
| Sample type | Backend API data from Amplitude, refreshed on the standard data refresh. |
| Why it matters | It is the fastest single read on whether your Amplitude data can be trusted. A dip flags instrumentation, conversion, or attribution trouble before it reaches downstream reports. |
| Reading the value | Higher is healthier. A score below the alert threshold means at least one of the four component signals has degraded; drill into the contributing cards to find which one. |
| Currency | count |
| Time window | RT/7D |
| Alert trigger | <70 |
| Sentiment key | amp_health_score |
| Roles | owner, marketing |
Calculation
Amplitude Tracking Health Score is a composite built from four component checks - core events firing, funnel conversion stable, retention healthy, and no attribution drift - each contributing to a single combined score that Vortex IQ refreshes in near real time. A weakness in any one component pulls the overall score down, so a falling number points you toward whichever signal has degraded rather than giving a single root cause. 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 Amplitude Tracking Health Score for a typical merchant on Amplitude. Suppose the gauge sits at 92 for most of the month, with all four components green: core events firing, funnel conversion holding, retention steady, and attribution clean. After a Friday deploy the score slides to 64, below the alert threshold of 70. The drop is not evenly spread: core events and retention are still healthy, but the funnel-conversion-stable and attribution components have weakened, hinting that a checkout step regressed and a UTM tag was lost in the same release. Vortex Mind decomposes the composite, shows which two of the four signals pulled the score down, and traces them to the deploy window. Ask Viq lets you ask, in plain English, “why did my tracking health score drop on 19 Jun 26 and which component caused it” and get the breakdown without opening four separate cards.Sibling cards merchants should reference together
| Card | Why merchants reach for it |
|---|---|
amp_core_events_firing | Core Events Firing is the first component of the score; check it when the gauge dips. |
amp_alert_tracking_broken | Tracking Broken alert fires when a core event stops, the sharpest contributor to a low score. |
amp_funnel_conversion | Checkout Funnel Conversion is the funnel-stability component of the composite. |
amp_retention_d7 | D7 Retention represents the retention-healthy signal feeding the score. |
amp_event_volume | Total Event Volume gives the raw evidence behind a core-events or attribution dip. |
Reconciling against Amplitude
Where to look in Amplitude’s own dashboard: This score is a Vortex IQ composite, so Amplitude has no single matching number; instead you reconcile each component separately. Use Event Segmentation to confirm core events are firing, the Funnels report to check conversion stability, the Retention report for the retention component, and your attribution or marketing dashboards for drift. The Data section’s event volume and ingestion views help verify the tracking foundation underneath all four. Match the date range and segments across each report to the Vortex IQ profile. Why the Vortex IQ value may legitimately differ:| Reason | Direction | What to do |
|---|---|---|
| Period boundary. Vortex IQ blends a real-time read with a 7-day view; Amplitude’s individual reports may use different ranges per component. | Variable | Match the date range on each component report. |
| 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 segment scope. Profile-level filters narrow the Vortex IQ view; an all-account Amplitude report will look broader. | Variable | Align segment and event filters across components. |