Symbol mapping for Telegram-to-MetaTrader copying

Signal symbol to canonical symbol

Normalise the many ways a signal might write an instrument into one canonical name.

Canonical to broker symbol

Resolve the canonical name to your broker's MT4/MT5 symbol, including suffixes like .r or .pro.

Per-account mapping

Each account can map symbols differently, because each broker is different.

Skip and log when missing

If a symbol can't be resolved, the signal is skipped and logged rather than routed to the wrong instrument.

Enabled and disabled symbols

Allow only the instruments you want to trade on a given account.

Cleaner troubleshooting

Mapping decisions are visible in the logs, so misroutes are easy to diagnose.

Frequently asked questions

What about gold and indices naming?

Common cases like XAUUSD to GOLD or US30 to DJ30 are handled, and you can adjust mappings per account.

What happens if a symbol isn't mapped?

The signal is skipped and logged. MarketSync will not guess an instrument.

Why do brokers name the same instrument differently?

Brokers add suffixes such as .r, .pro or m and use their own labels, like GOLD versus XAUUSD or US30 versus DJ30. Mapping translates a signal's symbol into the exact name your broker's account uses.

Do I have to set up a mapping for every symbol by hand?

No. Common forex, metal and index names are recognised out of the box. You only adjust mappings where your broker uses an unusual suffix or label, and you can do it per account.

Does mapping cover crypto and index CFDs too?

Yes, for any instrument your broker lists, including crypto pairs and indices. If a broker simply doesn't offer an instrument, that signal is skipped for that account and logged.

Can two accounts on different brokers follow the same signal?

Yes. Each account keeps its own symbol map, so one signal can route to broker A's naming and broker B's naming at the same time.