TradingView Alerts Guide · Price · Technical · Watchlist · Multi-Condition
TradingView alerts are one of the best ways to stop watching charts all day and start monitoring only the conditions that actually matter.
In 2026, alerts are much more than simple “price reached this level” notifications. TradingView separates alerts into price alerts, technical alerts, and watchlist alerts. You can also combine multiple conditions, use indicators and drawings, work with Pine strategies, manage notification schedules, and send alert data to external apps through webhooks.
This guide shows you how to create TradingView alerts from the beginning, how the different alert types are counted, which features depend on your plan, how to avoid alert noise, and how to build a monitoring workflow you can actually trust.
New to TradingView? TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. Eligibility and offer terms are controlled by TradingView.
Key Takeaways
- TradingView now separates alerts into three resource types: price, technical, and watchlist alerts. Each type has its own active-alert limit.
- Basic currently includes 3 active price alerts. Essential adds 20 price + 20 technical alerts; Plus 100 + 100; Premium 400 + 400 plus 2 watchlist alerts; Ultimate 1,000 + 1,000 plus 15 watchlist alerts.
- Multi-condition alerts are available from Plus upward. You can combine up to five conditions on the same symbol, and the entire setup counts as one technical alert.
- Watchlist alerts monitor an entire watchlist with one condition. Each symbol is evaluated independently, and adding or removing symbols updates the alert automatically.
- Open-ended alerts are currently available on Premium and Ultimate. Watchlist alerts do not support the open-ended option.
- Indicator alerts keep the indicator settings that existed when the alert was created. Changing the indicator later does not automatically update the old alert.
- Webhook alerts require two-factor authentication. Never send passwords, credentials, or other sensitive data in the webhook message.
- The best alert system uses fewer, clearer, better-named alerts tied to a real chart, watchlist, or trading workflow.
Table of Contents
- What Are TradingView Alerts?
- Price vs Technical vs Watchlist Alerts
- TradingView Alert Limits by Plan
- How to Create Your First Alert
- Price Alerts
- Technical Alerts
- Drawing Alerts
- Multi-Condition Alerts
- Watchlist Alerts
- Trigger Frequency and Expiration
- Notifications and Alert Messages
- Alert Presets
- Webhook Alerts
- How to Manage Alerts
- A Better Alert Workflow
- Common Alert Mistakes
- Troubleshooting Alerts
- FAQ
What Are TradingView Alerts?
TradingView alerts are server-side monitoring rules. You define a condition, TradingView monitors it, and the platform notifies you when the condition is met. You do not need to keep staring at the same chart waiting for something to happen.
A simple alert might notify you when BTCUSD crosses a price level. A technical alert can monitor an RSI threshold, moving average, Pine indicator, strategy, drawing, or chart pattern. A watchlist alert can apply one condition across an entire list of symbols.
The value is not the notification itself. The value is attention management. A good alert system lets you spend less time checking charts that are doing nothing and more time reviewing the few situations that have actually reached your planned conditions.
Best beginner mindset: an alert should tell you when to review a chart. It should not automatically tell you what trade to make.
Price vs Technical vs Watchlist Alerts
Understanding the three alert types matters because TradingView counts them separately. Two alerts can look similar on the chart but consume different plan resources depending on what they monitor and which operator they use.
| Alert Type | What It Monitors | Typical Examples | Resource Pool |
|---|---|---|---|
| Price alert | A symbol and a direct price condition | Crossing, Crossing Up, Crossing Down, Greater Than, Less Than | Price-alert limit |
| Technical alert | Indicators, drawings, strategies, chart patterns, technical operators, or multiple conditions | RSI level, trendline break, moving condition, Pine strategy event | Technical-alert limit |
| Watchlist alert | One condition applied across symbols in a watchlist | Notify when any symbol in a list crosses a chosen condition | Watchlist-alert limit |
A price alert is considered a price alert only when it monitors the symbol itself with an eligible direct price operator. If you use an indicator, drawing, strategy, multiple conditions, or certain technical operators such as channel or moving conditions, the alert belongs to the technical-alert pool.
This distinction can help you use plan capacity more efficiently. If all you need is a simple level crossing, use a price alert instead of spending a technical alert on a drawing that represents the same fixed price.
TradingView Alert Limits by Plan
TradingView gives each plan separate active limits for price, technical, and watchlist alerts. These limits are one of the clearest reasons to upgrade if monitoring is central to your workflow.
| Plan | Active Price Alerts | Active Technical Alerts | Active Watchlist Alerts |
|---|---|---|---|
| Basic | 3 | — | — |
| Essential | 20 | 20 | — |
| Plus | 100 | 100 | — |
| Premium | 400 | 400 | 2 |
| Ultimate | 1,000 | 1,000 | 15 |
Do not choose a plan only by looking at the biggest number. A user with five carefully designed alerts may have a stronger system than someone with 300 alerts that are mostly ignored.
Upgrade test: if you keep deleting useful alerts only because you are hitting the active limit, that is a real plan bottleneck. If you still have unused alert capacity, better alert design is probably more important than a higher subscription.
| If This Is Your Real Need | Plan to Check First | Why |
|---|---|---|
| A few simple price alerts | Basic | 3 active price alerts may already be enough |
| Indicator, drawing, strategy, or technical alerts | Essential | First paid tier with 20 price + 20 technical alerts |
| Multi-condition alerts or much more alert capacity | Plus | 100 + 100 alerts and multi-condition alerts |
| Watchlist alerts or open-ended regular alerts | Premium | 2 watchlist alerts, 400 + 400 capacity, and open-ended regular alerts |
| Maximum alert capacity | Ultimate | 1,000 + 1,000 alerts and 15 watchlist alerts |
How to Create Your First TradingView Alert
For a beginner, the best first alert is usually a simple price alert. Open the chart you care about, create an alert, choose the symbol and condition, set the trigger behavior, choose the expiration and notification settings, write a clear message, and save it.
- Open Supercharts and choose the symbol you want to monitor.
- Open the alert dialog from the toolbar, Alerts Manager, right-click menu, drawing panel, or price scale.
- Choose the symbol or watchlist.
- Select the condition and operator.
- Choose how often the alert should trigger.
- Set an expiration date or an available open-ended option.
- Give the alert a clear name and message.
- Choose how you want TradingView to notify you.
- Review the settings once, then create the alert.
Before clicking Create, ask yourself one useful question: what will I do when this fires? If the answer is unclear, the alert condition probably needs more thought.
Price Alerts: The Best Place to Start
Price alerts are the simplest alert type and usually the easiest for beginners to trust. They monitor the symbol’s price directly instead of depending on an indicator calculation.
| Operator | What It Means | Example Use |
|---|---|---|
| Crossing | Price reaches a threshold from either direction | Notify me whenever price crosses a key level |
| Crossing Up | Price reaches the threshold from below | Resistance breakout review |
| Crossing Down | Price reaches the threshold from above | Support breakdown review |
| Greater Than | Price moves above the chosen threshold | Monitor sustained movement above a level |
| Less Than | Price moves below the chosen threshold | Monitor weakness below a level |
A strong beginner routine is simple: mark the level first, explain why it matters, then create the alert. Do not create a notification first and invent a reason afterward.
If you cannot explain why the level matters, the alert probably does not deserve your attention either.
Technical Alerts: Indicators, Strategies and Chart Patterns
Technical alerts cover much more than indicators. TradingView classifies alerts based on indicators, drawings, strategies, chart patterns, technical operators, and multi-condition setups as technical alerts.
Examples include an RSI reaching a threshold, a moving-average condition, a Pine indicator event, a strategy order event, or a chart pattern reaching a monitored condition.
Good Technical Alert
You already understand the indicator or rule, and the notification saves you from repeatedly checking the chart manually.
Bad Technical Alert
You do not understand the underlying indicator and assume the alert itself will turn the condition into a reliable trading signal.
There is also an important technical detail: when you create an alert based on an indicator or strategy, TradingView saves the relevant settings at creation time. If you later change the indicator parameters on the chart, the existing alert can continue using the older settings.
Whenever you materially change an indicator: review the alert too. Do not assume the old server-side alert automatically inherited the new chart parameters.
If you want a better foundation before building indicator alerts, use our TradingView Technical Indicators guide.
Drawing Alerts for Trendlines, Levels and Channels
Drawing alerts are useful when your analysis starts with chart structure rather than an indicator. You decide which line, level, or drawing matters, and TradingView handles the monitoring.
This is a practical way to combine discretionary analysis with automation. You still make the human decision about which structure matters, but you no longer need to stare at the chart waiting for price to reach it.
| Drawing Workflow | Alert Use | Beginner Check |
|---|---|---|
| Horizontal level | Monitor support or resistance interaction | Can you explain why this level matters? |
| Trendline | Monitor a trendline interaction or break | Is the line based on meaningful structure? |
| Channel | Monitor entry, exit, inside or outside conditions | Does the channel still match current structure? |
| Other supported drawings | Build technical alert logic around the drawing | Is the drawing still relevant after the chart changes? |
Remember that drawing alerts use the technical-alert pool. If a simple fixed price alert can solve the same problem, using a price alert can preserve technical-alert capacity for more complex conditions.
Multi-Condition Alerts: Up to Five Conditions Without Code
Multi-condition alerts are one of the most useful alert upgrades for users who want confirmation logic without writing Pine Script. TradingView currently lets you combine up to five conditions in one alert.
For example, instead of creating a notification when price simply reaches resistance, you could require price to meet one condition while RSI, a moving average, or another supported condition also confirms the setup.
| Multi-Condition Rule | Current Behavior |
|---|---|
| Maximum conditions | Up to 5 |
| Plan availability | Plus and above |
| How it counts | One multi-condition setup counts as one technical alert |
| Symbols | All conditions must use the same symbol |
| Timeframes | Conditions can use different timeframes |
| Trigger logic | All configured conditions must be true together |
| Strategies / alert() scripts | Not supported in the multi-condition feature |
If the conditions use different timeframes, the alert frequency is based on the smallest timeframe used. That matters because the same logic can behave differently depending on how frequently the underlying conditions are recalculated.
Do not add conditions just to make an alert look sophisticated. Add a second or third condition only when it removes a specific kind of low-quality trigger you have already observed.
Watchlist Alerts: One Condition Across Multiple Symbols
Watchlist alerts solve a different problem. Instead of creating the same condition separately for every symbol, you can apply one alert across a watchlist.
Each symbol is monitored independently. If one symbol meets the condition, it can trigger without waiting for the rest. The watchlist alert continues until its lifecycle ends or the relevant conditions have been handled across the list.
TradingView also keeps the alert connected to the current watchlist membership. If you add a symbol after creating the alert, the condition starts applying to the new symbol. If you remove a symbol, the alert stops applying to that symbol.
Best Use
A focused list where the same monitoring condition makes sense for every symbol — for example a defined group of stocks, ETFs, or crypto pairs.
Biggest Risk
Applying one broad condition to a giant mixed watchlist and creating a flood of notifications that have no shared context.
For US stocks and ETFs, TradingView also provides an Extended session option for watchlist alerts so calculations can include regular, pre-market, and post-market sessions. Futures continue to follow their electronic trading hours.
Watchlist alerts are currently a higher-tier feature: Premium includes 2 active watchlist alerts and Ultimate 15. They do not support open-ended expiration.
Use our TradingView Watchlist Tutorial if you need to clean up the list itself before applying alerts to it.
Trigger Frequency and Alert Expiration
An alert condition can be correct and still feel wrong if the trigger frequency is poorly chosen. TradingView lets you control how often an eligible alert can fire, including options such as one-time triggering, repeated triggering, once per bar close, or once per minute depending on the alert type and configuration.
| Trigger Choice | Why You Might Use It | Main Risk |
|---|---|---|
| Only once | You only care about the first occurrence | You forget that the alert stops after triggering |
| Every time | You want repeated monitoring | Noisy conditions can produce too many triggers |
| Once per bar close | You want confirmation after the candle closes | You receive the notification later than an intrabar trigger |
| Once per minute | You need frequent monitoring where supported | Weak conditions can create unnecessary noise |
Expiration also matters. You can select an expiration date, and Premium and Ultimate currently support open-ended alerts for eligible regular alerts. Watchlist alerts do not support open-ended expiration.
Even open-ended alerts are not a reason to forget maintenance forever. TradingView can automatically deactivate very old alerts when they are more than a year old, have not triggered for over a year, and have not been edited for over a year.
Notifications and Alert Messages
A good alert is only useful if the message tells you what happened and the notification reaches you in the right place. TradingView supports several notification methods depending on the platform and alert configuration, including in-app notifications, toast notifications, email, sound, mobile push, plain text options, and webhooks.
Use alert names and messages that remain understandable days or weeks later. “BTC breakout review — 4H resistance” is more useful than “Alert 12.” If you open your phone during a busy day, the message should contain enough context that you know why you created it.
TradingView currently allows up to 300 characters in an alert name and up to 4,000 characters in the normal Message field. That is far more room than most users need. Clarity matters more than length.
If you regularly create structured alert messages, use our free TradingView Alert Message Builder to create cleaner text and webhook JSON.
TradingView Alert Presets
Alert presets can save time when you repeatedly create similar alerts. A preset can store much of the alert configuration so you do not need to rebuild the same notification behavior manually every time.
TradingView says presets can include condition-related settings, timeframe where applicable, trigger frequency, expiration behavior, custom name and message settings, and notification choices such as app notifications, toast, email, sound, and plain text.
Important: webhook URLs are not saved inside alert presets. Also, an existing preset cannot simply be edited in place; if you want a changed version, create a new preset.
Presets are most useful when the repeated structure is genuinely stable. Do not let convenience turn into blindly copying the same alert logic onto symbols or timeframes where it no longer makes sense.
TradingView Webhook Alerts: What Beginners Need to Know
A webhook lets TradingView send an HTTP POST request to an external URL when an alert triggers. This is useful for integrations, automation workflows, logging systems, bots, and external applications that need to receive alert data.
If the alert message is valid JSON, TradingView sends it with an application/json content type. Otherwise, the body is sent as plain text.
| Webhook Rule | Current TradingView Requirement |
|---|---|
| Account security | Two-factor authentication must be enabled |
| Ports | Only ports 80 and 443 are accepted when a port is specified |
| Server response time | Requests taking longer than 3 seconds can be cancelled |
| IPv6 | Currently not supported |
| Valid JSON message | Sent as application/json |
| Other message text | Sent as text/plain |
Security rule: never put passwords, exchange credentials, API secrets, private keys, or other sensitive credentials directly inside a webhook message.
TradingView also notes that webhook delivery can occasionally fail. You can inspect the Webhook status column in the alert log when troubleshooting delivery.
How to Manage TradingView Alerts Without Creating Noise
Creating an alert is easy. Maintaining a trustworthy alert system is the harder part.
TradingView’s Alerts Manager lets you browse, sort, stop, resume, edit, and delete alerts. Alerts also display statuses such as active, stopped after triggering, manually stopped, or expired.
| Management Habit | Why It Helps |
|---|---|
| Use clear names | You know immediately which setup fired. |
| Review active alerts weekly | Old levels and abandoned ideas do not pile up. |
| Pause instead of deleting when appropriate | You can preserve useful logic while temporarily stopping noise. |
| Check stopped-alert reasons | You can distinguish expiration, manual stops, and one-time triggers. |
| Keep messages consistent | Mobile and email notifications remain easy to understand. |
| Match alerts to watchlists | Your monitoring system stays connected to symbols you actually review. |
A Better TradingView Alert Workflow
A strong alert system begins before you open the alert dialog. It begins with a reason to monitor something.
| Step | Action | Goal |
|---|---|---|
| 1 | Start with a focused watchlist | Monitor symbols you can realistically review. |
| 2 | Mark meaningful chart levels or conditions | Give every alert a reason to exist. |
| 3 | Use price alerts where possible | Keep simple monitoring simple and preserve technical capacity. |
| 4 | Add technical alerts selectively | Monitor indicators or drawings only when the logic adds value. |
| 5 | Use multi-condition alerts for known false-trigger problems | Improve precision instead of adding complexity for its own sake. |
| 6 | Name and message alerts clearly | Understand every notification immediately. |
| 7 | Review the chart after the alert | Treat the alert as a review trigger, not a trade command. |
| 8 | Clean the system regularly | Prevent stale alerts from becoming background noise. |
This workflow works well with our TradingView Watchlist guide and TradingView Screener tutorial: use the screener to discover candidates, the watchlist to organize them, and alerts to tell you when something deserves a deeper chart review.
Common TradingView Alert Mistakes
Too Many Alerts
If every small movement generates a notification, you eventually stop respecting the alerts. More monitoring can produce less attention.
Vague Names
An alert called “breakout” is useless if you cannot remember which timeframe, level, or setup it referred to.
Changing an Indicator but Not the Alert
The old server-side alert may keep using the settings captured when it was created. Review alerts after changing indicator parameters.
Treating Alerts as Trade Signals
An alert tells you a condition was met. It does not automatically tell you whether the broader setup, risk, liquidity, news, and market context still support a trade.
Using Technical Alerts for Simple Price Levels
If a direct price alert can solve the same monitoring problem, using it may preserve technical-alert capacity for more complex logic.
Webhook Secrets in Messages
Do not place passwords, API secrets, private keys, or login credentials in webhook payloads.
Why Did My TradingView Alert Stop or Trigger Incorrectly?
When an alert behaves unexpectedly, start by checking the alert itself rather than assuming the chart is wrong.
| Problem | What to Check |
|---|---|
| Indicator alert does not match current chart settings | The alert may still be using parameters from when it was created. |
| Alert stopped after firing | Check whether the trigger was configured as Only once. |
| Alert expired | Check its expiration date and whether your plan supports open-ended alerts. |
| Webhook not delivered | Check Webhook status, endpoint response time, port, JSON format, 2FA, and external-server availability. |
| Too many rapid triggers | TradingView has fire-control limits and can stop alerts that trigger excessively. |
| Watchlist alert partly stops | A specific symbol can enter a limited-functionality state while other symbols continue working. |
| Unexpected timeframe behavior | Indicator, strategy, and drawing calculations can depend on the interval used by the alert. |
TradingView currently applies a fire-control rule to regular alerts of no more than 15 triggers in three minutes. Watchlist alerts have additional overall protection. If your condition is triggering that quickly, the condition itself may also be too noisy for a useful workflow.
Do You Actually Need More Alert Capacity?
If you are hitting real alert limits, compare the plans by the alert type you actually need. Essential is the first paid tier with separate price and technical capacity, Plus unlocks multi-condition alerts, and Premium adds watchlist alerts plus open-ended regular alerts.
New-user partner benefit: TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. TradingView controls eligibility, availability, and offer terms.
Conclusion: How to Use TradingView Alerts Well
The best TradingView alert system is not the one with the most notifications. It is the one that reliably tells you when a chart deserves your attention.
Start with simple price alerts. Move into technical alerts only when you understand the indicator, drawing, or strategy behind the condition. Use multi-condition alerts when they solve a known false-trigger problem. Use watchlist alerts only when one condition genuinely makes sense across the list. Keep names clear, messages useful, and old alerts cleaned up.
Most importantly, treat every alert as a review trigger, not as an automatic trading instruction. Market context can change between the moment you create an alert and the moment it finally fires.
For a wider workflow, continue with our TradingView Watchlist Tutorial, TradingView Screener guide, and Technical Indicators guide. If your main question is whether your plan has enough alert capacity, use our TradingView Plan Comparison.
FAQ: TradingView Alerts
How do TradingView alerts work?
You define a condition and TradingView monitors it on its servers. When the condition is met, TradingView can notify you through the notification methods configured for the alert.
What are the three types of TradingView alerts?
TradingView separates active alert resources into price alerts, technical alerts, and watchlist alerts. They have separate plan limits.
How many alerts does TradingView Free have?
The current Basic plan includes three active price alerts. Paid plans add separate technical-alert capacity and higher overall limits.
Can new TradingView users get a $15 discount through ChartWiseHub?
TradingView currently says eligible new users referred through its Partner Program receive a $15 discount coupon toward a new TradingView plan. Eligibility and coupon terms are controlled by TradingView and can change.
What is the difference between a price alert and a technical alert?
A price alert directly monitors a symbol with an eligible price operator. Alerts based on indicators, drawings, strategies, technical operators, chart patterns, or multiple conditions use the technical-alert pool.
Can TradingView alerts use multiple conditions?
Yes. Multi-condition alerts currently support up to five conditions on the same symbol and are available from the Plus plan upward. The full multi-condition alert counts as one technical alert.
Can multi-condition alerts use different timeframes?
Yes. Conditions can use different timeframes, but all conditions must use the same symbol. The trigger frequency is based on the smallest timeframe used.
What are TradingView watchlist alerts?
A watchlist alert applies one condition across multiple symbols in a TradingView watchlist. Each symbol is monitored independently, and changes to watchlist membership are reflected by the alert.
Which TradingView plans have watchlist alerts?
The current public plan comparison lists two active watchlist alerts on Premium and 15 on Ultimate.
Do TradingView alerts work when my computer is closed?
TradingView alerts are monitored server-side, so your chart does not need to remain open on your computer for an active alert to be monitored.
Why does my old indicator alert use the wrong settings?
TradingView saves the relevant indicator settings when the alert is created. If you later change the indicator parameters on the chart, the existing alert can continue using its older settings.
Which plans have open-ended TradingView alerts?
TradingView currently lists open-ended alerts for Premium and Ultimate. The open-ended option is not available for watchlist alerts.
Do TradingView webhooks require two-factor authentication?
Yes. TradingView requires two-factor authentication before webhook alerts can be used.
Can I send JSON with a TradingView webhook?
Yes. If your alert message is valid JSON, TradingView sends the webhook request with an application/json content type. Otherwise it uses text/plain.
Why did my TradingView alert stop after triggering?
Check the alert status and trigger frequency. An alert configured to trigger only once stops after its first trigger, while alerts can also stop because of expiration, manual changes, script errors, or excessive trigger frequency.
Are TradingView alerts trading signals?
No. An alert only tells you that the condition you configured has been met. You still need to review market context, risk, liquidity, news, and the rest of your trading process.
Related Articles
About ChartWiseHub
ChartWiseHub helps traders and investors learn TradingView step by step with clear tutorials, practical workflow guides, current plan comparisons, and free tools. Our goal is to make TradingView easier to understand and easier to use without adding unnecessary complexity.
Transparency & Risk
ChartWiseHub is reader-supported and this article contains affiliate links. Read our Affiliate Disclosure, Financial Disclaimer, and Editorial Standards.