What does & do in an Autoview alert?

It splits one command into sections. What happens next depends on the exchange. Tradovate turns each section into a bracket on the entry. OANDA, Capital.com and Bitfinex place each section as its own order. Charles Schwab adds each section as another leg of the same order. Most other venues do not read the sections at all and run the line as one command.

Can I scale out with two take-profits using &?

On Tradovate, yes: give each section its own q= and tp=, and each becomes a bracket on the entry. On OANDA, Capital.com and Bitfinex each section is a separate order, so two sections open two positions rather than one entry with two exits. On venues that do not read &, only the first tp= on the line is used.

Why did my & alert place one order with the wrong size?

On a venue that does not read &, the whole line is one command and the first value of a repeated parameter wins, so a q= in a later section is ignored. Also put a space on each side of &: a value written right against the & is not read.

The & separator by exchange

Autoview · Guide · Updated October 20, 2026

An & in an Autoview command splits it into sections. The text before the first & is the base, and each section after it adds its own parameters on top of the base. People reach for it to attach a stop and a target to an entry, or to scale out with two targets in one alert.

The catch is that each exchange treats the sections differently. On one venue they become brackets on a single entry. On another each section is a separate order. On most venues the sections are not read at all, and the whole line runs as one command. This page lists which is which. It comes from the Autoview integrations code that runs on our servers today, read venue by venue.

One rule for every venue: spaces around &

Write b=buy q=1 & sl=1% tp=2%, with a space on each side of the &. A value written right against it, as in q=1&sl=1%, is not read, so the order does not get the size you wrote.

Tradovate: each section is a bracket on the entry

Tradovate is the venue where & does what most people expect. The base is the entry, and each section becomes one bracket attached to it, with its own q=, sl= and tp= (or the fixed fsl= and ftp=). Autoview sends the entry and every bracket to Tradovate as one order strategy. Auto-trail settings (atf=, atx=, atsl=) also go inside a section.

So b=buy t=market q=2 & q=1 sl=10 tp=10 & q=1 sl=10 tp=20 buys two contracts and gives each one its own take profit, both behind the same ten-point stop. Add oco=1 and Autoview places an OCO exit pair instead of a bracketed entry. The Tradovate command reference has the full parameter list and lines confirmed on Simulation.

OANDA, Capital.com and Bitfinex: each section is its own order

These three have no order type that takes several linked legs, so Autoview places each section as a separate order. The base text is a template only and never places an order of its own. Each section takes the base, applies its own parameters, and goes out by itself.

The common mistake: b=buy q=1000 & sl=1% & tp=2% is two sections, so it opens two full-size positions, one with only a stop and one with only a target. Put both in the same section: b=buy q=1000 & sl=1% tp=2%.
OANDA: the stop, target, trailing stop and guaranteed stop in a section attach to that order when it fills. They also attach on a plain command with no &. On a c=position alert an & does not close anything: Autoview sets or moves the stop, target, trailing stop and guaranteed stop on each open trade instead. The OANDA command reference covers units and prices.
Capital.com: the sections are sent one after another. A partial close never fans out, even when the line has an & in it. The Capital.com command reference walks through scaling out.
Bitfinex: all sections go to Bitfinex in one request, up to 75 orders. Bitfinex works through them one by one, so one can fail while the others go live. Autoview reports how many failed.

Charles Schwab: each section is another leg of one order

On Schwab each section is added as a further leg of the same order, with its own side and size. A leg carries no price of its own, so a section with sl= or tp= does not become a stop or a target. The one-cancels-the-other line in the code is switched off, so treat the result as extra legs, not a bracket, and check your Schwab order log the first few times. A trailing stop together with & is refused with an error.

Crypto.com and Binance.US: not ones to rely on

Crypto.com reads the sections only when the line also has oco=1, and then sends them as an OCO order list, which Crypto.com rejects. Without oco=1 the sections are not read. See the Crypto.com command reference.
Binance.US sends the sections to its OCO endpoint, but the request carries the main order instead of the legs you wrote. Until this is fixed, place the stop and the target as separate orders. The OCO orders guide has the detail.

Venues that do not read the sections

Alpaca
Binance, Binance Futures and Binance Delivery
Bitget, Bitget Mix and Bitget Mix Copy
Bybit and Bybit Copy
Coinbase Advanced
Deribit
Gate.io and Gate.io Futures
Gemini
HTX
HyperLiquid
Kraken and Kraken Futures
Kucoin, Kucoin Futures and Kucoin Futures Copy
OKX
TradeStation

On these venues there is no error. Autoview reads the whole line, sections included, as one command, and when a parameter appears more than once the first value wins. So b=buy q=1 & sl=1% tp=2% works the same as b=buy q=1 sl=1% tp=2%, and whether the stop and target attach depends on that venue's own support for sl= and tp=.

The trap is scaling out. Here b=buy q=2 & q=1 tp=1% & q=1 tp=2% does not make two exits. It runs as b=buy q=2 tp=1%: the base size and the first target, with the second target dropped. To scale out on these venues, send each exit as its own alert. The stop loss, take profit and trailing stop guide covers the syntax.

Test it once before you rely on it

Add d=1 to the alert first. Autoview writes what it would send to your log and places nothing, so you can count the orders and check each size, stop and target. When the log looks right, take d=1 off. The log guide shows where to look. The sibling pages cover the same question for trailing stops, reduce-only orders and OCO orders.

Open the command reference