PostHog Tracking Health Score, PostHog

PostHog Tracking Health Score for PostHog stores. Tracked live in Vortex IQ Nerve Centre. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Analytics

At a glance

PostHog Tracking Health Score is an executive-overview gauge tracked from PostHog data. It rolls several data-integrity signals, core events firing, event volume stability, and session-replay coverage, into a single 0 to 100 score. It exists so a non-technical owner can answer one question at a glance: can I trust the numbers on this dashboard today? A score below 70 means at least one part of your instrumentation needs attention before you act on the data.

What it counts	A composite 0 to 100 score summarising tracking integrity across event firing, volume stability, and replay coverage.
Sample type	Backend API data from PostHog, combined into a single health gauge on the standard data refresh.
Why it matters	It is the trust dial for the whole PostHog connector. A healthy score means every other card can be relied on; a low score means investigate before deciding.
Reading the value	Read the gauge band. Below 70 signals degraded tracking; drill into the component cards to find which signal pulled it down.
Currency	count
Time window	RT/7D
Alert trigger	<70
Sentiment key	ph_health_score
Roles	owner, marketing

Calculation

Calculated automatically from your PostHog data. 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 PostHog Tracking Health Score for a typical merchant on PostHog. Suppose the gauge sits at 92 all month: every core event is firing, volume is stable, and replay coverage is high. After a deploy on 12 Jun 26 drops the snippet from the cart page, core events fall to 5 of 6 and the score drops to 64, below the 70 threshold. The single gauge flags the problem even before you open the detailed cards. Drill into Core Events Firing and Session Replay Coverage to see which component dragged the score down. 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
ph_core_events_firing	Event Health sibling: a key input to the score.
ph_event_volume	Executive sibling: volume stability input.
ph_session_replay_coverage	Session Replay sibling: capture coverage input.
ph_alert_tracking_broken	Nerve Centre sibling: a core event went silent.
ph_dau	Executive sibling: Daily Active Users.

Reconciling against the vendor’s own dashboard

Where to look in PostHog’s own dashboard:

This score is a Vortex IQ composite, so PostHog does not show the exact number. To reconcile, inspect the components in PostHog directly: the events list for core-event activity, an “All events” trend for volume stability, and the session-replay settings and capture rate for coverage. If each component looks healthy in PostHog, the score should be high.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Composite metric. No single PostHog number maps to this score.	Variable	Check each component separately.
Weighting. Components contribute by weight, so one weak signal can dominate.	Variable	Identify the lowest component.
Window blend. Real-time and 7-day inputs are blended; a brief blip may persist briefly.	Marginal	Re-check after the next refresh.

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 PostHog Tracking Health Score 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: What pulls the score down most? A core event going to zero is the most damaging single signal, because it usually means a revenue flow stopped being tracked. Volume drops and low replay coverage also lower the score.

Q: My score is 68. What do I do first? Open Core Events Firing and confirm every critical event still fires, then check Total Event Volume against its baseline. Fix the component with the largest gap before trusting downstream cards.

Q: Can I customise the alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. Adjust to match your business baseline rather than relying on the generic default.

---

Tracked live in Vortex IQ Nerve Centre

PostHog Tracking Health Score is one of hundreds of KPI pulses Vortex IQ tracks across PostHog 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 or book a demo to see this metric running on your own data.