UT Bot Alerts: Settings, ATR Logic, and TradingView Test Guide
UT Bot Alerts is a TradingView indicator that marks changes around an ATR-based trailing level. Its settings control signal behavior; they do not supply a universal win rate. This guide identifies the original publication, explains how to evaluate sensitivity, and separates a chart signal from an executable trading strategy.
Start with an Identifiable Script
The UT Bot Alerts publication by QuantNomad is an open-source indicator. Its description credits Yo_adriiiiaan for the earlier indicator and HPotter for the original idea. The publication identifies this version as Pine v4 alerts for an earlier strategy.
Save the publication URL and author with your test. Similar names, later editions, and ports can change the price source, smoothing, initialization, or exit rules. Results from one version do not establish the behavior of another. The original publication is free to use; TradingView account features and third-party variants have separate availability conditions.
How the ATR Trailing Logic Works
QuantNomad's Python implementation of the UT Bot strategy provides a readable reference for the core recurrence. The offset is the ATR multiplied by a sensitivity factor. While current and previous prices stay above the previous stop, the next stop is the greater of the old stop and price minus the offset. On the lower side it uses the lesser of the old stop and price plus the offset. A side change resets the level. Signals use crossings of price and that level.
In compact notation:
Offset = sensitivity multiplier × ATR(period)
This is a stateful calculation: the previous stop influences the next one. A fixed band drawn at today's price plus or minus ATR is not the same calculation. Compare initialization and early observations when checking a port against the original.
For any version that describes an EMA as confirmation, inspect its length. A one-period EMA equals its source, so it cannot supply an independent smoothed trend filter. A code label alone is not evidence of extra confirmation.
The plotted trailing level also does not submit a protective broker order. An indicator needs separately defined execution and risk rules before its labels can be evaluated as trades.
What Key Value and ATR Period Change
| Input or choice | Mechanical effect | What to measure |
|---|---|---|
| Larger sensitivity multiplier | Increases the ATR offset for the same ATR value | Reversal timing, turnover, and loss size |
| Smaller sensitivity multiplier | Reduces that offset | More frequent crossings in the selected sample, if they occur |
| ATR period | Changes how the volatility estimate responds to observations | Signal stability across quiet and active intervals |
| Price source | Changes the series compared with the stop | Whether signals use actual or synthetic prices |
| Timeframe | Changes the bars used for the calculation | Holding time, event count, and execution costs |
These mechanisms do not imply a monotonic improvement in profit. A wider offset may avoid some reversals but delay others. A longer ATR period can smooth the estimate without guaranteeing fewer signals on every dataset.
Test Settings Instead of Copying a Best-Settings Table
Record the defaults of the exact publication you added. Keep one baseline and a small, predeclared set of alternatives. For example, one experiment can vary only the multiplier around that baseline while holding the ATR period and all order rules constant. A separate experiment can vary the ATR period. These are experimental comparisons, not recommended values.
For a 5-minute test, costs per completed trade and signal-to-fill delay deserve explicit measurement. For a 4-hour test, record overnight exposure and gap behavior. A daily crypto test needs an exchange and candle-boundary convention. None of those use cases justifies transferring a setting or win rate from an unrelated chart.
Configure TradingView Alerts
- Open a standard candle chart and add the publication by its verified author.
- Record the instrument, timeframe, input settings, and selected price source.
- Create an alert using the indicator's relevant buy or sell condition. For a rule evaluated at completed bars, select the bar-close frequency where available.
- Save the alert's condition and frequency beside the test settings. Record notification timestamps during live observation.
- Recreate the alert after changing its relevant inputs or chart context.
TradingView's alerts documentation explains that running alerts use a saved snapshot of the script, inputs, and chart context. Editing the chart does not update that existing snapshot. Notifications also do not prove that a brokerage order was submitted or filled.
Repainting: What a Close-Based Alert Does and Does Not Fix
An open candle can cross a level and move back before closing. A bar-close alert aligns notifications with a completed-bar rule, but it does not prove that every version has stable historical signals.
TradingView's repainting documentation distinguishes unconfirmed values from other causes, such as future information leaking into historical calculations. A confirmation check does not correct every data-request or historical-plotting issue. Inspect the exact source and compare a saved real-time signal log with the chart after reload.
Heikin Ashi adds another distinction: its OHLC values are synthetic. TradingView's non-standard chart documentation explains why these prices should not be treated as ordinary market execution prices. If using a synthetic source to generate signals, evaluate fills on real tradable prices and document both series.
Turn Signals into a Testable Strategy
An alert indicator has no single inherent win rate. Define what happens after a signal before counting wins:
| Decision | Example test specification |
|---|---|
| Direction | Long-only; a sell signal exits the long |
| Entry observation | Confirmed buy signal |
| Fill assumption | Next available standard-bar open |
| Exit observation | Confirmed sell signal |
| Open position at end | Report separately or close under a declared terminal rule |
| Costs | Charge each side and model spread/slippage without double counting |
| Risk limits | State whether any separate stop, time exit, or exposure limit is implemented |
This table is a candidate research specification, not a result or a live-use recommendation. If adding a stop and target, define what happens when both are touched within one candle. If allowing shorting, specify borrowing or funding treatment and reversal sizing.
Keep a trade ledger with signal time, order time, fill price, quantity, exit reason, and all costs. Compare net expectancy, drawdown, turnover, market exposure, and trade count. Save the selected settings before running a later holdout interval; do not re-label a tuned interval as out-of-sample evidence.
Evaluate LinReg, RSI, or Other Filters Separately
Adding Linear Regression Candles, RSI, or a trend filter changes the strategy. Test the baseline and filtered version over the same dates with the same fills and costs. Record excluded signals as well as retained ones. A filter that raises the win rate may reduce net return or retain too few trades to support a conclusion.
Several indicators can transform the same price history. Their agreement is not automatically independent evidence. Each additional setting also expands the number of possible variants, making it easier to select an attractive historical result by chance.
Check Platform Ports Before Reusing Results
An MT4, MT5, or thinkorswim port needs its own review. Compare ATR smoothing, initial stop values, price source, session boundaries, and signal timing. Then match signals bar by bar on equivalent input data. A shared indicator name or similar screenshot does not establish equivalence.
Frequently Asked Questions
What are the best UT Bot Alerts settings?
No universal best settings are established here. Start by recording the defaults of a specific publication, then compare a predeclared set of alternatives with unchanged execution rules and later holdout data.
How accurate is UT Bot Alerts?
This article provides no verified win rate. Accuracy requires a definition of a completed trade, the full sample, execution prices, costs, and unchanged settings. Buy and sell labels alone do not provide those records.
Does bar-close alerting eliminate repainting?
It avoids sending an alert for a condition that disappears before that bar closes. It does not establish that all data sources or historical calculations in a particular script version are free of repainting.
Is UT Bot Alerts the same as Supertrend?
Both can use ATR-based trailing levels, but that shared component does not make the algorithms identical. Compare their source price, band updates, state transitions, and signal conditions before substituting one for the other.
Does a buy alert place a live order?
A chart alert is a notification. Any order-routing integration needs separate configuration and verification, including duplicate handling, rejected orders, and a record of actual fills.