Alerts vs Fills
The Alerts vs Fills analysis tool compares alert intent with imported broker-reported fills. Use it after Backtest vs Alerts when you want to inspect what happened after a signal was generated.
What the review shows
Section titled “What the review shows”Even when alerts agree with a historical comparison, broker-reported fills can differ:
- Slippage — The difference between your intended price and actual fill price
- Latency — Delays from signal generation to reported fills
- Missing Fill Reports — Alert intents with no matching imported fill
- Partial Fills — Fills reported at different sizes than intended
This tool makes those differences inspectable. It does not submit orders or prove that a strategy is profitable.
Prerequisites
Section titled “Prerequisites”Before using Alerts vs Fills, ensure you have:
- Alpaca broker connection — Required for fill data
- Alert events — Captured webhook events or a supported alert CSV
- Basic or Professional plan — Required for this feature
Choose what you need
Section titled “Choose what you need”Review one bounded window
Section titled “Review one bounded window”The page follows this sequence:
-
Scope Definition — Select your symbol, date range, and data source
-
Automatic Matching — The engine pairs alerts with broker fills
-
Visual Audit — Review signals and fills on an interactive chart
-
Metrics Review — Analyze slippage, latency, and fill quality
-
AI Insights — Ask for a bounded review of the observed differences (optional)
Read metrics as evidence
Section titled “Read metrics as evidence”| Metric | What it describes |
|---|---|
| Match Rate | Share of alert events paired with fill reports under the selected rules |
| Latency | Time from the alert timestamp to the broker-reported fill timestamp |
| Slippage | Difference between the alert price and broker-reported fill price |
| Quantity difference | Difference between intended and reported filled size |
There is no universal “good” match rate, latency, or slippage value. Compare the distribution with the order type, liquidity, session, market conditions, and your own prior windows.
Where it fits in the validation chain
Section titled “Where it fits in the validation chain”| Aspect | Backtest vs Alerts | Alerts vs Fills |
|---|---|---|
| Purpose | Audit signal alignment | Audit reported execution differences |
| Compares | Backtest events with alerts | Alert intent with broker fill reports |
| Data Source | TradingView CSV | Alpaca broker API |
| Key Metric | Match rate | Slippage & latency |
| When to Use | Before external use | After external fills are available |
Run it
Section titled “Run it”Related documentation
Section titled “Related documentation”- Backtest vs Alerts — Audit backtest-to-alert alignment first
- Alpaca Setup — Configure broker connection
- Webhook Configuration — Set up real-time alerts
- AI Pine Editing — Fix identified issues inside Algo Lab