It has one alert, not five accounts
An alert is a message, not a router. It has no concept of your evaluation account being smaller than your funded one, because it has never seen either.
Sizing happens after the alertTradingView
One TradingView alert. Every account you own.
TradingView is where the decision gets made. It is not where the order gets placed, and it does not know how many accounts you are running. Quanify is the part in between: your alert arrives once and lands on every account, each at its own size.
Two things people mean by a TradingView copier
Both are supported and they are worth separating, because the setup is different.
Alert to accounts. A PineScript strategy fires an alert. That alert becomes real orders across every account you have attached, sized per account. No one is at the desk. This is the automation path.
Chart to accounts. You trade manually from the TradingView chart into your broker, and your other accounts mirror the fill. TradingView is your order ticket; the copier follows what your broker reports. This is the Copy Trader path.
The difference is where the signal comes from — a rule you wrote, or your own hand. Everything downstream of that is identical.
Alert → accountsPineScript fires a webhook. Quanify sizes and places an order on every attached account.Auto
Chart → accountsYou trade the leader account by hand. The broker's fill mirrors to the others.Manual
What is sharedThe same broker connections, the same per-account sizing, the same risk caps.
What you chooseWhether a rule or a person decides the trade. Accounts move between the two without re-onboarding.
The alert is a webhook, and that is all it is
Each strategy in Quanify gets its own webhook URL. You paste it into the TradingView alert's webhook field and put a small JSON body in the message. There is no SDK, no plugin, and nothing to install on the chart.
TradingView's own alert placeholders are enough — the strategy's action, the ticker, and the contract count come straight from the alert. The Webhook Setup panel builds the exact body for you, already matching that strategy's settings, so it is a copy and a paste rather than a format to learn.
{
"action": "{{strategy.order.action}}",
"ticker": "{{ticker}}",
"contracts": "{{strategy.order.contracts}}",
"price": "{{strategy.order.price}}",
"market_position": "{{strategy.market_position}}"
}The token in the URL is the credential, so treat it like a password: not in a public chart, not in a screenshot, not in a shared repository. If you want a second factor, set a webhook password on the strategy and include it in the body.
Why the copy happens server-side
TradingView fires the alert from its own servers, so the alert itself does not need your machine. The part that usually does is whatever receives it — a desktop bridge, a local script, a bot on a VPS.
Quanify receives the webhook and holds every broker connection itself. Nothing is installed, nothing has to stay awake, and the alert that fires at 3am reaches your accounts whether or not your laptop is open.
That also removes an entire class of failure that is hard to notice: a bridge that silently stops does not tell you, and you find out from a position you did not expect — or from one you expected and do not have.
- AlertTradingView posts to your strategy's webhook URL from its own servers.
- CheckThe token and optional password are verified, then that strategy's own settings are applied — fixed contract size, and the guard against adding to an open position.
- SizeEach attached account applies its own whole-number multiplier, or the strategy's fixed contract size if you set one.
- PlaceOne order per account, on that account's own direct broker connection.
Quanify never closes a position on your behalf. Turning a strategy off stops new orders; it does not flatten you.
What TradingView cannot do on its own
Worth being clear about the division of labour, because it explains why this piece exists at all.
It does not know your fills
TradingView knows what the strategy intended. Your broker knows what actually happened, including partials and rejections. The copier works from the second one.
Execution events, not chart stateTry it without pointing it at money
Attach the strategy to a simulated or evaluation account first and let it run through real sessions. Every part of the configuration — the webhook, the sizing, the caps, the alerts — is identical when you later attach a funded account.
Quanify also has built-in paper accounts that fill from your strategy's own signals, with commission and slippage you set. They are useful for watching how a strategy behaves across a week without spending an evaluation to find out.
Common questions
Can TradingView copy trades to multiple accounts?
Not by itself — a TradingView alert is a message, not a router, and it has no knowledge of your accounts. Quanify receives the alert and places one sized order per account, so a single alert becomes trades on every account you have attached.
How do I connect TradingView to my broker?
Create a strategy in Quanify, copy its webhook URL into the TradingView alert's webhook field, and paste the JSON body the Webhook Setup panel generates. Quanify holds the broker connection, so there is nothing to install and no bridge to keep running.
Does this work with PineScript strategies and indicators?
Anything in TradingView that can fire an alert with a webhook can drive it, which includes strategies and indicators. The body needs to carry the action and the contract count; TradingView's own placeholders supply both.
Do I need a VPS to run TradingView alerts to my broker?
No. TradingView fires the alert from its servers and Quanify receives it on its own, so there is no machine of yours in the path. Setups that use a desktop bridge do generally need a VPS.
What happens if TradingView sends the same alert twice?
Duplicate protection is applied per execution inside a 60-second window per account, so a repeat lands once. Partial fills are handled separately and are never mistaken for duplicates, because the de-duplication is keyed on the execution rather than the order.
Can I trade manually on TradingView and still copy to my other accounts?
Yes. Trade the leader account however you like — TradingView, the broker's own platform, a phone. The copier works from your broker's execution report, so it does not care which front end placed the order.
More on trade copiers by platform
How to copy trade on Tradovate.Set one Tradovate account as the leader and have your others follow, each at its own size. What to do, in order, and how to verify it before it matters.Copy your NinjaTrader fills across every account you run.Copy trades across your NinjaTrader accounts with per-account sizing and whole-number multipliers. Cloud-side, no add-on to install, nothing to keep running.A trade copier on Rithmic rails.Copy trades across Rithmic accounts with per-account sizing and loss caps. What Rithmic is, why prop firms use it, and how copying works on it.Run more than one TopstepX account without trading them twice.A trade copier for TopstepX accounts with per-account sizing, per-account daily loss caps and an ownership gate on every fill. No VPS, nothing to install.Tradovate is the one where this works cleanly.Copy trading on Tradovate, where every funded sub-account under one login is addressable on its own. Per-account sizing, per-account caps, nothing installed.A trade copier built directly on Tradovate.Copy trades across every Tradovate account you own, scaled per account. Direct API, no bridge, no VPS. Built for funded and personal side by side.
Start on a simulated account.
Connect a sim or evaluation account and run the whole product against it before you point anything at live money. Nothing about the setup changes when you do.