Auto Trail Stop Futures Math: Trigger, Distance, Frequency

Every auto trail stop futures traders run through PickMyTrade comes down to three numbers: a trigger, a distance and a frequency. Most people set them once and picture a stop that hugs price one tick behind. That isn’t what happens.

The stop moves in steps. On PickMyTrade’s day-trading preset, a 10-tick distance with a 5-tick frequency, it can sit 14 ticks behind the best price before it moves again. Turning trailing on doesn’t lock in profit either. In the configuration guide’s own walk-through, the stop starts trailing 15 points below where the trade began.

So what does that cost you? Our earlier look at how auto-trail behaves covers who runs the trail and why TradingView isn’t the one watching it. This post does the arithmetic. It shows where the stop lands, how much it hands back per contract, and which settings quietly work against you.

Key Takeaways

• An auto trail stop moves in frequency-sized steps, so it can sit distance + frequency − 1 tick behind the best price: 14 ticks on a 10/5 setting.
• When trailing starts, the stop lands at trigger − distance, which can still be a loss.
• Tradovate’s servers run the trail, and an update_sl alert can wipe it out.

An auto trail stop is a stop-loss that stays put until a trade reaches a set profit, then moves toward price in fixed steps. Trail frequency is the size of each step: how far price has to move in your favor before the stop moves again. It’s a price distance, not a time interval.

What Happens Between the Alert and the First Stop Move?

Nothing trails at first. PickMyTrade turns the alert’s stop and target prices into distances and waits for the real fill. Then it rebuilds both orders from that fill and starts watching for the trigger. In its documented MNQ example, the entry fills 18.5 points away from the alert price, so every level moves with it.

Here’s that example one step at a time. A TradingView alert buys MNQ at 26,000 with a stop at 25,990, a target at 26,030 and trailing switched on. PickMyTrade keeps only the gaps, 10 points to the stop and 30 to the target. The trail itself is a 5-point trigger, a 2-point distance and a 1-point frequency.

The order fills at 26,018.50. PickMyTrade then places the working stop at 26,008.50 and the target at 26,048.50, the same 10 and 30 points measured from the fill. Price has to reach 26,023.50 before anything trails. At that moment the stop jumps to 26,021.50, and every further 1-point gain lifts it another point. Why rebuild from the fill at all? Slippage would otherwise eat the stop distance. Used as a literal price, the alert’s 25,990 would have left a 28.5-point stop under a 26,018.50 fill.

The strategy asked for 10.

PickMyTrade’s trailing SL from TradingView price guide says the trailing after the fill is handled entirely by Tradovate. Once the trade is live, the stop isn’t waiting for another alert or a bar close. It’s an order on Tradovate’s side, moved by Tradovate’s rules.

In short, PickMyTrade builds a trailing stop from the real fill price, not the alert price. It stores the alert’s stop and target as distances, rebuilds both orders from the fill, and hands the trailing to Tradovate. Nothing trails until price covers the full trigger distance measured from that fill.

Why Does an Auto Trail Stop Move in Steps Instead of Ticks?

Because the frequency sets the step. Tradovate has two trailing tools. A trailing stop order follows price tick for tick, while Auto Trail waits for a profit trigger and then moves the stop in frequency-sized jumps. PickMyTrade’s trigger, distance and frequency fields match Auto Trail’s three settings, so the steps come with them.

A trailing stop order is a stop that starts trailing the moment it’s placed and moves with every new favorable tick. Auto Trail works differently. When price reaches the trigger, the stop jumps to the trigger level minus the distance. After that it moves one step each time price gains another step. Between steps it doesn’t move at all, however long the market takes.

Take a long at 1,000 with a 990 stop, a 10-tick trigger, a 5-tick distance and a 2-tick frequency, where one tick is one point. At 1,010 the stop jumps to 1,005. At 1,012 it moves to 1,007, and at 1,014 to 1,009. At 1,013, it’s still sitting at 1,007. We found the same stepping in every trailing example PickMyTrade publishes, from its FAQ to its TradingView-price guide.

The chart runs the same logic on MNQ with PickMyTrade’s day-trading preset: a 15-tick trigger, 10-tick distance and 5-tick frequency. Price peaks at +29 ticks, one tick short of the next step, so the stop is still parked at +15. When the market turns, the trade exits at +15. So why did a 10-tick trail hand back 14 ticks? Because the peak landed between steps.

Why not set the frequency to one tick?

You can. A frequency equal to the contract’s tick size moves the stop on every favorable tick. That’s as close as Auto Trail gets to a plain trailing stop. PickMyTrade’s FAQ warns that very small values cause too many rapid updates, while large values mean fewer updates and less protection. Its own presets set it at half to two-thirds of the distance. Is a coarse frequency ever the better choice? Sometimes. A stop that moves on every tick also tightens on every tiny push, so a strategy that needs room to pull back can get stopped out of trades it would have held.

The frequency is a trade-off between protection and room. Choose it on purpose.

How Much Profit Can an Auto Trail Stop Give Back?

Up to the distance plus the frequency, minus one tick, measured from the best price. On the day-trading preset that’s 14 ticks: $7 on MNQ, $70 on NQ and $175 on ES per contract. The distance you type is the least the stop trails by, not the most.

Here’s why. Right after a step, the stop sits exactly one distance behind price. Price can then climb one tick short of a full step without moving it. Turn there, and the stop sits one distance plus one frequency, less a tick, below the best price.

We ran that formula across the three starting presets in PickMyTrade’s configuration guide. All values are ticks.

The pattern holds for any settings: when the frequency is half the distance, the stop can trail up to about 1.5 times as far as you asked. Across these three presets the real trail runs from 1.33 times the typed distance up to 1.47. That’s the number to plan around. Will a reversal wait for a convenient moment between steps? It won’t.

PickMyTrade’s advanced trading features guide works out the trailing buffer as distance × contracts. That figure is the gap right after a step. Between steps, add the frequency minus one tick, then multiply by the tick value and your size. On 3 ES contracts with the day-trading preset, the worst case is $525, not the $375 the distance alone suggests.

When the formula stops working

The give-back formula assumes price trades through every tick. After a news release or a market reopening, it often doesn’t. Price can jump straight past your stop with no tick in between for it to trigger on. The exit then depends on the next price that trades, not on your trail settings.

On a live account, exchange rules take over from there. CME Globex has no trailing stop order type, and its stop orders carry protection. A triggered stop fills only within a protection range around the trigger price, usually half of the product’s non-reviewable range. Any unfilled remainder rests in the book as a limit order. Our guide to stops that turn into stop-limits in a fast market walks through that case. Prop and evaluation accounts on Tradovate run on its simulator instead, which tries to match the real market but won’t fill identically.

Either way, treat the trail distance as protection for normal trading. A gap needs its own plan, such as smaller size into scheduled news.

Is Profit Locked the Moment Trailing Starts?

Only when the trigger is bigger than the distance, because at activation the stop lands at trigger minus distance from your entry. PickMyTrade’s FAQ example, a 15-point trigger with an 8-point distance, locks 7 points. Its configuration walk-through, a 5-point trigger with a 20-point distance, starts trailing 15 points below entry.

Does the unit matter? No. The same subtraction works in ticks, points or price, as long as both numbers use one unit. A 10-tick trigger with a 10-tick distance drops the stop exactly on your entry. Anything lower means the trail is already running while the trade can still lose money.

PickMyTrade’s suggested starting points all clear that bar. Scalping (a 5-tick trigger with a 3-tick distance) locks 2 ticks when it switches on, day trading (15 and 10) locks 5, and swing (50 and 30) locks 20. The trouble starts when a trader widens the distance for breathing room and leaves the trigger where it was. Nothing on screen warns you that “trailing” and “protected” just stopped meaning the same thing.

What if the first trailed stop is looser than your fixed stop?

It can happen on paper. Take a 10-point fixed stop, a 5-point trigger and a 20-point distance. When trailing switches on, the formula puts the new stop 15 points under entry, 5 points further away than the stop you started with. Tradovate defines the jump as the trigger level minus the distance, and we couldn’t find anything that says it refuses a jump in the losing direction.

Don’t find out with real money. At the very least, the first trailed stop should sit closer to entry than your fixed stop does. If “trailing” is supposed to mean “protected,” it should sit above entry.

Breakeven first, then the trail

A breakeven setting closes the gap between entry and the trigger, which is exactly where a wide trail leaves a trade exposed. PickMyTrade’s FAQ pairs breakeven: 20 with trail_trigger: 40, trail_stop: 15 and trail_freq: 5. The stop jumps to entry at 20 points of profit, sits there until 40, then trails from +25 and climbs 5 points at a time.

Tradovate’s own ATM strategies run the same order of events: the stop moves once when breakeven triggers, then starts trailing at the later trigger. The pairing suits prop accounts whose drawdown trails open profit. There, a trade that runs up and comes all the way back costs you twice, once in the balance and once in a higher drawdown floor. What protects the trade before the trail wakes up? Breakeven does.

Which JSON Fields Control an Auto Trail Stop?

Four fields do it. trail switches trailing on with a 1, trail_trigger sets the profit needed to start, trail_stop sets the distance and trail_freq sets the step. PickMyTrade’s FAQ reads all three values as points, so a 5-tick frequency on MNQ or ES is 1.25, the same value its own indicator template uses.

Here’s a trimmed alert built on the template’s numbers, sent for MNQ:

{
  "symbol": "MNQ",
  "date": "{{timenow}}",
  "data": "buy",
  "quantity": 2,
  "dollar_sl": 5,
  "dollar_tp": 10,
  "trail": 1,
  "trail_trigger": 5,
  "trail_stop": 3.75,
  "trail_freq": 1.25,
  "breakeven": 0,
  "update_sl": false,
  "token": "your_token_here",
  "account_id": "your_account_id"
}

What does that alert actually do? Read it as ticks and it’s easy to predict. The stop starts 20 ticks under the fill. Trailing switches on at +20 ticks and puts the stop at +5, so 5 ticks are locked. After that, the stop steps 5 ticks at a time and can sit up to 19 ticks behind the best price, which is $9.50 per MNQ contract.

“dollar” fields are price distances, not dollars

The field names mislead a lot of futures traders. PickMyTrade’s Point / Dollar type measures distance in price. Its own formula multiplies the value by the contract’s point value and your quantity, so 2 points on 10 NQ contracts is 2 × 20 × 10 = $400. That means "dollar_sl": 5 on NQ risks 5 index points, $100 a contract, not five dollars.

update_sl can erase the trail

PickMyTrade’s guide to updating SL and TP by alert warns that a trailing stop might get removed when an alert arrives with update_sl set to true. The update overwrites the stop with the exact price you send. It doesn’t apply point or dollar distances, and it skips orders that haven’t filled yet. If a position is trailing, let the trail own the stop.

Trail only the runner

In the multiple TP/SL format, each quantity group in advance_tp_sl carries its own trail fields and its own breakeven. That lets two contracts take fixed targets while a third keeps a wider target and a trail. For the full field list, see PickMyTrade’s TradingView JSON alert reference.

When the Trail Exits Before Your Strategy Does

TradingView doesn’t find out. The trail can flatten your Tradovate position while the strategy on your chart still shows an open trade. When that strategy exits later, the alert says sell rather than close. On PickMyTrade’s strategy template, with pyramid true and reverse_order_close false, a sell reaching a flat account reads as a new short.

Why does nothing look broken? Because every piece is doing its job. TradingView’s {{strategy.order.action}} placeholder only ever sends buy or sell, so an exit from a long is simply a sell. On a netted futures account, that sell closes the long when the long is still there. After the trail has already closed it, the same sell opens a short that nobody meant to take.

Reversal strategies get it worse. When a TradingView strategy flips from long to short, it sends one order sized to close the old position and open the new one. A 1-contract strategy sends sell 2. If the trail took you flat first, those 2 contracts all become a short, double the size the strategy intended.

Would PickMyTrade read that late alert as a close instead? Its docs don’t say. What’s above is what the documented pyramid and reverse_order_close rules imply, so treat it as a case to rule out rather than a certainty.

There are two clean ways out, and both come down to giving exits a single owner. The first is to let the broker own them: give the strategy’s exit orders an alert_message that sends "data": "close" through the {{strategy.order.alert_message}} placeholder, because PickMyTrade’s close action does nothing when no position is open. The second is to send the position rather than the action, using the {{strategy.market_position}} placeholder that PickMyTrade’s multiple TP/SL guide documents. It arrives as long, short or flat and tells PickMyTrade where the position should end up.

Either way, test the exact sequence on a demo account: entry, trail exit, then the strategy’s own exit a few bars later. It’s the cheapest way to see the problem before a funded account does.

Why Did Five Accounts Exit at Five Different Prices?

Each account runs its own stop from its own fill. PickMyTrade rebuilds the stop, target and trigger from every account’s real fill price, and stop orders on separate demo or funded accounts can also fill a tick or two apart.

One tick of difference at entry shifts that account’s whole trail ladder by one tick.

Prop firm and evaluation accounts on Tradovate always run in simulation mode, and each account keeps its own place in the simulated queue. So a multiple_accounts alert can fill account one at 26,018.50 and account two at 26,018.75. Account two’s trigger, every step and its final stop all sit a quarter point higher. On a sharp reversal, one account can be stopped out while another stays open for a moment. Which one is right? Both are.

PickMyTrade’s sync notice guide covers exactly this and treats a 1 to 2 tick gap and a few seconds between stop fills as normal. Large price gaps, missing orders or a mismatch that won’t clear are the cases worth chasing. On a funded account, the prop firm has to open that investigation, because Tradovate doesn’t handle trade disputes for prop and evaluation accounts.

Two practical notes for anyone copying one strategy across accounts. First, the trail only reaches other accounts through the alert itself. PickMyTrade’s manual TradingView-to-Tradovate Trade Copier doesn’t copy trailing stop orders or breakeven orders. Second, the give-back math applies per account. Five accounts with 2 MNQ contracts each on the day-trading preset can each hand back $14 on one reversal. Every account counts that against its own trailing drawdown.

Should the Trail Live in Pine Script or at the Broker?

For most automated futures trades, at the broker. A Pine Script trail is a simulated order: when it fills, TradingView fires an alert, and your real exit only starts once that webhook reaches PickMyTrade. A broker-side auto trail is already a working stop at Tradovate. Its worst case is a number you can work out before the trade.

A Pine Script trailing stop is a trailing exit that TradingView’s broker emulator simulates from strategy.exit() settings such as trail_points and trail_offset. Once active, it follows the market by the offset every time the trade makes a new high, with no frequency steps. In live trading it can fill partway through a bar, and TradingView fires the order-fill alert right away.

It’s still a simulated fill, though. Tradovate never held that stop, so the real exit is a market order sent after the alert arrives, filled at whatever price is available by then. A trail you code by hand, such as an ATR trail, usually recalculates only when each bar closes, which is slower again.

Backtests add a second gap. On historical bars, TradingView assumes a path through each bar’s open, high, low and close. A trailing stop’s backtest fills are estimates, and they can repaint once the strategy runs live. The Bar Magnifier option on Premium and Ultimate plans uses lower-timeframe bars to narrow that gap.

A broker-side trail avoids both problems. It keeps working when TradingView, your browser or your computer is off, because the stop and its steps live on Tradovate’s side. The trade-off is that your backtest can’t see the frequency steps, so live exits will usually trail further behind the peak than a strategy.exit() backtest suggests.

Can you use both? Yes, if only one of them sends exit orders: a Pine trail for analysis, a broker trail for execution. If your strategy.exit() trail settings throw errors, our Pine Script error reference for trail_offset covers the usual ones. Our comparison of paper and live bot execution explains why simulated fills rarely match real ones.

Auto Trail Stop Futures Settings That Keep the Math on Your Side

Six checks catch nearly every surprise in this post. Each one takes a minute with a calculator. The first one alone would have caught the configuration guide’s 5-point trigger with a 20-point distance.

We analyzed every trailing example PickMyTrade publishes to build those checks, and the demo rehearsal is the one we’d never skip. PickMyTrade connects to Tradovate demo accounts the same way it connects to live ones. Its 5-day free trial needs no credit card and is long enough to watch a full trail play out. Plans and trial details are on the PickMyTrade pricing page.

Connecting a funded account? Read who runs PickMyTrade, check the supported prop firms list, or contact the PickMyTrade team about your settings first.

Frequently Asked Questions

The Short Version

An auto trail stop does three things in order. It waits for the trigger, jumps to the trigger minus the distance, then climbs in frequency-sized steps. Each stage hides a trap: a trigger that starts trailing below entry, steps that trail up to 1.5 times the distance you typed, and a stray update_sl or bare sell that undoes the setup.

None of that makes auto trail a bad tool. It makes it one to price out on paper first: trigger minus distance for what’s locked, distance plus frequency minus a tick for what can be given back, then tick value times size.

Building the alert from scratch? Start with our TradingView to Tradovate webhook guide. Then see how to route one TradingView alert to multiple prop firm accounts before a trail runs on more than one.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: Automate TradingView Indicators with Tradovate Using PickMyTrade