Execution & tools

TradingView

A charting and analysis platform with Pine Script indicators and strategies, alerts and supported broker integrations. Data coverage, delays and functionality depend on the feed and account configuration. A backtest uses a broker emulator rather than live fills; realistic costs and execution assumptions must be configured and checked.
Example. A strategy signal on a chart is not necessarily a live broker order. Record the data symbol, script version, bar interval, alert settings and actual broker fills separately when comparing a test with execution.

Data and execution are distinct

TradingView provides charts, scripts and integrations. Feed coverage, delays and available features depend on the symbol, data entitlements and account configuration. Do not assume that every FX feed requires a paid plan or that the chart quote is the broker’s executable quote.

Backtests need explicit assumptions

Configure commission, slippage and order assumptions in the broker emulator. Check lookahead, repainting and intrabar behaviour. Synthetic chart prices can produce unrealistic fills; test with appropriate standard market-price data.

Reference: TradingView: strategy testing and broker emulator. Checked 8 September 2026; verify later changes before relying on jurisdiction-specific rules.

Alerts need an execution path

For an automated workflow, verify the supported integration, authentication, duplicate handling and failure recovery. An alert firing is not proof that an order was accepted or filled. Confirm the current platform documentation before choosing a connection method.

FAQ

Does a paid TradingView plan include every real-time data feed?
No. Plan features and market-data entitlements are different. Certain exchanges or feeds require separate subscriptions, while availability and delays depend on the symbol and agreement.
Is a profitable TradingView backtest enough to start live trading?
No. Check information available at each decision, execution assumptions, costs and out-of-sample results. The broker emulator is a model; a simulated result does not establish that live orders would have filled identically.
What is repainting?
Historical signals can differ from those observed in real time, for example because a bar was unfinished, higher-timeframe data changed or the script used unavailable future information. Waiting for bar close may address some cases, but does not fix every source of misleading historical results.
Why can results differ from my broker’s platform?
Data feeds, quote sides, costs, slippage, financing, volume rounding and timing can differ. Compare the assumptions and actual fills; there is no universal size of the discrepancy or single cause.

← Back to the full glossary

Jarosław Wasiński

Editor-in-chief, ForexMechanics.com • Macro & FX analyst

Independent analyst and practitioner with over 20 years of experience in financial markets. Actively involved in Forex since 2007, with a focus on fundamental analysis, OTC market structure, and disciplined capital risk management.

  • Creator and editor-in-chief of MyBank.pl, providing reliable financial education since 2004.
  • Author of hundreds of in-depth market commentaries, structural analyses, and educational materials for traders and investors.
  • Advocate for market transparency, promoting education grounded in hard data and institutional reports (BIS, ESMA, CFTC).

All content is educational and informational only – it does not constitute investment advice or a recommendation. Remember: leveraged trading (Forex/CFD) carries a high risk of rapid capital loss.