What is Alligator?
Alligator belongs to the trend group in the cBot Factory Indicator Library. Its practical purpose is multi-average trend state. The Alligator uses three smoothed moving-average lines with different speeds. Their ordering and separation are used to describe whether price is compressed or developing directional structure. The value of the indicator in a cBot comes from making the interpretation explicit: which state matters, which event matters, and what other evidence must agree before an order is allowed.
The product context is straightforward: Alligator appears in the Trend section of the Indicator Library, carries the Premium label, and is intended as a multi-average trend state. Confirm expansion with volatility or volume rather than relying on line order alone. 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 Alligator works
A useful way to understand the calculation is to ask what information it compresses and what information it leaves out. Bullish line order and widening separation can support an upward trend state; bearish order and widening separation can support a downward state. Contracting lines suggest less directional separation. Whatever it omits must come from price structure, another indicator, risk controls or a rule that keeps the bot inactive. Automation is strongest when an indicator condition is deliberately narrow rather than overloaded with several interpretations.
Parameter choices alter the behavior of the signal, not just its appearance on a chart. Alligator packages several smoothed averages into a state model rather than treating one moving-average cross as the entire strategy. A more reactive configuration can create more opportunities and more false transitions, while a smoother configuration can filter noise and also miss early movement. The useful setting is the one whose behavior fits the rest of the cBot and remains reasonably stable across different samples.
How to interpret the signal in a cTrader strategy
The same Alligator reading can be used differently in different strategy styles. That is acceptable as long as the meaning is defined before testing. Trend-state classification, breakout preparation, multi-average direction filters and Bill Williams-style combinations are the most natural research directions here. Confirm expansion with volatility or volume rather than relying on line order alone. A good rule describes not only what must happen, but also whether the condition must persist for one or more completed candles before it counts.
Alligator settings in cBot Factory
The configurable Alligator 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.
Alligator editable parameters
| Parameter | Default | Available input / rule |
|---|---|---|
| Jaw period | 13 | Numeric input · min 2 · max 200 |
| Teeth period | 8 | Numeric input · min 2 · max 200 |
| Lips period | 5 | Numeric input · min 2 · max 200 |
| Rule | Bullish line order | Bullish line order · Bearish line order · Lines expanding · Lines contracting |
Numerical settings determine the indicator output; the Rule determines what the cBot does with that output. A durable state can remain valid long after it first appeared, while a transition can be missed if the strategy waits too long for confirmation. For Alligator, make entry persistence, re-entry and confirmation timing part of the written specification.
How to automate Alligator signals in a cTrader cBot
The safest automation pattern is to write the Alligator rule as a yes/no statement that can be tested on a completed bar. A cBot might require bullish Alligator line order plus expanding separation, then use Awesome Oscillator and tick volume as independent confirmation. From there, define whether the condition can open another position while one is already active, whether an opposite signal closes or reverses exposure, and whether confirmation candles are required. Those implementation details often change results more than a small parameter adjustment.
Best strategy styles
In the current cBot Factory catalog, Alligator is compatible with Trend following, Breakout, and Hybrid / custom. That list does not mean the same rule should be reused in every style. A breakout strategy may interpret strength as continuation, while a mean-reversion strategy may interpret extension as a setup that requires re-entry confirmation. The strategy thesis should decide the meaning before optimization begins.
The indicator is most defensible when used for trend-state classification, breakout preparation, multi-average direction filters and Bill Williams-style combinations. Those applications match its design more closely than an all-purpose signal rule. If a backtest improvement requires giving Alligator a new meaning after each losing period, the thesis is drifting. Keep the interpretation stable and let independent filters decide when the strategy is active.
Indicators that pair well with it
The library suggests ATR, Awesome Oscillator, and Tick Volume as complementary evidence for Alligator. Alligator packages several smoothed averages into a state model rather than treating one moving-average cross as the entire strategy. 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.
The library names ATR, Awesome Oscillator, and Tick Volume as common companions, but that is a menu of possibilities rather than a requirement to stack all three. Begin with the Alligator-only baseline, add one complementary condition, and compare the effect on expectancy, drawdown, stability and trade count. If the second indicator barely changes the quality of the sample, simplicity may be the stronger design choice.
How to backtest the cBot
For Alligator, the most informative test is often robustness rather than maximum historical profit. Verify that completed-bar timing, data source and symbol settings match the intended cTrader deployment. Test multiple date windows and inspect losing periods instead of optimizing them away. If the strategy only works after many thresholds, filters and exceptions are tuned together, simplify and retest. A smaller, understandable rule set is easier to diagnose when live behavior differs from the historical sample.
After the headline backtest, study the distribution of Alligator trades. Identify whether losses concentrate in ranges, volatility spikes, quiet sessions or one symbol. That analysis can support a simple regime rule, but the rule must then be tested on later data. Removing bad trades after seeing the answer is hindsight, not validation.
Common mistakes to avoid
The most common mistake is treating Alligator as a prediction engine. Three averages can still be three views of the same price history, so line order alone can overstate the amount of independent evidence. Another mistake is selecting a threshold only because it maximizes one backtest. Settings should have behavioral logic and should remain reasonably stable when the date range moves. Finally, avoid adding several correlated confirmations until almost every losing trade disappears; that is a classic path to overfitting and very low real-world trade frequency.
Risk management and practical limits
No Alligator 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: Alligator 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.
Alligator FAQ
Is Alligator a leading or lagging indicator?
It is primarily a lagging or confirming tool because it is calculated from historical price information. Some traders use changes in its state to react early to a possible transition, but the value still comes from data that has already printed. Treat it as measurable evidence rather than a forecast.
What is the best Alligator 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 Alligator be used by itself?
It can be coded as a stand-alone rule, but that does not make it a complete trading system. Confirm expansion with volatility or volume rather than relying on line order alone. A cBot still needs direction logic where applicable, entry timing, exits, position sizing, exposure limits and realistic validation.
Which indicators pair well with Alligator?
The cBot Factory library commonly pairs Alligator with ATR, Awesome Oscillator, and Tick Volume. 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 Alligator
Alligator can be valuable in a cTrader cBot when it has one clear responsibility and its settings are treated as testable assumptions. Start with the simplest rule that expresses the strategy thesis, combine it only with genuinely different evidence, and test the complete system across realistic market conditions. cBot Factory's role is to make those rules explicit enough to build and evaluate; the indicator itself cannot guarantee a profitable outcome.
Turn the indicator into an explicit rule you can test.
Add Alligator 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.