A TradingView strategy can fire alerts on order fills in the Pine tester. That is not the same as MT5 executing. To run TradingView strategy alerts on an MT5 EA, you forward each alert to software that places the live order. TradingView Bridge does that locally: no cloud relay, no webhook URL.
Strategy alert vs indicator alert
- Indicator: you write the alert condition (crossover, level, “once per bar”).
- Strategy: you enable strategy alerts so Pine’s
strategy.entry/ exit can emit a message when the backtest/engine would trade.
Either way, the message that arrives in the bridge is just text. The EA does not “understand Pine.” It understands buy/sell/close plus optional lots, SL, TP.
Recommended message
In the strategy’s alert message, send something explicit — do not rely on a screenshot of the chart:
buy,{{ticker}},vol_lots=0.01,sl_pips=30,tp_pips=60
Or a sentence: Buy {{ticker}} 0.01 lots, 30 pips SL, 60 pips TP.
Match your strategy: if Pine uses percent of equity, put the same idea in risk_pct and a stop, or size lots in the EA panel and keep the alert as buy,{{ticker}} only.
Two sizers at once (Pine lots + EA lots + alert lots) is how people double size.
No cloud relay
Webhook bridges send that string to someone else’s server, then to MT5. Here the string stays on the Windows PC: TradingView window → local queue → TradingView Trade Automation on MT5. Official description: source.html.
Practical limits
- TradingView strategy alerts still need the alert to be created and the bridge online. They are not a hosted VPS inside TradingView.
- Repainting indicators will fire garbage live, same as any bridge.
- MT5 market execution, spread, and session filters can skip a signal the Pine tester assumed was fillable.
- One strategy, many symbols: map each ticker, or send the broker symbol in the message.
Message cookbook: plain English / compact alerts. Install steps: connect TradingView to MT5.