Imbalance Fibonacci EA: Automated MT5 trading with verified trend-following performance

This Imbalance Fibonacci EA review for 2026 presents an objective performance analysis of a trend-following Expert Advisor built for MT5. The EA automates signals derived from the popular indicator [IMBA] Lance Algo on TradingView, and its core value is translating those signals into executable trades while enabling robust backtesting and parameter optimization. Imbalance Fibonacci EA is priced at $249 and developed by Daniel Johannes Kiefer, who published the EA with clear documentation on setup and signal mapping. What makes Imbalance Fibonacci EA unique is its focus on imbalance-based trend entries combined with Fibonacci-based confluence filters and time-of-day constraints. The algorithm waits for confirmed directional momentum before opening positions, uses dynamic stop placement based on recent structure, and applies configurable take profit ladders. Because it is explicitly trend-following, Imbalance Fibonacci EA is not suited for prolonged sideways markets and performs best on trending pairs and indices where momentum persists for multiple bars. Risk management is handled through per-trade risk percentages, maximum concurrent trades, and optional breakeven or partial close rules. The EA supports walk-forward optimization in MT5 and trade logging for post-trade analysis. Expected performance characteristics include moderate to high win-rate variability depending on timeframe and broker, occasional larger drawdowns during trend reversals, and a preference for 1-hour and 4-hour timeframes for stable signals. Users should test on demo accounts and apply conservative sizing before live deployment.

Performance expectations for Imbalance Fibonacci EA vary by broker, timeframe, and risk setting. Live signal snapshots show moderate risk performance on Tickmill with 2.6% signal returns and higher risk snapshots on Robo-Forex up to 9.8%, illustrating how leverage and execution affect results. Typical win rates can range from 45% to 65% depending on timeframe and market regime, with profitable months driven by extended trends. Drawdown management relies on per-trade stop placement and maximum equity risk settings; realistic peak drawdowns of 10% to 30% are possible in aggressive modes. Trade frequency is moderate, averaging several trades per week on H1 and H4 charts, and lower frequency on daily charts. Account requirements start at standard mini-account sizes for low-risk modes but recommend at least $1,000 to $5,000 depending on leverage and the chosen risk profile. Backtests should be run with tick data in MT5 to mirror live spreads and slippage for accurate performance reading.

Imbalance Fibonacci EA operates across a spectrum from moderate to aggressive risk depending on configuration and broker execution. The default approach emphasizes per-trade stop loss placement derived from recent structural levels rather than fixed pip stops, which helps align risk with market volatility. Position sizing should be percentage-based, for example risking 0.5% to 2% of equity per trade, and scaled up gradually after consistent demo or small-live results. Vulnerabilities include false breakouts during ranging markets and slippage during major news events, which can increase realized drawdown. Recommended account size depends on chosen risk; conservative settings can run on $1,000 accounts, while full-featured or high-risk modes are better suited to $5,000 or larger to withstand expected volatility. Consider broker execution quality and latency when deploying the EA.

Install Imbalance Fibonacci EA by copying the EA file into the Experts folder of your MT5 installation and restarting the terminal. Open the Navigator pane, attach Imbalance Fibonacci EA to an H1 or H4 chart, and enable automated trading. Key parameters to configure include risk percent per trade, maximum concurrent trades, stop loss multiplier, and take profit ladder settings. Recommended brokers are those with low spreads and reliable execution, such as ECN-style or institutional demo accounts. Start with H1 or H4 timeframes for balance between signals and noise, and run extensive backtests using real tick data followed by forward testing on a demo account before going live.