I purchased a trading strategy, can I automate it with Autoview?
Short answer: yes, if it can produce an alert. Autoview doesn't care whether you wrote the strategy yourself or paid someone else for it. It reads whatever signal the strategy fires and turns it into a real order on your connected exchange. The strategy is your side of the deal; Autoview is the execution.
What Autoview actually needs from you
Autoview is a bridge, not a strategy provider. It doesn't generate signals, judge whether a strategy is any good, or promise a result. What it needs is an alert it can read: a symbol, a side, a quantity, and an order type, at minimum. Where that alert comes from is up to you.
Most purchased strategies land in one of two forms:
- A TradingView Pine Script strategy. If the strategy is a
strategy()script running on TradingView, its own alert placeholders ({{strategy.order.action}},{{strategy.order.contracts}}, and the rest) can fill in most of an Autoview command automatically. The Pine Script strategy alerts guide covers exactly this. - A manual rule set, indicator, or PDF. No script, no auto-fill. You write the alert's command by hand from the rules the strategy gives you, the same way you would for any TradingView alert. Start with the automate TradingView alerts guide, which takes an alert from firing to a live order end to end.
Either way, the full parameter list, including stop loss, take profit, and trailing stops, lives in the command reference. This page won't repeat it; that's the page that owns it.
Before you pay: a checklist
"Any strategy that can produce an alert" is true, but it hides a handful of things that decide whether a specific purchased strategy actually can, cleanly, before Autoview enters the picture at all. Ask the seller these before you buy, not after:
- Source visibility. Is the script open, or a locked/invite-only Pine script? A locked script can still fire an alert, but you can't inspect what it's actually doing or verify placeholders yourself.
- Alert type. Does it fire from a
strategy()backtest engine (auto-fill placeholders available) or a plainindicator()/alertcondition()(you write the whole message by hand)? These need different setup. - Placeholder availability. If it's a locked strategy script, confirm the seller's alert message actually exposes
{{strategy.order.action}}and the other placeholders you need. A locked script can restrict what its own alert message is allowed to contain. - Repainting policy. Does the seller disclose whether the strategy repaints (its historical signals shift after the fact)? A repainting strategy's backtest results and its live alerts can disagree, which matters more once real orders are attached to it.
- Symbol mapping. Does the strategy trade the exact symbol format your exchange expects, or will you need to translate a chart symbol into your venue's own naming before Autoview can route it?
- License and terms. Does the seller's license actually permit automating the strategy's output, including sending its alert to a third-party execution tool? Some strategy marketplaces restrict redistribution or automation of their signals; read the terms, don't assume.
- A test account first. Can you point the strategy's alert at a demo or testnet connection before any real money is involved, the same
d=1and paper-trading discipline this page recommends below regardless of where the strategy came from? - Maximum size. Does the strategy's own documentation specify a position size or risk-per-trade assumption? If so, your Autoview command's
q=needs to match that assumption, not a number you picked separately. - A real sample alert. Ask the seller for an actual alert message their strategy fires, not a description of one. A sample captured from the real script is the only way to confirm the fields, formatting, and placeholders line up with what Autoview's command syntax expects before you've paid and started troubleshooting live.
- Marketplace status. TradingView's Terms of Use (section 23) now say: "Scripts available for Commercial Use are only permitted to be distributed via the Marketplace." Its September 30 announcement says selling access to an invite-only script "will no longer be permitted starting November 1, 2026," and that customers who paid before that date "can keep using it for the period already purchased, including lifetime access." Ask whether the seller is on the TradingView Marketplace or has a plan to move there.
If you already automate an invite-only script, invite-only scripts after November 1 covers what to ask your seller and how to test a new signal source.
Two ways to connect it
Autoview runs on two surfaces, and either one can automate a purchased strategy:
- The webhook platform. Runs on Autoview's servers around the clock and accepts a POST from anything that can send one, TradingView included. This is the current, primary way to run Autoview.
- The Chrome extension. The older, browser-local surface, wired directly to TradingView alerts. It only trades while your machine and Chrome are on, and it keeps your keys in the browser rather than on a server.
The what is Autoview guide lays both out side by side if you're deciding which fits your setup.
Before you trust it with real money
Whatever the strategy, connect your exchange with an API key scoped to trading and reading only, never withdrawal; see are my API keys safe? for why that matters. Then dry-run the command with d=1 before you go live, exactly as you would for any alert, purchased strategy or not. That step catches a wrong symbol or a typo'd parameter before it costs you anything.
A note on what Autoview is. Autoview is an execution tool, not a trading or investment advisor. It places the orders a strategy's alerts tell it to, whether you wrote that strategy or bought it. It doesn't vet strategies, generate signals, or make any claim about the results you'll get. Trading carries risk of loss, and you're responsible for the strategy you choose to automate. See our disclosures.