TradingView Alerts: Types, Triggers and Reliable Setup Guide

TradingView alerts are the part of the platform that watches the market for you and tells you, or another system, when a condition is met. They are simple to create and surprisingly easy to get subtly wrong: an alert that expires unnoticed, fires on the wrong bar, or runs on an old copy of a script behaves differently from what you pictured. This guide is about creating TradingView alerts that behave the way you expect, whether you only want a phone notification or an alert that feeds automation.

It deliberately does not repeat the webhook concept. For that, read Automating TradingView Alerts with Webhooks. For the message text itself, see TradingView alert JSON message examples. Here we focus on the alert: what kinds exist, what the conditions mean, when it triggers, and how long it lives.

The kinds of alerts

TradingView's help center page "About TradingView alerts" (read 11 October 2026) groups alerts into three categories:

• Price alerts: trigger when a symbol's price reaches or crosses a level you set.
• Technical alerts: trigger on indicator values, custom conditions or chart patterns.
• Watchlist alerts: apply one condition to several symbols in a list, each evaluated independently.

On top of those categories, the alert's source can be a drawing, an indicator, a Pine Script strategy or a script that calls the `alert()` function. The source matters more than the category once automation is involved, which is why the next sections separate indicator alerts from strategy alerts.

Conditions: what the alert is watching

The setup dialog starts with the condition. According to TradingView's "How to set up alerts" page, the main parts are the trigger condition, which determines when the alert appears, the frequency, an optional timer or expiration, a name, and a message with placeholders. Typical conditions include a price crossing a value, an indicator crossing its signal line, or a drawing being touched.

A few habits help here:

• Pick the symbol and timeframe first, then the condition. An alert is tied to the chart it was created on.
• Use a specific, testable condition rather than one that relies on your reading of the chart.
• Name the alert so that you will recognize it in a list six weeks from now.

Trigger frequency

Frequency decides how many times one condition can produce notifications. TradingView's setup page describes it as whether an alert is triggered only once or multiple times. The dialog offers choices such as only once, once per bar, once per bar close and, for some conditions, once per minute; the exact list depends on the condition, so read the options shown in your dialog rather than relying on memory. The difference between the "per bar" options and "per bar close" is the heart of most surprises.

For scripts that call `alert()`, TradingView's Pine Script documentation (read 11 October 2026) defines three frequencies in code:

Why bar close matters

An alert that evaluates while the bar is still forming can fire on a condition that disappears before the bar closes. Your backtest or your eye usually judges closed bars. If you want the alert to agree with what you see on a closed chart, a once-per-bar-close style option is the closer match. If you want speed and accept that the condition may flicker, intrabar is the choice. Neither is better in general; the point is to choose on purpose and to test.

Indicator alerts versus strategy alerts

This is where reliability questions concentrate.

Indicator or condition alerts

You create them on an indicator or a custom condition. They fire when the indicator's own logic says so. In Pine, `alertcondition()` is available in indicators only and takes constant message strings; `alert()` works in both indicators and strategies and can build dynamic messages. For scripts with `alert()`, the dialog lets you pick "alert() function calls only" so the script's own messages are used.

Strategy alerts

TradingView's strategy alerts page (read 11 October 2026) explains the facts that surprise people most:

• When you create the alert, TradingView deploys an independent copy of the strategy on its servers. Changes to the strategy on your chart have no effect on that copy. To apply modified settings you must delete and recreate the alert.
• Notifications are sent only for real-time order executions, not for orders on historical bars. A strategy that shows plenty of historical trades on your chart will send nothing for them.
• Alerts stop triggering if they send more than 15 notifications within 3 minutes.
• Placeholders such as `{{strategy.order.action}}`, `{{strategy.order.price}}`, `{{strategy.market_position}}` and `{{strategy.position_size}}` fill the message with order details.

For scripts, the alert can trigger on order fills only, on `alert()` calls only, or on both. Choosing "both" is the usual cause of duplicate messages: a fill and an `alert()` call at the same moment each send one.

Expiration: the silent failure

According to the "About TradingView alerts" page, standard alerts expire after a maximum of two months, while Premium and Ultimate plans can keep alerts active indefinitely. The same page lists an additional rule: an alert is switched off if it was created more than a year ago, has not triggered for over a year and has not been edited for over a year.

The practical consequence: an alert that stops sending because it expired does not shout about it. If your workflow depends on an alert, put its expiry date in a calendar or a checklist, and re-create or extend it before then. It also applies to alerts that feed automation, where a quiet alert can look just like a market with no signals. See TradingView alert not firing for a checklist when it happens.

Notification channels

TradingView lists several ways an alert can reach you: a notification on the mobile app, a pop-up on the chart, an email, a webhook URL, a sound, and a plain-text message. Some practical points:

• Pop-ups and sounds only work while the browser tab or desktop app is open.
• The mobile app is the most reliable personal channel for discretionary alerts, but turn on notifications in your phone's settings as well.
• A webhook is the channel for software to react. It has its own conditions: two-factor authentication on the account, ports 80 and 443 only, and a three-second timeout, as covered in the webhook security guide.
• You can use several channels at once. Many people keep the mobile notification on for any automated alert, so that a human sees when something fires.

Practical alert hygiene

A short routine keeps a growing alert list from becoming a liability:

1. Name consistently: strategy or setup, instrument, timeframe, action.
2. One purpose per alert: avoid duplicating the same condition in two alerts.
3. Record expiries: a calendar entry a week before.
4. Delete what you stopped using: old alerts are the ones that surprise you.
5. Recreate after changing a strategy: because a running strategy alert uses a copy.
6. Read the log: TradingView's alert log shows what fired and what the webhook delivery status was.
7. Test with a harmless target first: a notification only, or a simulated account.

A creation checklist

1. Open the chart with the symbol and timeframe you intend to use.
2. Confirm the script version on the chart is the one you want to run.
3. Open the alert dialog and set the condition.
4. Choose the frequency deliberately and write down why.
5. Set the expiration or timer.
6. Select notification channels; add the webhook only when the receiving side is ready.
7. Write the message, using valid JSON if software will read it.
8. Save, trigger it safely, and read the log.

Alerts that feed automation

When the destination is an automation platform, add a few more checks. Make sure the message is valid JSON and includes what the receiver needs (WeCore reads a ticker and an action at minimum). Use the continuous ticker form such as `MNQ1!` if the receiver resolves it to the front month, so that you do not edit alerts at each roll. Test in Simulation, where WeCore starts every new broker account, and only move on after you have saved risk rules. Remember that WeCore is a bridge and not a broker, that it does not give advice, and that your prop firm's automation rules apply to you. The overview in prop firms that allow automation lists what several firms state on their own pages.

For the full wiring of alerts to a broker, see how to connect TradingView alerts to WeCore. If you would rather use ready-made logic, WeAlgo strategies run on your own trading server. When you are ready, you can create an account and compare the plans; the trial lasts 7 days and starts with a $5 (refunded immediately) card verification.

FAQ

How long does a TradingView alert last?

On standard plans an alert can last at most two months before it expires, according to TradingView. Premium and Ultimate plans allow alerts that stay active indefinitely.

What is the difference between once per bar and once per bar close?

Once per bar fires on the first occurrence while the bar is forming, while once per bar close waits until the bar finishes. The first is faster but may fire on a condition that later disappears.

Why did my strategy alert ignore my latest changes?

Because TradingView runs a copy of the strategy on its servers. Edits on your chart do not reach that copy, so delete the alert and create it again.

Why does my strategy send no alerts for past trades?

Strategy alerts are only sent for real-time orders. Orders on historical bars, which you see in the strategy tester, do not generate notifications.

Can I use several notification channels at once?

Yes. You can combine a mobile notification, email, pop-up, sound and webhook on the same alert. Keeping at least one human-readable channel on an automated alert makes problems easier to notice.

This article is general information, not investment advice. It makes no promise of results, and futures trading carries a high risk of loss. Check your broker's and prop firm's current rules before automating.