Symbol mapping

Why mapping matters

TradingView tickers are normalised for humans — BTCUSD, EURUSD, ES1!. Brokers almost always expect a more specific symbol: BTCUSDT, EUR/USD, ESM2026. Symbol mapping bridges that gap.

Where to configure

Open Bridge → Modifier. The symbol mapping table lives under the signal authentication section. Each row is a from / to pair:

BTCUSD  →  BTCUSDT
ETHUSD  →  ETHUSDT
SPX     →  SPY

Mapping syntax

Mapping entries are case-insensitive. Whitespace is trimmed. Use uppercase for consistency — TransisTrade normalises incoming payloads to uppercase before lookup.

Exact match

The simplest form. An incoming BTCUSD becomes BTCUSDT.

Template substitution

You can use {{base}} and {{quote}} tokens when the broker wants a specific join character.

{{base}}USD  →  {{base}}/USD  (useful for FX)
{{base}}{{quote}}  →  {{base}}-{{quote}}  (for some crypto exchanges)

Wildcards and prefixes

TransisTrade supports a conservative wildcard set to avoid surprises:

• *USD → *USDT — any ticker ending in USD maps to USDT.
• FX:* — match only symbols from the FX: TradingView exchange prefix.
• NASDAQ:*, NYSE:* — same idea for US equities.

Per-account overrides

Mappings can be scoped. Open a connection in Connections and add overrides that only apply when the signal targets that account. This is how teams run the same strategy on IBKR for equities and Binance for crypto.

Common examples

TradingView → Binance perp

BTCUSD     →  BTCUSDT
ETHUSD     →  ETHUSDT
{{base}}USD →  {{base}}USDT

TradingView → Interactive Brokers (equities)

NASDAQ:AAPL  →  AAPL
NYSE:TSLA    →  TSLA

TradingView → OANDA (FX)

EURUSD  →  EUR_USD
GBPUSD  →  GBP_USD
USDJPY  →  USD_JPY