TradingView Trade Copier: Multi-Account Routing and Risk Checks
A TradingView trade copier can route one alert to several accounts or copy trades from a master account to followers. Those are different architectures. Before connecting accounts, identify which events are copied, where execution runs, and how each account handles size, stops, and failures.
Choose the copying model
An alert fan-out service sends instructions to selected accounts. A master/follower copier observes orders or positions in one account and mirrors supported changes. A product may combine these models, but an arbitrary TradingView JSON message does not work with every service.
For example, PickMyTrade documents multi-account alert routing with account-specific quantity and risk settings. That is evidence of a documented workflow, not a measured execution-speed endorsement or support for every broker.
Read the exact provider schema and account requirements. A field named risk may represent a percentage, lots, or a receiver-specific setting. No generic example can safely establish those units without the provider's definition.
Cloud and local are operating choices
| Responsibility | Hosted receiver | Local or VPS receiver |
|---|---|---|
| Availability | Provider infrastructure and broker integration | Your host, terminal, network, and any upstream relay |
| Access to data | Depends on permissions and service design | Still depends on broker, relay, licensing, and logging connections |
| Maintenance | Provider updates plus your configuration | Your updates, restarts, and monitoring |
| Cost | Check subscription and account limits | Check license, hosting, and maintenance costs |
“Local” does not mean no information leaves the computer, no third-party dependency, or automatic permission under a funded-account agreement. “Cloud” does not establish a rule violation by itself. Account ownership, permitted strategies, copying restrictions, and each firm's current terms determine eligibility.
Map each account explicitly
Confirm symbol names, tick/contract value, minimum size, size increments, account currency, and whether the account uses netting or hedging. A fixed lot ratio can produce different risk across instruments or brokers.
Define what happens when one follower rejects an order while the others accept it. Specify how partial fills, manual closes, partial exits, and reconnects are reconciled. A copier cannot guarantee identical fills on independent accounts.
Validate before scaling
Start with one demo follower. Inspect the alert log, receiver event, requested order, broker acknowledgement, resulting position, and protective orders. Then test duplicate events, lost connections, a restart with an existing position, rejected stops, and a close instruction after a missed entry.
TradingView's webhook documentation explains delivery requirements. Receipt is only one step. Keep credentials out of messages and use the receiver's supported authentication.
When measuring latency, distinguish alert creation, receiver arrival, order submission, and broker fill. A provider's internal routing number is not end-to-end execution latency. There are no verified 1–3 ms or sub-100 ms live tests supporting the old rankings on this page.
Monitor account divergence
Set per-account exposure limits and an emergency stop procedure. Regularly compare actual positions with intended positions before sending corrective orders. Check existing state before retrying an uncertain result.
Pineify can help prepare Pine scripts and analysis workflows, but that does not make it a trade copier or guarantee server-free operation, missed-signal prevention, or funded-account compliance. Copying multiplies exposure to the same strategy; it does not diversify or improve that strategy's expected return.
