How to Set Up TradingView Alerts (Without the False Pings)

Your phone buzzes. Gold just did something. You look, and by the time you have your chart open the move is gone, or worse, it never really happened because the candle reversed before it closed. That is what a badly built alert feels like: noise that trains you to ignore your own phone.

Done right, TradingView alerts are the opposite. They let you stop babysitting the screen and go live your life, while the platform watches your levels and your conditions for you. This is a practical walkthrough of how to set up TradingView alerts that fire when they should and stay quiet when they shouldn't. No fluff, just the settings that matter and the traps that catch people.

What a TradingView alert actually is

An alert is a rule that runs on TradingView's servers. When the rule is met, it notifies you through whatever channels you picked. The key word is servers: once an alert is set, it keeps watching even when your browser is closed and your laptop is asleep. You are not relying on a tab staying open.

There are two broad flavors, and knowing which one you want saves a lot of frustration.

• Price alerts. Simple. "Tell me when XAU/USD touches 2400." One value, one trigger.
• Condition alerts. Richer. "Tell me when the RSI crosses below 30," or "when this moving average crosses that one," or "when my indicator prints a signal." These are tied to something on your chart, not just a raw number.

Most of the interesting work lives in condition alerts, because a price level is dumb on its own. Price tags 2400 all day. A condition can encode why you care.

Setting up a price alert, step by step

Start with the easy one to learn the interface.

1. Open the chart for the symbol you want, say XAU/USD or BTC/USD.
2. Click the alert button in the right-hand toolbar (the clock-with-a-plus icon), or press the keyboard shortcut, or right-click the chart and choose "Add alert."
3. In the Condition row, pick your symbol and choose something like "Crossing" with your target price.
4. Set the Trigger (more on this below, it is the part people get wrong).
5. Choose your Expiration. Free plans cap how long an alert can live, so open-ended is not always available.
6. Pick your notifications: app push, email, popup, sound.
7. Write a clear message. "XAU 2400 tag" beats the default gibberish when six alerts fire in a week.
8. Click Create.

That is a working price alert. Now the part that separates a clean setup from a noisy one.

The trigger setting: bar close beats every tick

When you create an alert you choose how often the condition is checked. The two options that trip people up are Once Per Bar and Once Per Bar Close.

• Once Per Bar can fire the instant your condition becomes true, in the middle of a candle. Price spikes, the alert screams, and then the candle reverses and closes nowhere near your level. You just got faked out by a wick.
• Once Per Bar Close waits for the candle to finish before it checks the rule. If the condition still holds at the close, you get pinged. If the wick was noise, you hear nothing.

For almost any trend, crossover, or indicator-based alert, Once Per Bar Close is the sane default. It costs you a few minutes of lag, and in exchange it filters out a huge chunk of false signals. Intraday scalpers sometimes want the faster trigger on purpose, but if you are not one of them, close the bar first.

There is also Only Once, which fires a single time and then deactivates, and Once Per Minute, which you rarely need. When in doubt, bar close.

A quick note on repainting, because it connects here. If an indicator's signal can change after the candle closes, an alert built on it will lie to you. A non-repainting signal, checked on bar close, is about as honest as an alert gets. What you were pinged about is what actually happened.

Condition alerts on indicators

This is where alerts earn their keep. If you have an indicator on your chart that exposes alert conditions, you can point an alert straight at it. In the Condition dropdown, instead of the raw symbol, you select the indicator, and its available signals appear.

Good setups usually let you alert on discrete events: a long signal, a short signal, an exit, a stop being hit. That is far more useful than raw price, because the indicator has already done the thinking. You are being told "the setup you care about just occurred," not "a number was touched."

If you trade gold or Bitcoin specifically, alerting on a trend flip or a trailing-stop hit is worth more than a hundred price pings, because it maps to an actual decision. If you are still building out your gold workflow, our guide on how to trade gold on TradingView covers how to structure the chart before you ever add the alert.

Notification channels: where the ping goes

Creating the alert is half of it. The other half is making sure you actually receive it in a form you will notice.

For most people, app push is the workhorse. Install the mobile app, log in, enable notifications at the phone level, and your alerts follow you around. Email is a nice backup and a searchable record, but do not rely on it for anything you need to act on in the next thirty seconds.

A plain word on webhooks

A webhook is TradingView sending a little packet of data to a web address you specify when the alert fires. People use it to pipe alerts into other tools: a spreadsheet logger, a Discord channel, a third-party service. It is genuinely useful and completely optional. If you do not know what a webhook is, you do not need one yet. It does not make TradingView place trades by itself; it just hands the message to something else that might.

The mistakes that make alerts useless

Most people do not have an alert problem, they have a discipline problem dressed up as an alert problem. Here are the four that do the most damage.

1. Too many alerts. If everything is an alert, nothing is. Ten pings a day and you will mute the app inside a week. Alert on the two or three events that would actually change what you do.
2. Alerting on unclosed bars. Covered above, but it is the number one cause of "my alert is broken." It is not broken. It is firing on a wick. Switch to bar close.
3. No plan for when it fires. An alert is a question: now what? If you have not decided in advance what you will do when XAU tags your level, the ping just creates anxiety. Write the plan before you write the alert.
4. Vague messages. Future-you, half-awake at 3am, will not remember why you set "alert 1." Name it like a human. "BTC 4H trend flip short" tells you everything in one glance.

The reason bar close and a written plan matter so much is the same reason backtesting matters: you want your live behavior to match a rule you can trust. If you have never pressure-tested the logic behind your signals, our walkthrough on how to backtest a strategy on TradingView is worth a read before you wire it to an alert.

A sane default setup

If you want a template to copy, here is a boring, reliable one:

• Trigger: Once Per Bar Close
• Channels: App push on, email as backup
• Message: Symbol, timeframe, and what happened, in plain words
• Count: No more than a handful of active alerts at once
• Rule: Every alert maps to a decision you have already made

That setup will not spam you, will not fake you out on wicks, and will not leave you staring at a ping wondering what it means.

FAQ

What is the difference between Once Per Bar and Once Per Bar Close?

Once Per Bar can fire the moment your condition is true, mid-candle, even if price later reverses and the bar closes without meeting the condition. Once Per Bar Close waits until the candle finishes before checking, so you only get pinged on a confirmed signal. For most trend and crossover setups, bar close is the safer default.

Do TradingView alerts work on the free plan?

Yes. The free plan gives you a limited number of active alerts, but they work the same way as on paid tiers. You create them, pick a trigger, choose your notification channels, and they run server-side even when your browser is closed. If you want more simultaneous alerts, that is one of the main reasons people move to a paid plan.

Why does my alert fire multiple times?

Usually because you set it to trigger on every tick or every bar instead of bar close, or you left it on "Once Per Bar" when you meant "Only Once." Check the trigger setting first. Repeated pings almost always trace back to the alert firing on unconfirmed price rather than a closed candle.

Can TradingView alerts place trades for me?

Not on their own. An alert is a notification. It can send a push, an email, or a webhook payload to another service, and that external service could act on it. But TradingView itself is telling you something happened, it is not executing an order. Treat every alert as a prompt to make a decision, not as a trade.

Set fewer alerts, close the bar before you trust them, and decide what you will do before your phone ever buzzes. That is the whole game. The tool is only as sharp as the rule you hand it.