Broadcaster Configuration
A broadcast source is your description of "this account, sending these trades to my other NinjaTrader installations, with these rules." You can run any number of sources on the same account or across different accounts. Broadcasting requires the Elite plan.
Every receiving login must be yours, signed in on one of your own NinjaTrader installations. Signal Share is not for sending trades to other people.
The source
| Field | What it controls |
|---|---|
| Name | Display name on your broadcaster page and on every invite you send to your receiving logins. Required. |
| Description | Free text. Shown on the invite when your receiving login reviews it. |
| Source Account | Which NinjaTrader account on this NT8 is being shared. Required. |
| Instruments | Optional list of instruments (for example ES, NQ). Leave it empty to share every instrument. |
Broadcast triggers
These two switches decide what kind of order activity gets shared on this source.
| Switch | What it covers | Default |
|---|---|---|
| Copy Manual Trades | Trades you place by hand (Chart Trader, DOM, Account Manager, hotkeys) | On |
| Copy Webhook Trades | Trades triggered automatically (NinjaScript strategies, ATI, CrossTrade webhooks, MCP) | On |
The two are independent. A common pattern is to run a discretionary account with only manual trades shared, and run a strategy in parallel with only automated trades shared, even on the same account.
Receiver enforcement
This section of the source form controls how strictly your receiving accounts must mirror the broadcasting account's position. The three settings stack: each one assumes the one above it is on.
Sync Strategy
When Sync Strategy is on, the broadcast tells the receiver where your position is intended to be after the trade (long, short, or flat), in addition to placing the order. The receiver checks that against its own position before acting.
When it is off, only the order itself is shared. The receiver places the order and moves on with no position-level check.
Sync Strategy is the gate for everything below. With it off, the rest does nothing.
Target Quantity
When Target Quantity is on (in addition to Sync Strategy), the broadcast also tells the receiver the exact size your position should be after the trade. The receiver converges on that target instead of just reacting to one order at a time.
Use this when you want your receiving accounts to land on an exact size even if they missed a previous signal. It is what lets a receiving installation catch up gracefully after a brief disconnect.
Out of Sync Behavior
When Sync Strategy is on, the broadcast also carries an out-of-sync rule. The receiver consults it when its own position does not match what the broadcast says it should be.
| Option | What the receiver does when out of sync |
|---|---|
Wait | Stop trading the instrument until alignment is restored. Default. Safest. |
Flatten | Flatten the account on that instrument, then resume. |
Ignore | Process the signal anyway. Dangerous. The receiving account's position can drift further from the broadcasting account on every signal. |
Resync | Place a corrective order to force the receiving account's position to your target. Only available when Target Quantity is on. |
Resync is the most aggressive setting.
Correction orders are size-limited (add-on v1.13.8 and later). A correction far larger than your target position and the triggering signal is withheld rather than submitted, and the receiver logs a warning in its activity log and signal history. This protects a receiving account whose local position has diverged badly (for example, after manual trading on that account) from receiving a large corrective market order without review.
Delivery guarantees (v1.13.8 and later)
- Dual-path broadcasts. Every broadcast travels over both the live connection and HTTP, deduplicated server-side, so a degraded connection on your machine cannot silently drop signals.
- Missed-signal replay. A receiving installation that reconnects after a brief outage automatically requests the broadcasts it missed. Replays arrive in order and are checked against the execution record, so a receiver never runs the same signal twice.
- Burst shedding. Past 100 signals in 10 seconds from one broadcasting login, only order modifications are shed; entries, exits, and cancels still deliver. Past 300, everything is shed. Shed events are counted and visible to support.
Receiver sizing
Signals mirror one-for-one: if you place 4 contracts, each receiving login places 4 on its mapped account. To trade a different size, see Scaling to a different contract size.
Each source also has a limit on how many receiving logins it can hold.
Combining multiple sources
If you run several sources on the same account, the same order can match more than one. In that case the broadcaster combines the matching sources into a single signal, applies the strictest enforcement across all of them, and delivers one copy to every receiving login attached to any of those sources.
Out-of-sync uses a strict-wins hierarchy: Resync beats Flatten beats Wait beats Ignore. This means overlapping sources is safe. A loose source cannot weaken the rules of a stricter source it overlaps with.
Activating, pausing, deleting
Each source has an Active toggle. Turning it off stops the source from matching any further orders. Deleting a source ends every receiving connection attached to it. There is no undo, but you can re-invite your receiving logins later from a new source.
How to add a broadcast source
- Sign in with the CrossTrade login on the NinjaTrader installation you trade from. Open
/user/signal-shareand switch to the Broadcasting tab. - Click Create Source and fill in the name, source account, and optional instrument filter.
- Choose your Broadcast Triggers. Both are on by default.
- Choose how strictly your receiving accounts stay in sync. Sync Strategy is what unlocks the rest.
- Save. The source is live. From the source card's Invite button, enter the email address of each of your other CrossTrade logins (one per receiving installation). A login cannot invite itself.
Each receiving login then accepts the invite. See Receiver configuration for the receiving side.