What is Average True Range?
The Average True Range indicator turns historical market data into a repeatable volatility reading. cBot Factory describes it as a volatility filter, and that description matters because it defines how the indicator should be used. ATR starts with true range, which captures the current high-low span and gap-like movement relative to the prior close, then smooths that range over the selected period. A cBot can evaluate that output consistently on every completed bar without changing the rule because of emotion or hindsight.
The product context is straightforward: Average True Range appears in the Volatility section of the Indicator Library, carries the Free label, and is intended as a volatility filter. Useful for volatility filters and adaptive stops; it does not show direction. Those facts should remain visible in the strategy design so the indicator is used for the job it was selected to perform rather than being reinterpreted after a backtest.
How Average True Range works
The output should be read in the context of how it is constructed, not as a colored buy/sell label. A higher ATR means price has been covering more distance per bar; a lower ATR means recent ranges are smaller. ATR does not indicate whether that movement is bullish or bearish. When the market changes regime, the same numerical event may carry a different meaning. That is why cBot Factory also exposes indicators from other evidence categories: direction, momentum, volatility and activity can be separated instead of forcing one indicator to do every job.
The chosen inputs control how quickly Average True Range responds to new data. ATR measures range rather than dispersion around an average. It is therefore different from Standard Deviation even though both describe volatility. This means optimization is really a test of signal behavior: frequency, lag, persistence and noise all move as settings change. Record those effects alongside profit and drawdown so the final parameter set has an explanation beyond being the best number in one historical window.
How to interpret the signal in a cTrader strategy
Interpretation becomes more reliable when the strategy separates context from trigger. Average True Range can provide either context or the event that opens the setup, but asking it to do both often creates circular logic. Volatility gates, adaptive stop distances, breakout filters and regime classification fit the indicator's design. Useful for volatility filters and adaptive stops; it does not show direction. The chosen interpretation should be tested across different volatility regimes and more than one isolated market sample.
Average True Range settings in cBot Factory
The configurable Average True Range inputs in cBot Factory are intentionally explicit. Each value changes either the lookback, sensitivity, threshold or interpretation of the indicator. The exact current parameters and defaults are listed below. Treat them as a reproducible specification for a test, not as an optimization target to maximize historical profit. If dozens of nearby combinations fail while one precise combination looks exceptional, the result may be fragile rather than insightful.
Average True Range editable parameters
| Parameter | Default | Available input / rule |
|---|---|---|
| Period | 14 | Numeric input · min 2 · max 200 |
| Minimum value | 0.001 | Numeric input · min 0 · max 10000 · step 0.0001 |
| Rule | ATR rising | ATR above value · ATR below value · ATR rising · ATR falling |
The interpretation selected in the Rule control changes the event model of the cBot. A condition such as 'is above' can qualify repeatedly, while a crossing or flip is naturally one-time until the next transition. For Average True Range, document whether repeated eligibility is intended and how confirmation candles interact with the original event so the backtest does not accidentally test a different strategy.
How to automate Average True Range signals in a cTrader cBot
A cTrader cBot needs an unambiguous entry condition. With Average True Range, that can be a persistent state, a transition event, or one layer of a multi-indicator gate. A cBot might require ATR to be rising before accepting a Donchian breakout, or use an ATR-based distance to scale a protective stop while direction comes from another indicator. The important part is the sequencing: decide which condition establishes the market regime, which condition triggers entry, and which independent rule prevents trades when the setup quality is poor. This prevents multiple indicators from repeating the same information while appearing to add confirmation.
Best strategy styles
cBot Factory associates Average True Range with Trend following, Mean reversion, Breakout, and Hybrid / custom. The category label is a starting point, not a promise of edge. Match the rule to the market behavior being targeted: trend systems need persistence, mean-reversion systems need evidence of a range or exhaustion, and breakout systems need a definition of expansion and follow-through. Hybrid systems should state which regime activates each branch.
A strong use case stays close to the indicator's native job. For Average True Range, that means volatility gates, adaptive stop distances, breakout filters and regime classification. The strategy can still be creative, but every interpretation should be written in advance. When one reading means continuation in one regime and reversal in another, the cBot needs a separate regime rule to decide which branch is allowed.
Indicators that pair well with it
The library suggests EMA, ADX, and MACD as complementary evidence for Average True Range. ATR measures range rather than dispersion around an average. It is therefore different from Standard Deviation even though both describe volatility. A strong combination assigns roles: one tool defines direction or regime, another confirms momentum or volatility, and a third may measure activity. Three indicators that all respond to the same moving-average behavior can create the illusion of confirmation without adding much independent information.
cBot Factory currently pairs Average True Range with EMA, ADX, and MACD. A clean research process adds only one of those at first, then measures what changed. Improvements should survive other periods and nearby settings; otherwise the apparent confirmation may be a sample-specific coincidence rather than a durable contribution.
How to backtest the cBot
Evaluate Average True Range as part of the whole strategy. The same signal may look excellent before costs but weak after realistic spread and commission, especially on lower timeframes. Check drawdown depth and duration, consecutive losses, exposure overlap and sensitivity to the chosen lookback. Use walk-forward or at least sequential out-of-sample testing where practical. The goal is to learn how the rule behaves, not to prove that the indicator predicts the market.
Trade-level review is essential for Average True Range. Sort outcomes by date, session, symbol and regime, then compare the signal behavior in the strongest and weakest periods. Look for a repeatable explanation rather than an exception for each loss. Any proposed filter should be written as a hypothesis and validated outside the sample that suggested it.
Common mistakes to avoid
Do not assume that a famous default setting is optimal. Absolute ATR values depend on symbol price scale and timeframe, so a threshold copied from another market can be meaningless. Defaults are convenient reference points, but the strategy must be tested on the actual symbol and timeframe. Also avoid confusing fewer trades with better evidence: an extra filter can raise historical win rate simply by removing sample size. Judge changes using return, drawdown, expectancy, stability and enough observations to support the conclusion.
Risk management and practical limits
No Average True Range setting removes trading risk. Position size, maximum concurrent exposure, stop logic, portfolio correlation and account-level drawdown limits belong outside the indicator signal. A technically valid setup can still lose because markets are uncertain and transaction costs are real. Treat indicator rules as entry or context logic and risk controls as a separate layer that limits what happens when the signal is wrong.
Risk note: Average True Range is based on historical market data and cannot guarantee future price direction or profitability. Backtests and demo results can differ materially from live trading because of spread, commission, slippage, liquidity, execution timing and changing market conditions.
Average True Range FAQ
Is Average True Range a leading or lagging indicator?
It is best described as a descriptive or confirming measure of realized volatility conditions. It can identify contraction or expansion that may matter for a strategy, but it does not know the direction or magnitude of the next move.
What is the best Average True Range setting for a cTrader cBot?
There is no universal best setting. Use the cBot Factory defaults as a reproducible starting point, then test nearby values on the intended symbol, timeframe and cost assumptions. Prefer settings that remain reasonably stable across different periods over a single narrow historical optimum.
Can Average True Range be used by itself?
It can be coded as a stand-alone rule, but that does not make it a complete trading system. Useful for volatility filters and adaptive stops; it does not show direction. A cBot still needs direction logic where applicable, entry timing, exits, position sizing, exposure limits and realistic validation.
Which indicators pair well with Average True Range?
The cBot Factory library commonly pairs Average True Range with EMA, ADX, and MACD. The useful pairing is the one that adds a different type of evidence rather than repeating the same calculation in another form.
Final takeaway on Average True Range
The practical advantage of Average True Range is repeatability. Once its rule, parameters, timing and supporting conditions are defined, a cBot can apply the same decision process without discretionary drift. The next step is not to search for a magical setting but to build the rule, backtest it responsibly, inspect its weaknesses and forward test before considering live execution. Automation improves consistency; it does not eliminate market uncertainty.
Turn the indicator into an explicit rule you can test.
Add Average True Range in cBot Factory, configure the current product parameters, combine it with complementary evidence where needed, and validate the complete cTrader strategy before forward or live execution.
Open StudioEditorial basis: this guide uses the current cBot Factory Indicator Library as the product specification. Technical indicator terminology is checked against the official cTrader Algo indicator reference where applicable. Educational content only; nothing on this page is financial advice or a guarantee of trading results.