Signal formats the parser understands
Which message layouts parse cleanly, how multiple take-profits are handled, and what the confidence score means.
Layouts that work
The parser is not a regex list — it reads the message. Emoji, extra prose, mixed languages and inconsistent labels are all fine as long as the numbers are unambiguous.
SELL GBPUSD 1.2740 SL 1.2790 TP 1.2650
BUY LIMIT XAUUSD 2308 - 2312 Stop loss: 2298 TP1 2320 TP2 2335 TP3 open
Getting long EURJPY here around 168.40, stop below 167.90, first target 169.50.
Multiple take-profits
When a signal carries several targets, PipSync splits the position so each target owns a slice. Configure the behaviour per channel:
Split evenly
One position per target, each sized to an equal share of the risk budget.
First target only
One position, TP set to TP1. The simplest and the least likely to surprise you.
Last target only
One position aimed at the furthest target. Bigger swings, lower hit rate.
The confidence score
Every parsed signal carries a score for how certain the parser is. It drops when fields are implied rather than stated, when numbers are ambiguous, or when the message mixes two setups.
| Score | Typical cause | Default behaviour |
|---|---|---|
| High | All fields explicit and labelled. | Treated like any complete signal: traded if auto-trading is on, otherwise waiting on the Signals page. |
| Medium | Direction not written out but derived from where the stop-loss sits relative to the entry. SL and TP are never filled in. | Same as High. |
| Low | Ambiguous numbers, two setups in one message, heavy formatting. | Held for manual approval. |
Signals that are held back wait on the Signals page for your approval. See Filtering a noisy channel.
What will not parse
- Screenshots and chart images with no text.
- Voice notes and video.
- Messages that name no instrument — "buy now" on its own goes nowhere.
- Signals split over several messages where the stop arrives minutes later, unless the follow-up references the entry.
Toujours bloqué ?
Envoyez le signal brut, l'horodatage et le nom du compte. N'envoyez jamais de mots de passe, de clés API ni d'identifiants de courtier.