How a MetaTrader Bridge Works
The route has three records worth keeping: the alert sent by TradingView, the bridge's handling of that alert, and the terminal's trading result. An Expert Advisor can receive an instruction correctly while the broker rejects the requested volume or stop. Investigate the terminal result before changing the alert condition.
For an EA-based connection, the terminal is part of execution infrastructure. It needs an active connection to the correct broker server, a trading-enabled account and the required EA permissions. Closing the chart browser does not shut down a server-side TradingView alert; shutting down the machine that runs the EA interrupts that part of the route.
MT4 and MT5 Support Must Be Checked Separately
AlgoWay documents MT5, while PineConnector and WebhookTrade document MetaTrader routes covering MT4 and MT5. This table describes their published materials, not a test of every broker or account. [S17] [S19] [S23]
| Service | MT4 | MT5 | What to establish before connecting |
|---|---|---|---|
| AlgoWay | Not established by the cited documentation | Documented | EA configuration, symbol mapping and sizing |
| PineConnector | Documented | Documented | Correct EA and supported hosting option |
| WebhookTrade | Documented | Documented | Account connection and execution arrangement |
A broker's mobile app is not proof that an EA can run on that account. Establish where the desktop terminal or service-managed execution actually operates. The methods comparison separates hosting choices from the market being traded.
Terminal, EA and Connection Requirements
Start with the account number and broker server visible in the terminal. Similar server names can lead to a successful login on a different environment. Next, inspect the EA's connection status and its Experts log. Finally, confirm trading permissions and the instrument's specification. These checks isolate account access, message reception and order eligibility.
Keep the broker's order ID beside the bridge event. “Sent” can describe delivery to the EA; it does not necessarily describe acceptance by the broker. The execution guide provides a record-by-record diagnostic method.
Symbols, Lots and Stop Distances
Broker suffixes
A chart ticker such as EURUSD can correspond to a broker symbol with a suffix or prefix. Copy the exact tradable name from the terminal's instrument list. Mapping must identify the intended contract, not merely produce a familiar string. Two gold products can have different contract sizes and trading conditions.
Units versus lots
For a conventional forex contract of 100,000 base-currency units per lot, the following arithmetic illustrates conversion. It is a worked example, not a universal interpretation of the TradingView quantity field.
| Intended base-currency units | Units per lot in this example | Resulting lots |
|---|---|---|
| 1,000 | 100,000 | 0.01 |
| 10,000 | 100,000 | 0.10 |
| 100,000 | 100,000 | 1.00 |
A strategy quantity of 1 might already mean one contract in the source model. Multiplying it as though it represented 100,000 units produces a different trade. Read the outgoing value, the bridge sizing setting and the terminal's resulting lots together. Also check minimum volume and volume increments in the instrument specification.
Pips, points and price
An absolute stop price, a distance in points and a distance in pips are different inputs. Write the intended stop as both a price and a distance for one test trade. That comparison catches a factor-of-ten mistake immediately. Broker price precision alone is not enough to infer how a bridge defines a pip.
A stop based on the chart price can land at a different distance from the broker fill. Different quotes, spread and execution timing matter. Record the chart price, requested stop and accepted stop rather than judging from the chart marker alone.
Testing Entries, Exits and Reversals
Use a demo account to establish the route's behavior before attaching the full strategy. The message format belongs to the receiver; the webhook guide includes a labeled AlgoWay example.
| Test | Evidence to inspect | Unexpected outcome to investigate |
|---|---|---|
| One entry | Terminal lots and instrument | Wrong multiplier or symbol mapping |
| One close | Remaining position and pending orders | A sell opened instead of reducing the long |
| Opposite signal | Final direction and quantity | An unintended hedge or oversized reversal |
| Protective stop | Accepted stop price and covered volume | Entry accepted but protection rejected |
| Repeated entry | Number of resulting orders | Duplicate message or add-to-position behavior |
Account mode affects opposite trades. Establish netting, hedging or reversal behavior explicitly. For a funded program, check prop firm restrictions before choosing a terminal host.
Questions and Answers
Why did the order open with the wrong lot size?
Compare the actual alert quantity with the bridge's sizing mode and broker specification. A valid message can contain units while the destination expects lots. Check for a conversion applied twice.
Does the terminal have to stay online?
An EA-based route needs its execution terminal running and connected. It can run on another permitted machine; keeping your browser open does not replace it.
Why does a valid symbol fail at my broker?
The broker may use a different exact symbol, restrict its trading session or offer a different contract. Read the terminal rejection and instrument specification before changing the strategy.
Does a successful entry prove that the stop is working?
No. Inspect the accepted protective order or position-level stop and its quantity. The entry and protection can have separate outcomes.
Sources & further reading
Official documentation supports the technical claims. Community discussions illustrate user questions, not verified product behavior. Rules and account terms can change.
- S17AlgoWay: platforms, plans and registration
- S19Frequently Asked Questions — PineConnector
- S23TradingView Alerts to MetaTrader (MT4/MT5) — WebhookTrade