Why does my backtest entry price differ from my live cTrader entry?
Backtests use TradingView's broker emulator and historical bar data; live cTrader orders encounter real bid/ask prices, spread, latency, slippage, market hours and broker execution. Exact price equality should not be assumed.
What this means in practice
Backtests use TradingView's broker emulator and historical bar data; live cTrader orders encounter real bid/ask prices, spread, latency, slippage, market hours and broker execution. Exact price equality should not be assumed. This page is specifically about “Why does my backtest entry price differ from my live cTrader entry?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.
Real-world scenarios
Scenario A — Market order after alert delay
Inspect the mechanism named by “Scenario A — Market order after alert delay” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario A — Market order after alert delay on question 60, use that evidence specifically to answer “Why does my backtest entry price differ from my live cTrader entry?”; keep it separate from the evidence for the other scenarios on this page.
Scenario B — Spread widens
Measure executable bid/ask spread at the entry decision. If the configured limit is exceeded, record a deliberate rejection; waiting until spread normalizes creates a different trade. For Scenario B — Spread widens on question 60, use that evidence specifically to answer “Why does my backtest entry price differ from my live cTrader entry?”; keep it separate from the evidence for the other scenarios on this page.
Scenario C — Backtest uses OHLC assumption
Inspect the mechanism named by “Scenario C — Backtest uses OHLC assumption” directly. Record its input, the state immediately before it and the first observable output that differs from the intended result. For Scenario C — Backtest uses OHLC assumption on question 60, use that evidence specifically to answer “Why does my backtest entry price differ from my live cTrader entry?”; keep it separate from the evidence for the other scenarios on this page.
What to check
- target connector/account identity
- exact broker symbol
- normalized order parameters
- cTrader response and final position/order state
Practical rule
For “Why does my backtest entry price differ from my live cTrader entry?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.
Decision summary
Direct answer: Backtests use TradingView's broker emulator and historical bar data; live cTrader orders encounter real bid/ask prices, spread, latency, slippage, market hours and broker execution. Exact price equality should not be assumed.
Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.
Primary sources
Need a TradingView → cTrader execution route?
NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.