A broker symbol suffix is extra text that a broker adds to an instrument's name in MetaTrader, such as the ".pro" in EURUSD.pro. Brokers use suffixes and prefixes to label their own versions of an instrument, which can differ by account type or contract. An order must use the exact name in the receiving account's Symbols list, including any prefix, suffix and capital letters. A TradingView ticker is not automatically that name.
A TradingView chart of OANDA:EURUSD produces the ticker EURUSD, while the broker account may list EURUSD.pro. Symbol names sit alongside lots, pips and margin in the trading mechanics library.
Broker symbol suffixes at a glance
Scroll horizontally to read every column.
| Term | What it means | Where to read it |
|---|---|---|
| Broker symbol | The exact instrument name an MT5 order must use, as the broker defines it on that account's server. | MT5 Symbols window (Ctrl+U): the Symbol column |
| Prefix or suffix | Text before or after the base name, such as i. or .pro. Capital letters count. |
The same Symbol column, then the symbol's Specification |
| TradingView ticker | The chart's symbol without the exchange prefix, such as EURUSD. |
Pine: syminfo.ticker. Alerts: {{ticker}}
|
| TradingView ticker ID | Prefix, colon and ticker, such as FX:EURUSD. The prefix identifies the data provider or exchange. |
Pine: syminfo.tickerid and syminfo.prefix
|
| Symbol Mapping | A PineConnector Portal rule that swaps an incoming From name for a To name before the terminal receives it. | PineConnector: Match your broker's symbols |
| EA Prefix and Suffix | PineConnector EA inputs that add text before or after the symbol received in an alert. | PineConnector EA settings |
| Unknown symbol | MetaTrader does not recognise the requested name. | Experts tab. MQL5 lists ERR_MARKET_UNKNOWN_SYMBOL (4301). |
PineConnector's syntax reference defines the symbol field of a message as "the exact broker symbol, including suffix and letter case".[1] Pine Script v6 describes the ticker, ticker ID and prefix variables.[2] MQL5 lists 4301 as "Unknown symbol" among its runtime errors.[3] Platform details on this page are as of 25 September 2026.
Why does my broker symbol have a suffix?
Brokers define the symbols on their own MetaTrader servers. MetaTrader 5 Help describes the Specification window as showing parameters "set by a broker".[4] Its custom-symbol page refers to "the names of symbols provided by the brokers".[5] Two brokers can therefore list the same currency pair under different names, and one broker can list several versions.
A prefix or suffix can label one of those versions. PineConnector's Symbol Mapping guide notes that "names and suffixes can differ between brokers and account types".[6] Its examples include EURUSD.i, EURUSD.mini and i.EURUSD.micro.[6][7] The broker that uses a label decides what it means. Read the symbol's Specification rather than guessing from ".pro", ".mini" or "i.".
Order symbol = prefix + base name + suffix, copied character for character from the receiving account's Symbol column
Either the prefix or the suffix can be empty, and capital letters are part of the name. PineConnector warns that two labels can refer to the same general market "without being interchangeable order symbols".[6] Its guide adds that a mapping "does not establish that two broker contracts have the same size, pricing or trading conditions".[6] Contract size, digits and volume limits belong to each named symbol.
How do you find the exact symbol name in MT5?
- Open MetaTrader 5 logged in to the account that will receive the orders.
- Open View, then Symbols, or press Ctrl+U.[8] MetaTrader 5 Help says the window lists "All symbols available in the platform".[4]
- Find the instrument and read the Symbol column, not the longer description. Copy the complete spelling, including any prefix, suffix and capital letters.[6]
- In Market Watch, right-click that symbol and choose Specification. Read its contract size, digits, minimal volume and volume step.[4]
An Expert Advisor reads the same details through MQL5, where SYMBOL_DESCRIPTION holds the "Symbol description" and SYMBOL_EXIST reports whether a "Symbol with this name exists".[9]
A name must also be usable in the terminal. MetaTrader 5 Help states that data for a symbol hidden in Market Watch "cannot be used in MQL5 programs and the Strategy Tester".[4] The PineConnector EA's Enable Symbols input has a published default of "Auto-enable on trade".[10] On PineConnector Edge, the hosted MT5 option, the docs say to find the symbol in the broker's supported MT5 mobile app, web terminal or desktop terminal for that same account.[7] Edge also has a Symbols tab (Portal → Edge → Symbols) that lists every symbol the broker offers on that account, searchable, with its specification, such as digits, contract size, minimal volume, volume step and stops level. Copy the exact name from there into the alert instead of retyping it from a terminal (Edge Symbols guide).
How are TradingView tickers different from broker symbols?
A TradingView ticker ID joins a prefix and a ticker with a colon. Pine Script v6 defines syminfo.prefix as "the symbol's broker/exchange identifier". syminfo.ticker holds the symbol "without the exchange prefix". syminfo.tickerid holds both, plus any dataset modifiers such as extended hours.[2]
FX:EURUSD and OANDA:EURUSD are therefore two TradingView datasets for the same currency pair, from two data providers. TradingView explains that its ICE forex symbols are composites from many contributors, "while others are separate forex brokers". Volume and trading hours can vary by provider.[11] Symbol Search shows each row's data source on the right.[12]
Both charts produce the same ticker. The alert placeholder {{ticker}} returns the "ticker of the symbol used in alert", and {{exchange}} returns its exchange.[13] Neither adds your broker's prefix or suffix. PineConnector's docs point out that {{ticker}} and syminfo.ticker use TradingView's symbol, which your broker may not share.[14] Its no-code guide says to use {{ticker}} in place of EURUSD "only when TradingView's ticker matches your broker's symbol".[15]
TradingView's own Broker Integration Manual defines symbol mapping as "the matching between the broker's and TradingView symbols".[16] The chart's data provider is also not your broker's price feed, as the guide to why TradingView prices differ from your broker's explains.
Worked example: one alert, two broker symbols
Illustrative example, not a recommendation. A trader charts OANDA:EURUSD. The alert's Message field sends LicenseID,buy,EURUSD,vol_lots=0.10,sl_pips=20. The alert is tested on two USD demo accounts in turn. Account A lists EURUSD.pro with a contract size of 100,000 EUR. Account B lists EURUSD.mini with a contract size of 10,000 EUR.
Both symbols quote to five decimals, so one PineConnector pip is 0.0001.[17] Neither account lists plain EURUSD, so each needs a translation.
| Step | Account A: EURUSD.pro | Account B: EURUSD.mini |
|---|---|---|
| Symbol Mapping rule | From EURUSD, To EURUSD.pro | From EURUSD, To EURUSD.mini |
| Units in 0.10 lot | 0.10 × 100,000 = 10,000 EUR | 0.10 × 10,000 = 1,000 EUR |
| Pip value per 1.00 lot | 0.0001 × 100,000 = 10 USD | 0.0001 × 10,000 = 1 USD |
| 20-pip stop at 0.10 lot | 20 × 10 × 0.10 = 20 USD | 20 × 1 × 0.10 = 2 USD |
Size from vol_dollar=20 and sl_pips=20
|
20 ÷ (20 × 10) = 0.10 lot | 20 ÷ (20 × 1) = 1.00 lot |
Illustrative names and contract sizes, not any broker's. The pair is quoted in USD and the accounts are in USD, so no currency conversion is needed.
The mapping fixes the name on both accounts. The contracts stay different. The fixed vol_lots=0.10 requests ten times as many euros on account A as on account B. A loss-based size such as vol_dollar= follows PineConnector's formula instead: lots = planned loss budget ÷ (stop distance in pips × pip value per 1.00 lot), before broker volume rounding.[18] With each symbol's own pip value, the formula gives a tenfold difference in lots. Each result must still fit the symbol's minimal volume, volume step and maximum.
The "mini" in a symbol name is a broker label, not the mini lot convention in the lot size, contract size and lot step guide. The guide to pips, points and pip value covers pip value per lot.
How does PineConnector Symbol Mapping work?
PineConnector's Symbol Mapping changes an incoming symbol name to the name your broker uses. The alert keeps its existing symbol, and the translation happens "before it is sent to the terminal".[6] The Symbol Mapping guide gives these steps as of 25 September 2026:
- Open Signals in PineConnector Portal and select Signal Modifier.
- Turn Symbol Mapping on and select Add Symbol.
- In From, enter the symbol your alert message sends. In To, enter the exact broker symbol.
- Select Save.
Both fields are case-sensitive, and the Signal Log shows the converted symbol. The guide lists Symbol Mapping as included with the Plus and Pro plans.[6] The broker name can live in one of three documented places, so choose one deliberately:
-
In the message. Type the broker symbol into the TradingView alert's Message field, for example
LicenseID,buy,EURUSD.pro,vol_lots=0.10(illustrative). The trigger chart and the order symbol are separate.[7] - In Symbol Mapping. Keep EURUSD in the message and add a rule From EURUSD, To EURUSD.pro. The From value must match what the message actually sends.[6]
-
In the EA inputs. The PineConnector EA's Prefix and Suffix inputs "add text before or after the symbol received in the alert". The docs' example turns EURUSD into
broker.EURUSD.mini.[19]
Pine Script code and TradingView placeholders can also change the name, so the guide says to review the entire path before adding another transformation.[6] In an illustrative case, a mapping produces EURUSD.pro and the EA suffix adds ".pro" again, so the request names EURUSD.pro.pro. Check the final symbol the EA uses when you combine the two.[19]
Keep the execution stages apart when a symbol fails. The alert condition becomes true and the TradingView alert triggers, then the webhook delivers the message. PineConnector processes the signal, which is where Symbol Mapping applies. The EA builds its order request with any Prefix or Suffix. Only then does MetaTrader look up the name and the broker check volume, price and stops.
A correctly translated symbol does not mean the broker will accept the rest of the order. PineConnector's guide suggests a demo alert with the intended incoming symbol, then a check of the Signal Log and of the order's instrument, direction, volume and targets in MetaTrader.[6] The stage-by-stage diagnosis for a webhook with no MT5 trade covers the other failure points.
What goes wrong with broker symbols?
- Changing the capitals. PineConnector's error guide states that EURUSD and eurusd are not interchangeable in its syntax. For an unknown symbol, it says to copy the name exactly from the broker's Symbols list.[20]
-
Sending the ticker ID.
syminfo.tickeridincludes the prefix, such asFX:EURUSD.[2] A TradingView identifier is not a MetaTrader symbol name. - A From value that the message never sends. The mapping guide warns that a chart label and the symbol inside a generated message may differ.[6]
- One License ID, several accounts. A License ID can reach several connected accounts. PineConnector says to check the broker symbol and EA settings on every destination account.[21] A name that is right for one broker may not exist on another.[6]
-
Trading a custom symbol. MetaQuotes notes that custom symbol names often carry suffixes "such as EURUSD.1 or EURUSD.f". It also states that "Real trades cannot be executed on custom symbols".[5] MQL5 flags these with
SYMBOL_CUSTOM.[9] - Expanding to a watchlist too early. PineConnector's recommendations say to verify suffixes and mappings before expanding to more symbols or a watchlist.[14]
PineConnector's error guide lists 4106 as the MetaTrader 4 unknown-symbol error.[20] Its MT5 table pairs an "Invalid request" detail beside 4756 with checking the exact symbol and the full request.[22] The docs do not name a separate MT5 code for an unknown symbol, so read the full Experts entry. The pre-flight checklist for symbol, lot size and account covers the other fields of the message. A correct symbol only decides which instrument receives an order.
Frequently asked questions
What does EURUSD.pro mean?
EURUSD.pro is a broker's MetaTrader name for a EURUSD contract, where ".pro" is a suffix that broker chose. Suffixes can mark variants such as an account type, but the meaning is broker-specific. Read the symbol's Specification in MetaTrader 5 for its contract size and volume rules, and use the exact name, suffix included, in any order message.
Why does my broker symbol have a suffix?
Brokers name the instruments on their own MetaTrader servers, and some add a prefix or suffix to separate versions of the same market. Names and suffixes can differ between brokers and between account types. Two differently named versions can also differ in contract size or pricing, so a shared base name such as EURUSD does not make the contracts interchangeable.
How do I map TradingView symbols to MT5 symbols?
Find the exact name in the MetaTrader 5 Symbols window (Ctrl+U), then either type it into the TradingView alert message or translate it. PineConnector's Symbol Mapping, under Signals and Signal Modifier in Portal, swaps a From name such as EURUSD for a To name such as EURUSD.pro before the terminal receives it. Confirm the result with a demo alert.
Is FX:EURUSD the same symbol as OANDA:EURUSD on TradingView?
Both are TradingView datasets for the euro against the US dollar, from different data providers named by the prefix before the colon. Volume and trading hours can vary by provider. Both give the ticker EURUSD through the {{ticker}} placeholder and syminfo.ticker. Neither is your broker's MetaTrader symbol, which may carry its own prefix or suffix.
Are MT5 symbol names case-sensitive?
For PineConnector messages, yes. PineConnector's syntax reference asks for the exact broker symbol, including suffix and letter case, and its error guide states that EURUSD and eurusd are not interchangeable. Symbol Mapping's From and To fields are case-sensitive too. Copy the name from the Symbol column of the MetaTrader Symbols window rather than typing it from memory.
Reviewed 25 September 2026. Facts were checked against the linked sources on that date. Nothing in this article was tested on a trading account and no code was compiled.
Related reading
- Trading mechanics: orders, lots, margin and costs
- Wrong symbol, lot size or account: the pre-flight checklist
- Lot size, contract size and lot step
- Why TradingView prices differ from your broker's
- Webhook received but no MT5 trade: a stage-by-stage diagnosis
Sources
- PineConnector – PineConnector Syntax: message structure, accessed 25 September 2026.
- TradingView – Pine Script v6 User Manual: Chart information, accessed 25 September 2026.
- MetaQuotes – MQL5 Reference: Runtime errors, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Market Watch, accessed 25 September 2026.
- MetaQuotes – MetaTrader 5 Help: Custom financial instruments, accessed 25 September 2026.
- PineConnector – Match your broker's symbols (Symbol Mapping), accessed 25 September 2026.
- PineConnector – Test your setup, accessed 25 September 2026.
- PineConnector – FAQ: How do I open the Symbols list?, accessed 25 September 2026.
- MetaQuotes – MQL5 Reference: Symbol properties, accessed 25 September 2026.
- PineConnector – EA settings reference: Enable Symbols, accessed 25 September 2026.
- TradingView – What is the difference between ICE and other forex providers?, accessed 25 September 2026.
- TradingView – TradingView Symbol Search: tips for finding assets, accessed 25 September 2026.
- TradingView – How to use a variable value in alert, accessed 25 September 2026.
- PineConnector – Best Practices & Tips: keep symbols and units explicit, accessed 25 September 2026.
- PineConnector – Connect your strategy: match the signal to the broker action, accessed 25 September 2026.
- TradingView – Broker Integration Manual: Symbol mapping, accessed 25 September 2026.
- PineConnector – PineConnector Syntax: PineConnector pip, accessed 25 September 2026.
- PineConnector – PineConnector Syntax: loss-based sizing, accessed 25 September 2026.
- PineConnector – EA settings reference: Symbol Prefix and Suffix, accessed 25 September 2026.
- PineConnector – EA errors: 4106 unknown symbol, accessed 25 September 2026.
- PineConnector – Send one alert to several accounts: before you begin, accessed 25 September 2026.
- PineConnector – EA errors: match the message beside 4756, accessed 25 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
