A signal with three take-profit levels looks reassuringly organised. The important missing detail is often the amount assigned to each level. A total size of 0.30 split three ways is not the same exposure as three orders of 0.30, however neatly the tickets line up in the terminal.

Before turning on multi-target handling, decide what the original size means. It can represent the budget for the whole idea or the size of every separate leg. The copier's selected mode must agree with that interpretation, and the resulting orders must confirm it.

In this guide
  1. Put the quantities on paper
  2. Separate orders and partial closes
  3. The smallest allowed trade can spoil a tidy division
  4. What remains after TP1
  5. Check the whole lifecycle

Put the quantities on paper

Take an illustrative buy with a total intended size of 0.30 lots and three targets. Equal division produces 0.10 lots for each target and preserves the 0.30 total. Repeating the full size produces 0.90 lots overall; the target count has tripled the initial exposure before any target has been reached.

Illustrative allocationTP1TP2TP3Initial total
Equal split of 0.300.100.100.100.30
Equal split across first two0.150.15None0.30
Full 0.30 at every target0.300.300.300.90

The Telegram settings manual documents first-target, first-two-target, split-size and full-size-per-target modes. Select deliberately rather than assuming that “multiple TP” is one universal behaviour. The table above is arithmetic, not a promise that every destination accepts every illustrated quantity.

Separate orders and partial closes

Some arrangements open separate orders with different targets. Others manage a position by reducing its quantity as targets are reached. Those approaches can look equivalent in a summary, but the destination's account model and order history may represent them differently.

Do not decide that several tickets are duplicates simply because they share an instrument and time. Compare their sizes and target levels with the original signal. Conversely, several identical full-size entries arriving from separate routes are not explained merely by saying “there were several targets”; trace their origin using the diagnostic guide.

The smallest allowed trade can spoil a tidy division

Suppose the destination permits increments of 0.01 lots and you want to divide 0.02 lots equally across three targets. The exact result, about 0.00667 per leg, is not a valid order size under that assumption. The software must follow its documented normalisation behaviour, or the request may be rejected; a spreadsheet's extra decimal places do not persuade a broker.

Verify both the minimum quantity and increment on the actual destination. Some markets impose a minimum order value as well. Our sizing article explains why changing a target split can affect acceptance even when the original total was valid.

What remains after TP1

In the equal-split example, closing the first 0.10 lot leg leaves 0.20 lots. A later instruction to close half needs an understood reference: half of the original 0.30 or half of the remaining 0.20? These produce 0.15 and 0.10 respectively, so test the destination's supported semantics instead of supplying an interpretation after the event.

Breakeven is another separate action. A remaining order's stop can be moved towards its own entry under supported rules, but costs and execution can keep the eventual net result below zero. Read updates and breakeven before treating a target hit as proof that the entire remaining trade is risk-free.

Check the whole lifecycle

On a demo route, record the initial total, every target allocation and the expected remainder. Then inspect the destination after each action: filled quantity, closed quantity, outstanding orders and current stops. A correct opening split does not prove that a later close instruction targets the right leg.

Finally, add the other signals reaching the same account. Three modest legs from each of several channels can become a substantial combined position in the same market. The risk-management guide moves from this one-signal arithmetic to the account as a whole.

Put the route to a demo test

Use the current setup instructions and verify the resulting orders in your destination account. Start with a configuration you can inspect before adding more sources.

Open TelegramSignal in AlgoWay