Slippage is the difference between the expected fill price and the actual fill price on an executed order. In a copy trading setup, slippage can affect the leader, follower accounts, or both — and the amounts can differ across accounts.
You might need this article if:
Follower accounts are filling at different prices to the leader
You're seeing price differences between accounts after a trade
A follower's entry or exit price was noticeably different from what the leader got
What Tradecopia controls and what it doesn't
Tradecopia sends an order instruction to the broker. Everything after that point is the broker's domain.
Phase | Controlled by |
Detecting the leader trade and replicating the instruction | Tradecopia |
Order routing and matching engine | Broker |
Fill price and execution quality | Broker |
Exit execution when the leader closes | Broker |
Market conditions at the time of fill | Market |
Tradecopia has built its engine with high-level concurrency to minimise transmission delay — but once the order reaches the broker, execution results are entirely outside Tradecopia's control.
Why follower accounts fill at different prices than the leader
Each account in a copy group is independent at the broker level. When Tradecopia replicates an order, each broker processes it through its own matching engine, liquidity routing, and order queue.
This means:
Fill prices can differ between the leader and each follower
Fill prices can differ between follower accounts on different brokers
Some followers may see slippage while others on the same group do not
The leader typically receives better fills. It is the originator of the trade — the order reaches the leader's broker first. Follower orders are replicated after the leader fill event is detected, which means they arrive at the follower's broker slightly later. In fast markets, this time difference can produce meaningful price differences.
Common causes of slippage
Market conditions
News events — economic releases, central bank announcements, and major data prints create sudden liquidity gaps that produce significant slippage across all accounts
Equity market open — the first minutes of the trading day often have wider spreads and faster price movement
Low liquidity periods — overnight sessions and pre-market conditions reduce available liquidity at any given price level
Broker-side factors
Each broker has its own execution engine, liquidity routing, and order processing speed
Tradovate is known for wider slippage compared to other supported brokers — this is a characteristic of their execution model
TopStepX uses market-based fill-on-event replication — entries are sent as market executions after the leader fill, which naturally introduces fill price differences compared to pending-style replication on other brokers
Tradovate API rate limits cause delays when you have many accounts trading at high frequency — this is documented by Tradovate and affects heavy scalpers and large copy groups on Tradovate connections specifically. See How broker API rate limits affect trade replication for detail.
Your hardware and network
CPU overload — if your computer does not have sufficient processing power for your copy group size, transmission delays are introduced before the order even reaches the broker
Network instability — a poor or inconsistent internet connection adds latency to order transmission
Large copy groups on lower-powered hardware amplify both of these effects
Trading style
Heavy scalping — very short holding times mean replication latency is a larger proportion of the overall trade duration. A 2-second scalp with a 500ms replication lag produces very different results than a 10-minute swing trade with the same lag
Large lot sizes on small targets — a slight price move during exit, or the commission cost on a large position, can exceed the intended profit target entirely. This is amplified in volatile conditions
Slippage on risk management exits
When your risk manager triggers and sends a market close instruction, the exit is executed by the broker at market price. In volatile conditions, the market can move between the trigger point and the time the close instruction is actually executed. The final exit price may be beyond your configured threshold — the risk manager fired at the correct level, but broker execution at that moment could not achieve the exact price.
This is normal broker execution behaviour. The risk manager triggered correctly. The fill result is determined by market conditions at the time the close instruction reaches the exchange.
How cloud plans reduce transmission-layer slippage
Tradecopia Pro+ Lite and Pro+ run on Tradecopia's own infrastructure rather than your local machine. This eliminates two of the user-side causes listed above: CPU limitations and network instability at your end are no longer factors in transmission delay. This makes the cloud plans particularly beneficial for users with large copy groups, high-frequency scalping strategies, or hardware that struggles under load.
Broker-side slippage and market condition slippage remain — the cloud plans address the transmission layer, not the execution layer.
How to assess whether slippage is normal
Check the broker order history — review the actual fill price and exit price for every affected order directly on the broker platform. This is the ground truth for any slippage assessment.
Compare leader and follower fills — note the fill price on the leader account and each affected follower. A small difference is expected. A large difference warrants further investigation.
Consider the context — was the trade placed during a news event or market open? Was it a heavy scalp or large lot size? Is the account on Tradovate, which has known wider slippage characteristics? Are there many accounts in the copy group running at high frequency?
If slippage is abnormally large and can't be explained by any of the factors above, contact the Tradecopia support team with the affected account, broker, and trade details — and we'll investigate the transmission timing.
Related articles
How broker API rate limits affect trade replication — Tradovate rate limits as a slippage contributor
Why didn't my risk management settings trigger? — includes context on slippage during risk management exits
What does Tradecopia need to copy trades? — replication requirements and what can delay execution