A provider writes GOLD while the broker lists XAUUSD. The trade idea may be clear, but a destination expecting one exact symbol cannot place an order in a nickname. Symbol mapping translates the source name into the name that destination actually accepts.
That translation is useful only after you establish that the instruments match. Changing letters cannot turn a spot balance into a perpetual contract or a full-size future into its micro counterpart. Think of mapping as an address book, not a currency converter.
In this guide
Three settings that should not be confused
A symbol map changes the destination name. A symbol filter decides whether an instrument is eligible to pass. A per-symbol quantity setting determines an amount; it does not rename the instrument or decide whether the channel is allowed to trade it.
These settings can use familiar-looking lists, which makes mistakes deceptively easy. In TelegramSignal, destination mapping belongs to the route settings described in the setup manual. Check the field label before pasting a list that was prepared for a different purpose.
| Purpose | Illustrative input | Meaning |
|---|---|---|
| Name translation | XAUUSD to GOLD | Send the destination's instrument name |
| Eligibility | Allow EURUSD only | Exclude other instruments from this route |
| Quantity | EURUSD assigned a defined size | Supply quantity under that mode's rules |
Read the contract, not just the abbreviation
Open the destination's instrument specification and inspect the trading unit, minimum quantity and price increment. In MetaTrader, the Market Watch documentation explains where symbol details and specifications are exposed. The broker's actual values matter more than a generic example from a different account.
Two symbols can track the same broad market and still be different contracts. An index CFD may use a familiar short name that resembles a futures root; crypto contracts may differ in settlement asset and quantity convention. Preserve those distinctions in the route's name so that the next person looking at it does not have to repeat the investigation.
Start with one observed source spelling
Use the symbol actually detected from the provider's message. Do not build a large collection of speculative aliases before one real message works. After a successful test, add other observed spellings only where the supported mapping mechanism calls for them.
A broker suffix deserves the same care as the main symbol. A suffixed instrument might belong to a particular account configuration or contract offering, rather than being decoration you can remove freely. Confirm it is tradable in the intended account and compare its specification before deciding it is an equivalent destination.
When two channels mean different things
One channel may use BTCUSD for a broker CFD and another for an exchange instrument. A global assumption about the abbreviation can send both into the wrong market even though the parser reads the letters correctly. Separate channel routes make it easier to preserve the source's intended context.
The same issue appears with gold, where the provider's pip convention may differ from the broker's price increment. Mapping solves the name; it does not solve gold distance units. Check those as a separate part of setup rather than declaring the trade correct because the ticker now looks familiar.
Prove the translation at the destination
For a controlled demo message, compare the source name, the name sent by the route and the symbol on the accepted order. Then check quantity and protective levels. A correct symbol with the wrong contract size is still the wrong result for the trader.
When no order appears, look for a symbol-related rejection rather than changing several mappings at once. The diagnostic guide helps isolate that stage, while position sizing covers the next common source of rejection. One tested translation is more useful than a long list of guesses.
Put the route to a demo test
Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.
Open TelegramSignal in AlgoWay