What you will learn in this lesson
- Understand the alert frequency setting and its available options
- Recognize how the wrong frequency choice causes alert fatigue
- Set an expiration date on an alert appropriately
- Understand, at a preview level, that alerts can also trigger a webhook
The previous two lessons covered setting up price and indicator alerts. This lesson covers the practical side of actually living with several alerts running at once - specifically, the frequency setting, expiration dates, and a short preview of where alerts eventually lead in this course.
The Alert Frequency Setting
Every alert has a frequency setting controlling how often it’s allowed to fire once its underlying condition is met. Common options include:
- Once per bar - can fire as soon as the condition is true within a still-forming bar, potentially repeating if the condition flickers true and false before that bar closes.
- Once per bar close - waits for the bar to fully close before firing, generally producing a steadier, less repetitive result.
- Every time (tick by tick) - can fire repeatedly for as long as the condition remains true, without waiting for any bar to complete.
Why the Wrong Frequency Causes Alert Fatigue
Imagine a price alert set to “every time,” watching for price crossing above a specific level, on a highly active, fast-moving instrument. If price ticks just above, then back below, then above again repeatedly over a few minutes, an “every time” setting can fire on every single one of those ticks - producing a flood of near-duplicate notifications for what is, practically, one ongoing event.
"Every Time" Frequency "Once Per Bar Close" Frequency
──────────────────────── ──────────────────────────────
Tick above level → fires Bar closes above level → fires
Tick below level → (no fire) │
Tick above again → fires ▼
Tick below again → (no fire) One clean notification per
(repeats all session) completed bar, not per tickThis flood is exactly what’s meant by alert fatigue - so much notification noise that a trader starts ignoring alerts altogether, including ones that genuinely mattered. Choosing “once per bar close” for this kind of condition generally produces a steadier, more genuinely useful signal.
Setting an Expiration Date
Not every alert deserves to run forever. A time-bound setup - say, watching a level relevant only to an upcoming earnings announcement - is a good candidate for an expiration date, after which the alert automatically deactivates. This is typically set directly within the alert creation dialog, alongside the condition and notification settings.
Leaving expiration dates unset on every single alert tends to produce a cluttered, ever-growing list of old, forgotten alerts - some no longer relevant to anything currently being watched.
A Preview: Alerts Can Also Trigger a Webhook
Beyond notifications, an alert can be configured to send its trigger event to an external system automatically - a concept called a webhook. This lesson only flags that the capability exists; the full mechanics, including how a fired TradingView alert can feed into an automated trading workflow, are covered in depth starting in Module 11 (TradingView Webhooks) later in this course. For now, it’s enough to know that everything learned about conditions, frequency, and expiration in these Alerts lessons carries forward directly into that more advanced material.
Real-Life Example: Fixing a Noisy Alert Setup
Consider a trader who set five RSI-based alerts across a Bank Nifty watchlist, all left on “every time” frequency by default. Within the first hour of a volatile session, their phone had buzzed more than thirty times - most of them near-duplicate notifications for the same handful of RSI crossovers, ticking back and forth around the 70 level. Frustrated, they nearly disabled alerts altogether. Instead, they revisited each alert, switched frequency to “once per bar close,” and added a one-week expiration to two of the more short-term setups. The next session produced a handful of clean, meaningful notifications instead of dozens of noisy ones - the same underlying conditions, just configured sensibly.
Analogy: A Car Alarm That Won’t Stop Chirping
A car alarm that goes off every time a leaf brushes against the windshield quickly becomes background noise - neighbors stop reacting to it entirely, even on the rare occasion something is actually wrong. A well-calibrated alarm, tuned to trigger only for genuinely significant events, stays meaningful precisely because it doesn’t cry wolf constantly. Alert frequency settings do the same job for a trading alert system - tuned poorly, they become ignorable noise; tuned sensibly, every notification remains worth a genuine look.
Common Beginner Mistakes
- Leaving every alert on a default “every time” frequency without considering whether that’s actually appropriate for the specific condition.
- Never setting expiration dates, resulting in a long list of stale, forgotten alerts cluttering the alerts panel months later.
- Disabling alerts entirely out of frustration after experiencing alert fatigue, instead of simply adjusting the frequency setting that caused it.
- Assuming the webhook preview in this lesson means immediate action is required. Module 11 covers that material fully and separately - nothing here needs to be implemented yet.
Practical Tips
- Default to “once per bar close” for most alerts unless you have a specific reason to want tick-by-tick notifications.
- Add an expiration date to any alert tied to a specific, time-bound event or setup.
- Periodically review your active alerts list and clean out anything no longer relevant, the same way you’d tidy a cluttered watchlist.
- Treat repeated, ignorable notifications as a signal to adjust frequency, not a reason to abandon alerts altogether.
Practical Exercise
- Open an existing alert you created in an earlier lesson and check its current frequency setting. Change it if it doesn't match how you'd actually want to be notified.
- Create a new alert with a specific expiration date set roughly one week out, appropriate for a short-term setup you're currently watching.
Mini Quiz
1. What does the "alert frequency" setting control?
The frequency setting controls how repeatedly an alert can trigger once its underlying condition is met, ranging from firing only once ever, to firing every single time the condition holds true.
2. What is "alert fatigue"?
Alert fatigue happens when a poorly chosen frequency setting causes far too many notifications for the same underlying condition, leading a trader to start ignoring alerts altogether - including ones that actually mattered.
3. Which frequency choice is most likely to cause alert fatigue if a condition remains true for an extended period?
An "every time" style setting can trigger repeatedly, tick by tick, for as long as a condition stays true, quickly producing a flood of near-duplicate notifications compared to a more limited setting like once per bar close.
4. What does setting an "expiration date" on an alert accomplish?
An expiration date automatically deactivates an alert once that date passes, which is useful for time-bound setups (like a specific earnings-week watch) that shouldn't keep monitoring indefinitely.
5. According to this lesson, what does Module 11 of this course cover regarding alerts?
This lesson previews, without going into full depth, that an alert can trigger a webhook - a concept fully covered in Module 11 (TradingView Webhooks), forming a foundational piece of the automation topics covered later in this course.
6. Why is choosing the right alert frequency considered a "best practice," rather than a minor cosmetic detail?
The whole value of an alert system depends on getting notified appropriately - not too rarely (missing something important) and not too often (drowning in duplicate notifications) - which is exactly why frequency deserves deliberate attention rather than being left on a default setting blindly.
Frequently Asked Questions
What frequency options does TradingView typically offer for an alert?
Common options include firing once per bar, once per bar close, or every time the condition is true (tick by tick) - the exact wording and available choices can vary slightly depending on the alert type and current platform version.
What's the difference between "once per bar" and "once per bar close"?
"Once per bar" can fire as soon as the condition is met within a still-forming bar, which may repeat if the condition flickers true and false before the bar completes. "Once per bar close" waits until the bar fully closes before firing, generally producing a steadier, less repetitive signal.
Why would "every time" frequency cause a flood of notifications?
Because it can fire repeatedly for as long as the underlying condition remains true, potentially multiple times within a single bar as price ticks around a level - this can quickly produce many near-duplicate alerts for what is, practically speaking, a single ongoing event.
Is there a "best" universal frequency setting for every alert?
Not really - it depends on the specific use case. A one-time breakout alert might reasonably use a more conservative "once per bar close" setting, while a different scenario might call for a different choice; the key is choosing deliberately rather than leaving every alert on a default.
How do I set an expiration date on an alert?
The alert creation dialog typically includes an expiration option, letting you choose a specific date after which the alert automatically deactivates, rather than continuing to monitor indefinitely.
Should every alert have an expiration date?
Not necessarily - a genuinely ongoing setup (like a long-term support level you always want flagged) might reasonably run indefinitely, while a short-term, time-bound setup benefits from an explicit expiration to avoid stale, forgotten alerts lingering for months.
What happens to an alert once it expires?
It stops actively monitoring and firing - the alert becomes inactive, though it typically remains visible in your alerts list (sometimes marked as expired or fired) rather than disappearing without a trace.
What is a webhook, briefly, and how does it relate to alerts?
A webhook is an automated message one system sends to another when a specific event occurs. TradingView alerts can be configured to trigger a webhook when they fire, forming the basis of automated workflows - this course covers webhooks fully in Module 11.
Do I need to understand webhooks to use alerts effectively right now?
No - everything in this lesson (frequency, expiration, avoiding alert fatigue) applies fully to ordinary notification-based alerts, with no webhook knowledge required. Webhooks become relevant only once you reach Module 11's automation-focused lessons.
How many active alerts can I run at once without hitting a plan limit?
This depends on your current TradingView plan tier - free plans allow a modest number of simultaneous active alerts, with paid tiers raising that limit considerably, which matters more once you're running several indicator-based alerts across multiple watchlists.
Key Takeaways
- The alert frequency setting controls how often an alert can fire once its condition is met - options generally range from once per bar to every time the condition is true.
- Choosing too aggressive a frequency causes "alert fatigue" - so many duplicate notifications that genuinely important ones start getting ignored or missed.
- An expiration date automatically deactivates a time-bound alert, keeping your active alert list current rather than cluttered with stale setups.
- Alerts can also be configured to trigger a webhook - a foundational piece of automation covered fully in Module 11.
- There's no single universal "best" frequency - the right choice depends on the specific setup each alert is built around.
Conclusion
Choosing frequency and expiration deliberately is what keeps an alert system genuinely useful, rather than a source of ignored notification noise - and knowing that alerts can also trigger a webhook plants a seed this course returns to fully in Module 11. That closes out Alerts - the next module moves from watching the market to practicing on it, with TradingView's built-in Paper Trading feature.