
Activity density describes how much market activity occurs per unit of time—for example, the number of trades, order-book changes, or price/probability updates per second (or per minute) in a prediction market.
It’s a useful concept because “nothing is happening” can mean either (a) the market is stable, or (b) the market is inactive and the displayed probability is becoming stale.
Activity density depends on what your feed considers an event. Common choices include:
Always specify which event types you’re counting. Two systems can report very different densities for the same market if one counts every order-book mutation and the other only counts last-trade or probability ticks.
Activity density impacts both how you interpret a market and how you engineer your data pipeline:
You’ll usually compute activity density over a rolling window.
Common metrics:
count(events) / window_secondscount(trades) / window_minutescount(events) / (window_seconds × number_of_markets) (useful for dashboards)Operationally, many teams track p95 / p99 density (not just the average) to plan for bursts.
If a market produces 240 probability updates in the last 60 seconds, its update-based activity density is:
240 / 60 = 4 updates per secondIf those 240 updates included 12 trades, then trade-based activity density is:
12 / 60 = 0.2 trades per second (12 trades per minute)Both numbers can be “true” at the same time—they answer different questions.
When you consume prediction market data programmatically, activity density helps you decide:
FinFeedAPI’s Prediction Markets API is designed for programmatic access to live and historical prediction-market probabilities and updates—so you can compute activity density consistently across markets and time windows.
