Appearance

Personalize your experience

Mode

Accent Color

Direction

Step 2 — Tagging

Wizard step

Optional. Client order ID templates, signal-level metadata and order linking — the machinery that makes live orders reconcilable against broker statements.

When to bother

Skip this step entirely while you are . Tags do nothing in a simulation. They earn their keep the moment real orders leave the platform, because that is when you need to answer like “which signal placed this fill” and “did the broker double-send this order” against a statement that knows nothing about your .

ℹ

Note:The short version: , skip it. capital, configure it before the first order, not after the first reconciliation problem.

Client order ID

The client order ID travels with every order to the broker. It serves two purposes: deduplication, so a retried request cannot become two positions, and attribution, so a fill in a statement can be traced back to the signal that caused it. It is built from a template of segments encoding , direction, broker and sequence.

Client order ID structure

template    {prefix} - {context} - {counter}

prefix      GC-NIFTY        you choose this
context     LE              LE / LX / SE / SX
counter     0001            auto-increment, padded

result           GC-NIFTY-LE-0001
next entry       GC-NIFTY-LE-0002
matching exit    GC-NIFTY-LX-0001

┌──────────────────────────────────────────────────┐
│  available segments                               │
├──────────────────────────────────────────────────┤
│  I        instrument     NIFTY, BTCUSDT           │
│  D        direction      B = buy, S = sell        │
│  B        broker         ZRD, BIN, FYR            │
│  context  LE  long entry      LX  long exit       │
│           SE  short entry     SX  short exit      │
│  counter  sequential number                       │
└──────────────────────────────────────────────────┘

Field	Type	Description
clientOrderIdPrefix	string	Base prefix for every order this places. Combined with context and counter. "GC-NIFTY" becomes "GC-NIFTY-LE-0001".
counterTemplate	string	Pattern used to assemble the ID. Segments: I (), D (direction), B (broker), and the LE/LX/SE/SX order context.
counterPadding	"YYYY" \| "MMDD" \| custom	Padding for the sequence number. YYYY pads to four digits (0001–9999). MMDD uses date-based numbering. Custom allows any length.

Caution:Choose the padding for the volume you expect. YYYY gives you 9,999 orders before the counter wraps, which sounds ample until a grid strategy on a 1-minute reaches it in a fortnight. A wrapped counter produces duplicate IDs, and a duplicate ID is exactly what deduplication will act on.

Order context

Every order is tagged automatically with a context that records whether it opens or closes, and on which side. This is what makes an exit matchable to its entry.

Tag	Type	Description
LE	context	Long entry — a buy that opens a .
LX	context	Long exit — a sell that closes an existing long.
SE	context	Short entry — a sell that opens a .
SX	context	Short exit — a buy that closes an existing short.

Signal tags

Signal tags attach a label to an order identifying which condition set produced it. With two or more entry signals running, this is the only way to answer the question that actually matters after a month of trading: which of them is making money?

Field	Type	Default	Description
signalTags	Record<string, string>	{}	Signal name to tag label. When a signal fires, its tag joins the order . { "rsi_oversold": "-30", "macd_cross": "MACD-BULL" }.

★

Pro tip:The preset buttons cover the common shapes — date-based (YYYYMMDD), sequential (SEQ-001), signal-derived (SIG-). Pick one and keep it consistent across strategies; per- tag formats defeat the of tagging.

Conditional tags

Conditional tags add based on state — order direction, market , time of day. They evaluate at placement time and enrich the order record for later analysis, without affecting whether the order is placed.

Order linking

Order linking connects an entry to its exit through a shared reference. With auto-linking on, LE↔LX and SE↔SX pairs are given a common trade reference, which is what allows a to be reconstructed — and P&L attributed — at the order level rather than the position level.

Field	Type	Default	Description
autoOrderIdLinking	boolean	false	Generate shared reference IDs linking entries to exits. "GC-LE-0001" links to "GC-LX-0001" through a common trade reference.

Before moving on

A meaningful client order ID prefix, distinct from your other strategies
Counter padding sized for the order volume the will actually produce
Signal tags configured if more than one is running
Auto order ID linking enabled for paired entry and exit tracking
Or: skipped entirely, because this is only being backtested

Appearance

Step 2 — Tagging

When to bother

Client order ID

Order context

Signal tags

Conditional tags

Order linking

Before moving on

See also

Related articles

Appearance

When to bother

Client order ID

Order context

Signal tags

Conditional tags

Order linking

Before moving on

See also

Related articles

Related to Step 2 — Tagging