Total Event Volume, PostHog

Total Event Volume 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

Total Event Volume is an executive-overview metric tracked from PostHog data. It is the total count of all events captured, autocaptured clicks and pageviews plus your custom events, across the period. It is the single best proxy for whether your instrumentation is healthy: a stable, traffic-shaped volume means data is flowing, while a sudden fall almost always means tracking broke before it means traffic did.

What it counts	The total number of events captured by PostHog in the period, across autocapture and custom events.
Sample type	Backend API data from PostHog event counts, refreshed on the standard data refresh.
Why it matters	Every other PostHog card is built on events. Volume is the heartbeat that tells you the data layer is alive. A drop of more than 25% is treated as tracking broken.
Reading the value	Compare today, 7-day, and 30-day reads against the prior period. Expect it to roughly track traffic.
Currency	count
Time window	T/7D/30D vsP
Alert trigger	drop >25% vsP (= tracking broken)
Sentiment key	ph_event_volume
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 Total Event Volume for a typical merchant on PostHog. Suppose your store captures about 3.1 million events over 7 days. The card shows that figure tracking flat against the prior week, which means instrumentation is stable. If a CSP change on 11 May 26 blocks the PostHog snippet on mobile and 7-day volume falls to 2.0m, that 35% drop crosses the tracking-broken threshold. Cross-reference Core Events Firing and the Event Volume Drop alert to confirm whether traffic fell or capture broke. 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_alert_event_volume_drop	Nerve Centre sibling: alert when volume drops past baseline.
ph_top_events	Event Health sibling: what makes up the volume.
ph_core_events_firing	Event Health sibling: are the critical events landing.
ph_dau	Executive sibling: Daily Active Users.
ph_health_score	Executive sibling: overall tracking health.

Reconciling against the vendor’s own dashboard

Where to look in PostHog’s own dashboard:

In PostHog, a trend insight on “All events” with daily granularity gives you the volume curve. The total for the period should align with this card. Break it down by event name to understand the composition, and check whether autocapture is on, since it contributes a large share.

Why the Vortex IQ value may legitimately differ:

Reason	Direction	What to do
Autocapture toggle. Turning autocapture on or off changes volume dramatically.	Variable	Confirm autocapture configuration.
Event filtering. PostHog may exclude internal or test events from a given view.	Variable	Align the event filters.
Sampling. High-volume projects may sample in PostHog views; Vortex IQ counts the captured total.	Variable	Check for sampling in the PostHog view.

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 Total Event Volume 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: Why is my volume so high? PostHog autocapture records clicks, form interactions, and pageviews automatically, which can dwarf your custom events. That is expected. Use Top 10 Events by Volume to see the breakdown.

Q: A drop fired but traffic is fine. What broke? A volume drop with steady traffic almost always means the snippet stopped loading on a template, a content security policy blocked it, or autocapture was disabled. Check recent deploys first.

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

Total Event Volume 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.