What Is a Conditional (Trigger) Order and How Automation Uses It

You set up a strategy that should only act when the market reaches a specific level — buy if price breaks above resistance, or exit if it falls through support. A regular order cannot wait for that moment; it tries to fill the instant you submit it. A conditional trigger order can. This guide has the conditional trigger order explained from the ground up: what it is, how it differs from a standard order, and how automated systems use it to turn a waiting condition into a precise, hands-off action on your exchange.

So much of automated execution is really just conditional logic applied to live prices, so this one order type clears up a lot of confusion for anyone moving from manual trading to automation.

What a conditional (trigger) order actually is

A conditional order stays dormant until a condition you define is met — almost always a specific trigger price. Until the market reaches that trigger, nothing is resting on the order book and nothing can fill. The moment price touches your trigger level, the exchange activates the order and sends it to the book, where it behaves like an ordinary order from then on.

Venues call this by different names — trigger orders, stop orders, or simply conditional orders — but the mechanics are consistent. You define a condition, the exchange watches the market for you, and it acts only when the condition is satisfied. That "watch, then act" behavior is what separates a conditional order from a plain market or limit order that executes immediately on submission.

Trigger price, execution price, and which feed fires it

The biggest point of confusion is that a conditional order usually involves two prices. The trigger price (sometimes called the stop or activation price) is the level that wakes the order up. The execution price is what the order does once awake, and this splits into two forms. A stop-market order triggers and then submits a market order that fills immediately at the best available prices. A stop-limit order triggers and then places a limit order at a separate limit price you set, which fills only at that price or better.

The trade-off is reliability versus control. A stop-market will almost always fill, but at whatever the book offers, so it is exposed to slippage. A stop-limit controls the price but may not fill at all if the market moves straight through your limit. Our explainer on market versus limit orders covers how each type interacts with the book once a trigger fires.

One more setting decides the trigger: which price feed the exchange watches. Many venues let you choose the last price or the mark price. A last-price trigger is fast but can be tripped by a brief wick — a momentary spike from a single large order on a thin book. A mark-price trigger uses a smoothed, manipulation-resistant reference, so it is steadier but can lag a sharp move. Set it deliberately; our explainer on mark price versus last price breaks down the difference.

Common types of conditional orders

Most conditional orders fall into a few roles. A stop-loss triggers when price moves against an open position, closing it to cap the downside. A take-profit triggers when price reaches a favorable target and closes the position. A stop-entry, used for breakout strategies, triggers a new entry only once price breaks through a level you are watching. Each is the same mechanism — a trigger price plus an execution instruction — applied to a different goal. For the practical setup, see how to add stop-loss and take-profit to automated TradingView orders.

How automation uses conditional orders

A conditional order shows up in automation in two distinct ways. In the first, your strategy sends a signal and your automation submits a conditional order to the exchange, where it rests until the trigger fires. The exchange does the waiting, which is reliable because the order lives on the venue even if your automation goes offline. In the second, your automation holds the condition itself, monitoring prices and sending a plain order only when its own condition is met — more flexible, but dependent on your system staying connected. Most robust setups rest protective exits on the exchange so a stop survives a disconnect, while using automation-side logic for complex entries that native order types cannot express.

Conditional orders in a webhook and relay workflow

When your strategy fires a TradingView alert or an automation-platform webhook, something has to translate that signal into an actual order. That is the job of a relay. SignalToExchange is a non-custodial webhook relay: it receives your signal and submits the exact order you defined — including a conditional order with a trigger price and an execution type — to your exchange using trade-only API keys that cannot withdraw funds. Your money never leaves your own exchange account, and the relay does not choose your levels or override your order type; it carries out precisely what your signal specifies. To see how a signal encodes a conditional order, how to structure a TradingView webhook JSON payload for orders shows the fields, and trade-only API keys and how to set them up explains the non-custodial key model.

How conditional orders relate to OCO and reduce-only orders

Conditional orders are the building blocks for smarter structures. An OCO (one-cancels-the-other) order pairs two conditionals — typically a take-profit and a stop-loss — so when one triggers, the exchange cancels the other, preventing a stray live order after your position has closed. A reduce-only flag ensures a conditional exit can only shrink a position, never accidentally flip it. Both build on the trigger mechanism. See what an OCO order is and how automated traders use it and reduce-only orders.

What can go wrong, and how to handle it

A few things trip up automated setups. A stop-market order can slip badly in a thin or fast market. A stop-limit can fail to fill entirely if price jumps through your limit, leaving a position unprotected. A trigger on the wrong price feed can fire on noise or lag a real move. And if your automation resubmits on an error without checking state, you can end up with duplicate orders. The defense is operational: confirm each order was accepted, handle rejections cleanly, and avoid blind retries. Our guide on handling failed and rejected orders in a trading bot covers the patterns worth building around.

Best practices for automating conditional orders

Before you wire conditional orders to live funds, build these habits:

• Decide per order whether you want a stop-market fill (reliable, but exposed to slippage) or a stop-limit fill (price-controlled, but may not fill).
• Set the trigger reference — last price or mark price — deliberately rather than accepting the venue default.
• Rest protective stops on the exchange where possible, so they survive a disconnect in your automation.
• Pair exits with OCO or reduce-only logic so a closed position does not leave stray live orders behind.
• Confirm every submission and handle rejections explicitly; never retry blindly and risk duplicate orders.
• Test with small size or in a sandbox before trusting a conditional order with a full position.

Where this leaves you

A conditional (trigger) order is simply an order that waits for a condition before it acts — a trigger price that wakes it, and an execution instruction that defines what it does next. Once you understand that two-price structure and which feed the exchange watches, the behavior of stops, take-profits, breakout entries, and OCO pairs all follows from the same idea.

When you are ready to route your signals to your exchange with trade-only keys and full custody of your funds, request access / start your free trial and connect your first strategy.

Frequently Asked Questions

What is the difference between a conditional order and a regular order?

A regular order (market or limit) becomes active immediately when submitted. A conditional order stays dormant until a trigger price is reached; only then does the exchange activate it. The conditional order is how you tell the exchange to wait for a specific market condition before doing anything.

What is the difference between the trigger price and the limit price?

The trigger price activates the order. The limit price, used only with stop-limit orders, is the price the resulting limit order fills at or better once it is activated. A stop-market order has only a trigger price and fills at the market once triggered; a stop-limit order has both.

Why did my stop-limit order trigger but not fill?

Because the market moved past your limit price before the order could fill. A stop-limit triggers at the trigger price but only fills at your limit price or better. In a fast move, price can gap straight through that limit, leaving the order unfilled. A stop-market avoids this by filling at the market, at the cost of potential slippage.

Can automation place conditional orders directly on the exchange?

Yes. Your automation can submit a conditional order that rests on the exchange until its trigger fires, which is the more resilient pattern because the order survives even if your automation disconnects. Alternatively, your automation can hold the condition itself and send a plain order when the condition is met.

Does a relay decide my trigger prices?

No. A relay such as SignalToExchange submits exactly the order your signal defines, including the trigger price and execution type. It does not choose levels, add logic, or override your settings. You keep control of the strategy; the relay handles reliable delivery of the order to your exchange.

Automated trading involves risk. SignalToExchange is execution infrastructure and does not provide financial advice, trading signals, or guarantees of any kind.