Stops, targets and trade management
How SL and TP are placed, what happens on break-even and partial-close messages, and how trailing behaves.
Placement at entry
- SL and TP from the signal are attached to the order, so protection exists from the first tick.
- A signal without a stop is rejected by default — see the completeness gate in How PipSync works.
- Levels closer than the broker's minimum stop distance are pushed to the nearest allowed level, and that adjustment is logged.
- Multiple targets are handled per the channel's multi-TP setting.
Follow-up management
| Provider message | What PipSync does |
|---|---|
| Move SL to entry / break-even | Modifies the stop on the matched open position. |
| TP1 hit, close half | Partial close of the matched position; the remainder keeps its stop and next target. |
| Move TP to X | Modifies the target. |
| Close now | Market close of the matched position. |
| Anything unmatched | Logged, not applied. Never guessed onto another trade. |
Modifications that the broker accepts as "no change needed" count as success — a stop already at the requested level is not an error.
Trailing stops
Trailing is optional and off by default. When enabled per channel or account, the stop follows price at your configured distance and only ever moves in your favour.
- Trailing runs server-side, so it keeps working when your machine is off.
- A provider message that moves the stop backwards is ignored while trailing is active.
- Trailing and break-even can be combined: break-even first, then trail from a given profit distance.
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.
Voir aussi