TradingView Alert to MT5 is a game-changer for traders. Every trader who uses automated trading asks the same question at some point: "What actually happens between the moment TradingView fires an alert and the moment the trade appears in MT5?" This deep-dive article walks through the entire TradingView alert to MT5 execution path — with real timing data and a step-by-step breakdown of every component.
⚡ The short answer: With TradingView Copier Pro, the total time from TradingView alert to MT5 order fill is typically 15–50 milliseconds — faster than a human can blink.
Phase 0: The Alert Condition (TradingView)
Before any webhook is sent, TradingView has to detect that your alert condition is true. TradingView re-evaluates indicator and strategy conditions on every new tick or bar close, depending on your alert's settings. As soon as the condition evaluates to true, TradingView queues a webhook send.
Important: TradingView's alert evaluation happens on TradingView's servers, not your PC. This means alerts fire even when your browser is closed — which is why webhooks are so powerful for overnight and 24/7 trading.
The Full Execution Timeline
Alert Condition Evaluates True
TradingView's alert engine detects your condition (price crosses level, indicator fires, strategy entry, etc.)
TradingView Prepares Webhook POST
TradingView substitutes any {{placeholders}} in your message with real values and prepares the HTTP POST request
POST Travels to Your Cloudflare URL
The request travels from TradingView's servers through the internet to your Cloudflare tunnel endpoint, then to your PC
TradingView Copier Pro Parses the JSON
The local Express server receives the POST, validates the JSON structure, and extracts action, symbol, lot, SL, TP
Command Forwarded to MT5 EA
The parsed command is sent via local TCP socket to the TV_Copier Expert Advisor running in MT5
MT5 OrderSend() Called
The EA calls MT5's native OrderSend() function. The order travels from your PC to your broker's server and is filled.
What Affects Execution Speed?
Not all alerts execute in the same time. The main variables are:
- Your internet connection speed: A faster ISP reduces the network transit phase (Step 3)
- Time of day: During peak market hours (London/NY open), slight delays may occur as TradingView processes more alerts simultaneously
- Broker server location: Your MT5 broker's servers are geographically located somewhere — a broker in Europe will fill faster if you're in Europe
- VPS vs home PC: A VPS in a data center typically has lower ping to both Cloudflare and the broker server
Types of TradingView Alerts and How They Behave
Price Level Alerts
Fires when price touches or crosses a horizontal level. Triggers once, then can be set to auto-reset. Great for breakout trading. Webhook fires immediately when the condition is met on the next tick.
Indicator Alerts
Fires when an indicator value crosses a condition (e.g. RSI below 30). May fire multiple times per bar if the indicator oscillates around the threshold. Use "Once per bar close" to prevent this.
Strategy Alerts
Pine Script strategy() objects fire alerts when strategy.entry() or strategy.exit() is called. Set to "Order fills only" for cleanest signal. The {{strategy.order.alert_message}} placeholder forwards your custom message from the Pine Script alert() call.
Setting Up Your TradingView Alert for MT5
For the most reliable alert-to-MT5 flow:
- Set alert frequency to "Once per bar close" (for indicators) or "Order fills only" (for strategies)
- Enable Webhook URL in Notifications tab
- Paste your TradingView Copier Pro webhook URL
- Set the message to valid JSON:
{"action":"BUY","symbol":"EURUSD","lot":0.1} - Optionally set an expiry date if you don't want the alert running forever
Set Up Your TradingView Alert to MT5 Pipeline
TradingView Copier Pro handles everything from webhook reception to MT5 execution. Sub-50ms, every time.
Get TradingView Copier Pro →Common Alert-to-MT5 Issues
- Alert fires but no trade: Check the App's Logs tab — if the webhook was received, the issue is with the EA. If not received, the tunnel may be down.
- Alert fires too many times: Change frequency to "Once per bar close"
- TradingView says "Webhook error 400": Your JSON may be malformed — validate it at jsonlint.com
- TradingView says "Webhook error 52x": The URL is unreachable — restart the app and ensure the tunnel is connected