Timing, frequency & duplicates
When alerts arrive, how many to expect, and how duplicates are avoided.
Speed
- Prices are monitored continuously during trading hours, and alerts are created in near real time.
- Reasoning is generated right after the alert is detected. When your feed includes reasoning, this can add a short delay, usually a few minutes at most.
Trading hours
| Asset class | Monitored |
|---|---|
| Stocks, ETFs | Regular trading hours of each exchange. No pre-market or after-hours alerts. |
| Commodities, futures | Trading hours of the contract |
| Crypto, forex | 24/7 |
One alert per asset, per type, per day
The same alert type is sent at most once per asset per trading day. For example, if Apple triggers a Sharp Move Up at 10:00, it will not trigger another Sharp Move Up that day, even if it keeps rising.
Why can one move create several alerts?
Different alert types are independent. One strong move can trigger, for example:
- a Gap Down at the open, then
- a Sharp Move Down a few minutes later, and
- a 50-Day Low.
Each one is a different event and is sent once. If you prefer fewer alerts, you can exclude some types, or keep only the first alert per asset per day on your side.
How many alerts to expect
It depends on your universe, the alert types you enable and market conditions. A focused list of assets can produce a few alerts per day. A broad universe of thousands of assets can produce hundreds per day, more on volatile days.
Before you go live, your account manager can run a volume analysis on your universe.
Frequency caps
SignalWise does not cap how many alerts a user receives. Apply your own cap per user (for example, 3 notifications per day) in your notification system.