Common strategies with Autoview

Autoview · Guide · Updated September 30, 2026

This page is about process. It takes strategy types traders already know, such as dollar-cost averaging, a moving-average crossover, or a breakout entry, and shows how each one runs through Autoview: where the signal comes from, what command it sends, and which account you rehearse it on first. It says nothing about whether any of them will make money. That part is yours to judge.

On this page

The process, for any strategy

Autoview doesn't run strategies. It places an order when a command arrives at your webhook. So every strategy on this page splits the same way: the decision lives in whatever sends the signal, and the order lives in the command.

  1. A signal source. Something decides when to act: a TradingView alert, a Pine Script strategy, a cron job, your own script, or a workflow tool. If it can send a webhook, it can drive Autoview. See send custom webhooks for anything that isn't TradingView, and automate TradingView alerts for the TradingView route.
  2. A webhook. The signal arrives at your Autoview webhook, which is linked to one exchange connection.
  3. A command. The text of the signal is an Autoview command, a line of key=value tokens like b=buy t=market q=2%. That line is where the strategy becomes an order. The command reference covers every parameter.
  4. A demo account first. Point the webhook at a demo or testnet connection, add d=1 to see what Autoview would place without placing it, then let a few real demo orders land before anything touches money. OANDA Practice and Bybit testnet are two free options; test and debug your setup covers reading the log.

If you bought a strategy rather than wrote one, the same process applies. Automate a purchased trading strategy lists what to check before you pay.

Strategy types

In rough order of how cleanly Autoview's commands express them. Only the first has its own step-by-step guide so far. The rest are a short description and the parameters involved, with links to the existing guides that cover those parameters. Parameter support varies by exchange, so check your venue's own command reference and dry-run with d=1 before you rely on any of it.

Dollar-cost averaging (DCA)

Buy a fixed amount on a fixed schedule, whatever the price is that day. A recurring buy needs a scheduler. A timer sends one market buy with a set size (b=buy t=market q=), and Autoview places the order each time the command arrives.

DCA with Autoview: a recurring buy on a schedule is the full guide, rehearsed on OANDA Practice. For the price-based kind, which spreads one entry across several lower prices, see the Bybit perpetual DCA entry with a trailing stop.

Moving-average crossover

Enter when a fast average crosses above a slow one, and exit when it crosses back. Autoview doesn't calculate averages. The crossover is detected in the signal source, which sends an entry command (b=long with a q= size) on the cross up and a close (c=position) on the cross down. The Pine Script strategy alerts guide has a crossover script that attaches those commands to its orders. No dedicated guide for this one yet.

Breakout entry

Enter only if price trades through a level, using a resting entry stop. Add a trigger price to the order, fpx= for an absolute level or px= for an offset, and the side stays as you wrote it. Choosing the level happens in the signal source. If the breakout never comes, a separate command cancels the resting order (c=order). The Bybit command reference and the OANDA command reference both show the entry-stop shape. No dedicated guide for this one yet.

Trailing-stop exit

Exit with a stop that follows price and closes the position after a set pullback. The parameters are ts= for the trailing distance, with tsx= as an optional activation price on venues that support it. Whether a venue attaches a native trailing stop varies, and on OANDA it only attaches inside the & advanced-syntax bracket. Stop loss, take profit, and trailing stop covers this venue by venue.

Bracket: a stop-loss and take-profit on every entry

Every entry goes out with a stop and a target attached, and whichever the market reaches first closes the position. The parameters are sl= and tp= as distances, or fsl= and ftp= as absolute prices. This is covered in the same stop loss, take profit, and trailing stop guide, including the OANDA & rule and how the order side differs between venues.

Scaling in (pyramiding)

Add to a position in steps as further signals fire, then close all of it on the exit signal. Each add is its own entry command with a q= size, and the exit is c=position, or c=position q=50% to close half. One limit to know: q=10% on an entry always means 10% of your balance, never 10% of the position you already hold, and Autoview keeps no count of how many adds have fired. The signal source has to track that. The command reference explains sizing on entries and closes.

Grid

A grid rests buy and sell limit orders at fixed spacing and replaces each one as it fills. Autoview can place the ladder, several t=limit lines with fp= prices in one alert, and clear it with c=order. A running grid also needs something that watches for fills and sends the replacement order. That job belongs to your signal source or script: when a level fills, it sends the next limit command, and Autoview places it. The Bybit DCA entry template shows the one-alert limit ladder that starts a grid.

Rebalancing

Hold several assets at target weights and trade back to those targets on a schedule. Rebalancing needs a script that knows your target weights and your current holdings. That script works out each buy or sell and sends it as an ordinary command, the same way the DCA schedule does. Autoview only places the resulting orders.

What Autoview does and doesn't do here

Autoview executes. It reads a command and places the order it describes on the exchange you connected. It doesn't generate signals, calculate indicators, pick levels, hold a strategy's state between alerts, or say which strategy suits you. None of the strategy types above is a recommendation. They are common shapes people automate, laid out so you can see which parts the signal source owns and which parts the command owns.

Trading carries risk of loss, and you are responsible for the strategy you automate. See our disclosures.

Start with DCA