Insights from ChartsWatcher
Stock Price Alerts vs Scanner Alerts: What Actually Triggers Each One?
A price alert usually watches a chosen symbol and level. A scanner alert looks for a defined event across an eligible group of symbols. They solve different research problems, even when both produce a notification.
Start with what you already know
If you already follow a stock and want to revisit it near a particular price, a fixed-symbol price alert may be enough. If you do not know which stock will meet your conditions, a scanner can search the relevant universe for you.
| Question | More directly relevant tool |
|---|---|
| Has this stock reached my chosen level? | Fixed-symbol price alert |
| Which eligible stocks are producing a defined event? | Scanner alert |
| Which stocks currently satisfy these conditions? | Screener or toplist |
Products use these labels differently. Confirm the actual trigger and universe rather than relying on the name alone.
A hypothetical example
A fixed-symbol alert might watch fictional stock XYZ for a move above $25. That does not search for other stocks or explain why XYZ reached the level.
A scanner configuration might instead combine a documented event, such as an opening-range break, with price and activity filters. Its purpose is to surface eligible symbols when that event occurs. The filters define which stocks qualify; the event defines what must happen.
Neither example is a recommended entry rule. A triggered condition is an observation to review.
An event is different from an ongoing state
“Price is above VWAP” and “price crosses above VWAP” are different statements. The first can remain true for many minutes. The second describes a transition.
This matters when an alert window is quiet: a stock can continue satisfying a condition without generating a new transition. Likewise, a toplist can contain a symbol even though no new alert has occurred.
Check the full alert specification
Before choosing a product or configuration, confirm:
- The monitored symbols and supported market sessions.
- The exact trigger, timeframe and any built-in thresholds.
- Whether it evaluates an unfinished candle or requires a completed one.
- The delivery channel, repeat behaviour and plan limits.
Do not assume every alert supports email, mobile push or SMS. Those are separate product capabilities.
ChartsWatcher's alert directory documents events, while its filter directory describes conditions used to narrow a configuration. Start with one event you can explain and inspect the result alongside a chart and available news.
If nothing appears, use the empty-scanner checklist before adding more conditions. More alerts are not automatically more useful; the goal is a clear, repeatable review process.