Supported signal formats

Signal providers all write differently. TradeJournal Pro is built to read the full range of real-world formats — so you don't have to ask your provider to change anything. This page is the complete reference of what the parser understands and how each field is extracted.

› Layouts

• Piped one-liner — SELL GBP/JPY @ 144.34 | SL 144.45 | TP1 144.10 | TP2 143.85
• Multi-line card — Pair: / Direction: / Entry: / TP1: / SL: on separate lines (the crypto standard)
• Symbol-first shorthand — XAUUSD BUY 2340 SL 2330 TP 2360
• Conversational— "going long gold around 2340, stop under 2330, first target 2360" (handled by the AI tier)
• Image / screenshot — text is extracted by OCR, then parsed

› Direction

› Symbols

• Concatenated — XAUUSD, EURUSD
• Slash pairs — EUR/USD → EURUSD, GBP/JPY → GBPJPY, XAU/USD → XAUUSD
• Crypto with quote — BTC/USDT → BTCUSD, $BTC
• Aliases & names — GOLD → XAUUSD, OIL → USOIL, plus Arabic names (ذهب → XAUUSD)
• Indices — US30, NAS100, GER40, SPX500

After normalizing to a canonical ticker, automatic symbol mappingtranslates it to your broker's exact name (XAUUSD.m, f.EURUSD).

› Entry

• Single price — Entry 2340
• Zone / range — 2340–2345, 62,500 – 63,000. Enters at the near edge, or one trade per edge with All-Price mode.
• Market — BUY NOW, INSTANT, @ market → fires immediately
• Pending — entry far from price becomes a limit/stop order

› Stop loss & take profit

• SL — SL, Stop Loss, S/L, 🛑
• TP — TP1–TP5, Target 1, T1, 🎯, or a bare list of prices on separate lines
• Multiple TPs split the position; the stop can move to breakeven after TP1
• TP open — no target; run a trailing stop
• SL/TP can be given as pip distances and are converted to price levels

› Split & edited signals

When the entry arrives in one message and the SL/TP in a follow-up, the copier links them — by Telegram reply, by symbol, or by the most-recent order in the channel (within a few minutes). Follow-ups can carry an SL only, a TP only (your existing stop is kept), both, or bare unlabeled numbers (classified by the trade's entry and direction). An edit that completes the original message is treated as a completion, not a second trade. Full explanation →

› Management commands & notifications

The same channel mixes entries with instructions and status updates. The parser tells them apart:

• Commands (acted on) — close all, close symbol, close position #, breakeven, modify SL, modify TP — in English, Arabic, emoji form, and (via AI) any language
• Notifications (no trade) — "TP1 hit", "SL hit", "running in profit", daily/weekly recaps, and cancelled/void signals are recognized and skipped

› How parsing runs

1. Normalize — clean separators/emoji noise, fix thousands commas, join slash pairs, uppercase.
2. Regex — instant and free; handles the large majority of standard formats.
3. AI fallback — for conversational, unusual, or non-English messages.
4. OCR — image signals are read to text, then re-enter the pipeline.

Each parse gets a confidence score — high-confidence signals auto-execute, partial ones queue for one-tap approval, and unreadable ones are saved for re-run rather than silently dropped.

› Known limits

• Entry zones apply the near edge by default (or one trade per edge with All-Price mode) — not a midpoint average unless you choose it.
• Bare-number follow-ups need the original trade to have an entry price and an unambiguous target; otherwise they're skipped rather than guessed.
• Leverage lines on crypto signals are read but ignored — position size comes from your risk settings, not the provider's suggested leverage.