tradingview tutorial execution

How to copy trade on TradingView (it doesn't work the way you think)

TradingView has no built-in copy trading. Here's how to copy your strategy trades to your broker using webhooks and a bridge like FillEdge.

Jonathan FillEdge 11 min read
How to copy trade on TradingView (it doesn't work the way you think) — FillEdge
In this article
  1. TradingView doesn't have a copy trading button
  2. How copy trading on TradingView actually works
  3. What breaks when you copy trades across accounts
  4. Copying trades to multiple broker accounts at once
  5. How to copy trade on TradingView with FillEdge
  6. Copy trading across prop firm accounts
  7. What you need before you start
  8. FAQ

There's no copy trading button on TradingView. Search the menus, dig through settings, ask support. It doesn't exist. TradingView is a charting and strategy platform, not an execution platform, and it has never shipped a native copy trading feature.

That catches most traders off guard. You've got a strategy running on TradingView, it's producing entries and exits, and you want those trades to land on your broker account (or five broker accounts) automatically. Reasonable expectation. But TradingView won't do that part for you, no matter which plan you're on.

The good news: TradingView has something better than a copy button. It has webhooks. And webhooks, paired with a bridge service, give you more control over how your trades copy than any built-in feature would. You get to decide which accounts receive the signal, at what lot size, with what risk rules, independently per destination.

This article covers the actual mechanism for copying trades from TradingView to a live broker account, what goes wrong when you try it, and how to set it up so it holds together across multiple accounts without constant babysitting.

TradingView doesn't have a copy trading button

Worth being specific about what TradingView can and can't do here, because the confusion runs deep.

A handful of brokers (Interactive Brokers, for example) have native integrations inside TradingView's trading panel. If your broker supports it, you can trade directly through TradingView by clicking buy and having the order go to your account. That's direct execution, not copy trading.

You can also share strategies publicly on TradingView. Other people can view your chart, read your Pine Script, even get notifications when you post ideas. But none of that copies a trade to anyone's broker account. It's social, not executable.

Copy trading means something specific: one signal fires, and real trades open on one or more broker accounts, sized correctly, with the right stop loss, without anyone clicking anything. TradingView's architecture wasn't designed for that. Its architecture was designed for something else (charting, scripting, alerting), and it turns out that "something else" is actually a better foundation for copy trading than a built-in button would be.

The reason is webhooks. When your TradingView strategy generates a signal, you can configure an alert that fires an HTTP request to any URL you specify. That request carries the trade data: symbol, direction, size, stop loss, take profit. A bridge service receives it and executes the trade on your broker.

How copy trading on TradingView actually works

The pipeline has four stages. Each one is a different system, and each one can break independently.

Stage 1. Your Pine Script strategy detects a setup and calls strategy.entry() or strategy.close(). This happens inside TradingView's servers. No trade has been placed yet.

Stage 2. TradingView fires the alert you configured. If you set up a webhook alert on TradingView, the alert sends an HTTP POST request to a URL you specified, carrying whatever you put in the "alert message" field. That message tells the bridge what trade to open.

Stage 3. The bridge service receives the webhook, parses the message, validates it, and routes it to the correct broker account. This is where lot sizing, account selection, and risk checks happen.

Stage 4. An Expert Advisor (or API connection, depending on your broker) picks up the instruction from the bridge and places the order. Your broker fills it. The full trip usually takes 200-400ms.

One prerequisite most people miss: webhooks require a paid TradingView plan. The free tier doesn't support them. You need Essential ($14.95/mo) at minimum. Without it, the entire pipeline stops at Stage 2.

The alert message itself is just a text string. Something like: buy,EURUSD,0.5,sl=1.0850,tp=1.0950,account=MyFTMO. The format depends entirely on which bridge you're using, and a single misplaced comma will kill the trade silently. Most bridge services provide a template builder that generates the correct message for you, so you rarely write it from scratch.

What breaks when you copy trades across accounts

The webhook pipeline works 95% of the time. The other 5% is where money disappears. And all of this assumes your strategy signals are valid to begin with. If your indicators aren't producing valid signals, no amount of copy trading infrastructure will save you.

Ghost positions are the most common problem. Your Pine Script calls strategy.entry() the moment it detects a setup, but the underlying order hasn't filled yet. TradingView fires the alert anyway. If the fill never comes (market closed, requote, insufficient margin), you end up with a position on your broker account that the strategy never intended. Multiply that across five accounts, and you've got five phantom trades.

Duplicate signals happen more than you'd expect. TradingView can fire the same alert twice during a single bar under certain conditions, especially when a strategy re-evaluates mid-bar. A naive bridge passes both through. Now you're holding double the position you wanted on every destination account.

Out-of-order reversals are the sneaky one. Your strategy says "close the long, open a short." Those are two separate HTTP requests with no ordering guarantee. Sometimes the "open short" arrives at the bridge before the "close long." The bridge processes them in arrival order, opens the short first, and now you're long and short simultaneously. The close hits the wrong position. You wake up facing the wrong direction on XAUUSD.

Stop-loss drift is quieter but compounds over time. Your strategy calculates SL at 1.0837. By the time the order reaches the broker, 200-400ms later, the price has moved. The broker fills the entry at a different price, but the SL instruction still carries the original number. Now your stop is tighter or wider than intended by a few points. Across hundreds of trades, that drift reshapes your risk profile in ways your backtest never predicted.

These four failure modes are worth asking about when comparing copiers for their TradingView setup. If the answer is "we just forward the webhook," you're on your own when something arrives twice or out of order.

Copying trades to multiple broker accounts at once

Most traders searching for copy trading on TradingView aren't trying to follow someone else. They want their own strategy hitting multiple accounts simultaneously: a personal account, two prop firm accounts in different phases, maybe a demo account for testing.

The naive approach is to duplicate the alert in TradingView. Create the same alert five times, each pointing at a different webhook URL. This works until you change the strategy. Now you're updating five alerts. Miss one, and that account drifts out of sync while the other four keep trading the updated version. You won't notice for days.

A better approach is a single alert that fans out inside the bridge. One webhook fires, the bridge routes it to every account on the route, with per-account lot sizing. Account A gets 1.0 lots. Account B gets 0.3 lots because it's a smaller funded account. Account C gets 2.0 lots.

The fan-out has to be independent. If Account B hits a risk limit and the trade gets blocked there, Accounts A and C should still execute. A bridge that treats fan-out as atomic (all-or-nothing) means that a single blocked account kills the trade everywhere. That's not copy trading. That's a single point of failure with extra steps.

Each fork also needs its own reconciliation. The fill on Account A might differ from Account C (different brokers, different spreads, different slippage). Anyone automating a TradingView strategy across multiple destinations needs per-account confirmation that each trade actually matched what the strategy intended.

How to copy trade on TradingView with FillEdge

FillEdge is a webhook bridge built specifically for this pipeline. You sign up, get a single webhook URL, and point every TradingView strategy at it. Routing, sizing, and risk checks all happen inside FillEdge, so TradingView stays focused on what it's good at: charting and generating signals.

The Signal Multiplier handles copy trading across accounts. You configure it once: this strategy goes to Account A at 1.0x size, Account B at 0.5x size, Account C at 2.0x size. Every signal fans out to every destination independently. If one account blocks the trade (risk limit, guardrail, margin), the others still execute.

Each fork gets its own reconciliation. FillEdge compares what TradingView sent against what actually happened on each broker account, and every trade gets a status badge. Signals where intent and fill agree carry ✓MATCHED. Ghost positions intercepted before reaching the broker show 👻CAUGHT. Duplicates that got blocked show 🛡️BLOCKED. Reversal signals that arrived out of order and were corrected carry 🔀REORDERED. Stale signals discarded instead of executed late show 💀EXPIRED. And when your stop loss lands at the exact price your strategy calculated, even after entry slippage, the trade carries 🎯LOCKED.

You don't need to write the alert message by hand. FillEdge's dashboard has a template builder: pick the strategy name, pick the destination accounts, pick the command (buy, sell, close, reverse), and it generates the message text. Paste it into TradingView, done.

Setup takes about fifteen minutes from signup to first test signal. The automation features TradingView provides (alerts, webhooks, Pine Script) handle signal generation, and FillEdge handles everything that happens after the signal leaves TradingView: validation, routing, compliance, execution, and reconciliation.

Copy trading across prop firm accounts

This is where copy trading gets genuinely complicated, and where most copiers fall apart.

FTMO uses a static max drawdown of 10% and a daily loss limit of 5%. Funding Pips uses a trailing drawdown that ratchets up with your high-water mark. Apex calculates drawdown on end-of-day balances. TopStep checks it in real time, tick by tick.

If you're running the same strategy across accounts at all four firms, the same trade that's perfectly safe on your FTMO account might breach the daily limit on your Funding Pips account. That account already took two losers earlier and has only 1.2% of its daily budget left.

A copier that doesn't understand how each firm calculates drawdown can't protect you here. It copies the signal, the trade executes, and you find out about the breach from the firm's dashboard the next morning. By then, the evaluation is over.

FillEdge's Compliance Guardrails solve this per-account. You bind each broker account to a prop firm profile (firm, account size, phase), and FillEdge loads the exact drawdown rules for that combination. When a signal arrives from the Signal Multiplier, the guardrail checks each destination independently.

Account A has room for the full position? It goes through. Account B is close to its daily loss limit? FillEdge either blocks the trade entirely or auto-reduces the lot size to fit within the remaining budget. Every guardrail decision gets logged with the reasoning: which rule was at risk, what your remaining budget was, and what the original size would have done.

For traders running three or four evaluations in parallel on different firms, this is the difference between passing all of them and losing one to a trade that was safe everywhere except the one account 0.4% from the floor.

What you need before you start

Three things.

First, a TradingView plan that supports webhooks, which means Essential ($14.95/mo) or higher. The free plan won't work. Plus and Premium include more alerts, which matters when you're running multiple strategies.

Second, a broker account that supports MetaTrader, cTrader, or API-based execution. IC Markets, Pepperstone, and most prop firms hand you MT5 credentials by default, so if you already have an account somewhere, you're probably covered.

Third, a bridge service between TradingView and your broker. That's what FillEdge is. It receives the webhook, validates the signal, and delivers it as a real order.

Total cost: $14.95/mo (TradingView Essential) + $29/mo (FillEdge) + whatever your broker charges in spreads and commissions. If you're running an EA on MetaTrader, you'll also need your terminal running 24/5, which usually means a VPS ($10-20/mo).

Copy trading won't fix a bad strategy. If your Pine Script signals are garbage, copying them to five accounts just multiplies the losses five times over. Test on demo first and verify the backtest holds on live data before you start routing signals to funded accounts.

Set it up once, point every strategy at the same URL, and stop worrying about which account got which trade.

FAQ

Does TradingView have a built-in copy trading feature?

No. TradingView is a charting and strategy platform, not an execution platform, and it has no native copy trading function. To copy trades from TradingView to a broker account, you need a bridge service that receives TradingView's webhook alerts and converts them into real orders on your broker. TradingView's paid plans (Essential and above) support webhooks, which are the technical foundation that makes this possible.

Can I copy trades from TradingView to multiple broker accounts at the same time?

Yes, but not inside TradingView itself. You need a bridge service with a fan-out or signal multiplier feature. The bridge receives a single webhook alert from TradingView and routes it to every broker account you've configured, with per-account lot sizing. The key thing to look for is independent execution per destination: if one account blocks the trade (margin, risk limit, compliance rule), the others should still execute normally.

How do I set the correct lot size when copying trades to different accounts?

Most bridge services let you assign a size multiplier per destination account. Your TradingView alert sends a base lot size (say, 1.0 lot), and the bridge scales it for each account: 1.0x on your main account, 0.5x on a smaller funded account, 2.0x on a more aggressive one. FillEdge's Signal Multiplier handles this with a simple matrix in the dashboard, where you set the multiplier once per strategy-account pair and every future signal is sized automatically.

Can I copy TradingView trades to prop firm accounts without breaking drawdown rules?

You can, but only if your bridge understands each firm's specific rules. FTMO, Funding Pips, Apex, and TopStep all calculate drawdown differently (static vs. trailing, real-time vs. end-of-day), so the same trade can be safe on one account and a breach on another. FillEdge's Compliance Guardrails solve this by checking each incoming signal against each destination account's remaining risk budget before the trade reaches the broker, and either blocking or auto-reducing the lot size if the trade would violate a rule.

More from FillEdge

Lock the best price before FillEdge opens to general public.

The first 50 traders lock today's price permanently — it never goes up, no matter the features we add. Get early access and we'll email you the moment the bridge is live.

Join and you'll only get FillEdge launch updates. Unsubscribe anytime.