Alert spam in TradingView almost always comes from three things: a trigger frequency that fires too often, duplicate alerts stacked on the same condition, and too many notification channels switched on at once. Fix those three and the noise drops fast. Below is the cleanup order we use, then the setup habits that keep it from coming back.
TL;DR
- Set the trigger frequency first. A condition that fires on every tick will flood you; fire once per bar close instead.
- Audit your alert list for duplicates, stale alerts and alerts on symbols you no longer trade. Delete or pause them.
- Pick channels per alert. Push for urgent, email for review, webhook for automation. Not all of them for everything.
- Build alerts on conditions that confirm on candle close, so a signal cannot appear and vanish mid-bar.
- Filter at the source: fewer, higher-quality signals beat a loud inbox.
Table of Contents
- Why TradingView alerts pile up
- Step 1: Set the trigger frequency correctly
- Step 2: Audit and clean your alert list
- Step 3: Choose notification channels per alert
- Step 4: Hide alert clutter on the chart
- Step 5: Put useful info in the message
- Step 6: Fix noise at the source, the signal itself
- Step 7: Send alerts somewhere you can filter
- Phantom or repeated notifications: a quick triage
- Our view on alert discipline
- Get fewer, cleaner alerts with Scalping-Algo
- A weekly alert routine
- FAQ
- Sources
Why TradingView alerts pile up
TradingView alerts are server-side. The condition is checked on TradingView's servers, so it can trigger without your browser being open, as this overview of TradingView alerts explains. That is great for coverage. It is also why spam builds quietly: alerts keep running long after you forgot you made them.
The usual causes:
- Frequency too loose. A price-cross alert set to fire every time the condition is true can ping repeatedly when price chops around a level.
- Duplicates. You created the same alert on two charts, two layouts or two timeframes and never noticed.
- Stale alerts. Old setups on symbols you no longer watch.
- Every channel on. Push, email, pop-up and sound all fire for each trigger, so one event feels like four.
- Noisy logic. The indicator itself flips signals on a forming bar, so alerts fire and then the signal disappears.
Work through them in that order. The first two take five minutes and remove most of the noise.
Step 1: Set the trigger frequency correctly
When you create or edit an alert, the dialog has a trigger option. It controls how often the same alert may fire. The options you will see are along the lines of only once, once per bar, once per bar close and once per minute. The exact labels can differ by alert type, so open the alert and read your own dialog.
How we think about each:
| Trigger style | Best for | Spam risk |
|---|---|---|
| Only once | One-off levels, breakout watch | Very low. Alert deactivates after firing |
| Once per bar | Levels you want to know about early | Medium. Can fire mid-bar on a wick |
| Once per bar close | Signals and indicator crosses | Low. One decision per candle |
| Once per minute / every time | Rare, specific automation | High on volatile pairs |
For scalping on 1m to 15m charts, once per bar close is the default we reach for. You get one notification per candle at most, and what you see is the confirmed state, not a half-formed one.
Match frequency to the job
- Level alert (a price you want to be told about once): only once. Recreate it when you want it again.
- Indicator cross or signal: once per bar close.
- Alert feeding a bot or Discord channel: once per bar close, plus a clear message so you can filter downstream.
If an alert is spamming right now, edit it and tighten the frequency before you do anything else.
Step 2: Audit and clean your alert list
Open the alerts panel and look at the full list. Most traders who complain of spam have 40 alerts and use six.
Sort through it with this checklist:
- Duplicates: same symbol, same condition, same timeframe. Keep one.
- Dead symbols: instruments you no longer trade. Delete.
- Old levels: price lines from last month's setup. Delete.
- Maybe later: alerts you want to keep but not right now. Pause (stop) them instead of deleting, then restart when you need them.
- Unnamed alerts: rename anything you cannot identify at a glance. A name like "BTC 5m long signal close" beats "Alert 14".
You can edit, pause, restart or remove an alert from the alerts panel. Pausing is the right move for anything seasonal, such as an alert tied to a session or event you only trade sometimes.
Make the audit a weekly habit. Two minutes on a Sunday keeps the list honest.
Check the alert log when something looks off
When a notification arrives that you do not recognize, check the alert log in the same panel. It shows which alert fired and when, so you can trace a surprise ping to a specific alert and fix or delete it. This is faster than guessing.
Step 3: Choose notification channels per alert
Each alert lets you choose where it goes. According to this guide to setting TradingView alerts, you can pick from channels such as mobile push, pop-up, email, sound and webhook when creating or editing an alert.
The mistake is leaving everything on. A simple routing plan:
| Alert type | Push | Pop-up / sound | Webhook | |
|---|---|---|---|---|
| Entry signal you act on | Yes | No | Yes (at desk) | Optional |
| Key level, early warning | Yes | No | No | No |
| End-of-day review item | No | Yes | No | No |
| Automation or logging | No | No | No | Yes |
Two rules keep it clean:
- One channel per urgency level. If you need to act in seconds, push or sound. If you can review later, email.
- Desk or phone, not both. If you are at your screen, the pop-up and sound are enough. A phone buzzing at the same time adds noise and no information.
If you route to a Discord channel through a webhook, you get a searchable history instead of a buzzing phone. Our guide to webhook trading alerts covers the setup, and the alert message syntax guide shows how to write messages that are easy to scan.
Step 4: Hide alert clutter on the chart
Sometimes the spam is visual. Alert lines and markers crowd the chart and make real levels hard to read. In the chart settings you can control whether alert lines and related markers are shown, and you can hide drawing and marker elements without deleting the underlying alerts. Hiding is cosmetic. The alert still runs, so if the problem is notifications, pause or delete instead.
A clean workflow: keep only the alerts for the symbols on your active layout visible, and keep older levels paused.
Step 5: Put useful info in the message
A vague message makes every alert feel like spam, because you have to open the chart to understand it. Write the message so a glance is enough:
- Symbol and timeframe
- Direction (long or short)
- Trigger price or level
- Which condition fired
TradingView supports placeholders in alert messages for things like the ticker and close price. Using them means one alert template can serve many symbols without you retyping. See the alert message syntax guide for copy-ready examples. If speed matters to you, our piece on cutting TradingView alert latency shows how to measure delay with a timestamp placeholder.
Step 6: Fix noise at the source, the signal itself
After cleanup, if you still get too many alerts, the logic is the problem. Three things drive it.
Repainting signals
An indicator that recalculates on the open bar can show a signal, fire an alert, then remove the signal when price moves. You end up with a notification for something that never existed on the closed chart. The fix is to use signals confirmed on candle close. This is how our indicators are built: signals are non-repainting and confirm on close, so an alert corresponds to a signal that stays on the chart.
No filter for chop
Most scalping spam happens in low-volatility ranges, where crosses fire back and forth. A volatility gate suppresses signals when the market is too quiet to trade. Fewer signals, better ones.
Single-condition triggers
One indicator crossing is a weak reason to interrupt yourself. Requiring two or three conditions to agree (confluence) cuts the count without hiding the setups that matter. For more on structure and levels as a filter, see our guide to support and resistance indicators.
Step 7: Send alerts somewhere you can filter
Phone notifications are the worst place to manage volume. A Discord or Telegram channel fed by webhook gives you history, search and mute controls. TradingView can post to a webhook URL, and your receiving service or bot formats and delivers the message. Webhook alerts require a paid TradingView plan, so check your plan before you build around them. Our copy-paste webhook examples show JSON message formats you can adapt.
Before you rely on any pipeline, test it. Our alert reliability checklist lists what to verify so a missed or duplicate message does not surprise you mid-trade.
Phantom or repeated notifications: a quick triage
If you get texts or pings that do not match anything current, work through this:
- Open the alerts panel and check the alert log for the matching time.
- Look for duplicate alerts across layouts.
- Confirm the alert's frequency is not set to fire repeatedly.
- Remove channels you no longer use, such as an old phone number or email.
- If it still happens, contact TradingView support with the alert name and timestamps from the log.
Notifications that seem delayed or out of sequence can come from carrier or app delivery, which is outside the alert itself. Push and email are usually the most dependable fallbacks.
Our view on alert discipline
We trade the short timeframes, so we see alert spam from both sides. The first time you set up ten alerts, it feels like coverage. By week two it feels like noise, and by week three you have muted everything and miss the one signal that mattered.
Our answer is to cut the alert count at the source. Every Scalping-Algo signal confirms on candle close, so you are never pinged for a signal that vanishes. Volatility gating keeps quiet-market chop out of your feed. Multi-indicator confluence means an alert represents several conditions agreeing, not one line crossing.
Then we route it properly. Native webhook alerts send signals to a Discord channel with sub-second delivery, so your phone stays quiet and your history stays searchable. Our scripts are open source, so you can see exactly what triggers an alert instead of guessing.
The goal is simple: fewer alerts, each one worth reading.
Tran
Get fewer, cleaner alerts with Scalping-Algo
If you want the noise handled at the signal level, our premium TradingView scalping indicators are built for 1m to 15m charts, with non-repainting signals, volatility gating, confluence and Discord webhook alerts. Plans are $79 per month, $799 per year, or $1,999 one-off for lifetime access. You can also browse Smart Scalping Signals to see the main signal tool, and our Trading Tricks & Tips page for setup shortcuts.
Prefer to read the terms first? Our refund policy is public.
A weekly alert routine
Keep it short and repeatable:
- Monday: delete expired level alerts; pause anything for sessions you will skip.
- Daily, before your session: confirm the alerts for your active symbols are on, with the right frequency and channels.
- After each session: check the log for anything that fired unexpectedly and fix its source.
- Monthly: rebuild any alert you have edited so often that you no longer remember its logic.
This takes minutes and prevents the slow build-up that turns a clean setup into a wall of pings.
FAQ
How do I stop TradingView alerts from repeating?
Edit the alert and change its trigger frequency to only once or once per bar close. Then check your alert list for a duplicate of the same condition on another chart or layout. Duplicates are the most common reason one event produces several pings.
How do I pause or delete a TradingView alert?
Open the alerts panel, find the alert, and use its menu to stop, restart, edit or delete it. Pause alerts you will need again, such as session-specific setups, and delete the ones you will not.
Can I hide alert lines on the chart without deleting the alert?
Yes. Alert lines and markers can be hidden through the chart's display settings. This only changes what you see. The alert keeps running and sending notifications until you pause or delete it.
Can I send TradingView alerts to Telegram or Discord?
Yes, through the webhook option. TradingView posts the alert message to a URL, and a bot or service forwards it to your channel. Webhooks need a paid TradingView plan. Our webhook guide walks through the flow.
Why did my alert fire for a signal that is no longer on the chart?
The indicator likely repaints, meaning it recalculates on the open bar. Use signals that confirm on candle close and set the alert to trigger once per bar close so the notification matches the closed chart.