2 min read
Signal vs Execution: Reading the Dashboard Without Overfitting
A practical guide to interpreting signal vs execution metrics and deciding what to check next.
January 21, 2026
Signal vs Execution: Reading the Dashboard Without Overfitting
The Signal vs Execution dashboard compares what your strategy intended (alerts) with what the broker actually executed (fills). It is best used as a trend tool, not a verdict on a single trade.
Metrics to track
- Execution rate: signals that resulted in an order and a fill
- Slippage: difference between alert price and fill price
- Fill latency: time between alert and fill
- Price improvement: fills better than the alert price
How to interpret them
Execution rate should be stable. Sudden drops usually point to configuration, permissions, or market hours issues. Slippage should be evaluated by symbol and volatility regime, not as a single global number. Latency is a baseline metric. Compare against your own historical median rather than a generic target.
Practical checks
- Review missing executions and confirm whether orders were rejected or never placed.
- Filter by symbol to separate liquid from thin markets.
- Split by order type (market vs limit).
- Compare a normal week to a volatile week.
Limits to keep in mind
- Latency includes network and broker processing, not just webhook time
- Some alerts do not become orders by design (filters, risk rules)
- Fill prices depend on liquidity and order size
When metrics move
- Check webhook delivery logs
- Verify account permissions and buying power
- Review order type and size
- Consider tightening or widening alert filters during volatile periods
Closing note
Use the dashboard to find patterns, make one change at a time, and re-check the baseline. Consistency matters more than perfect numbers.
Tags:
Analytics