Copy Trading Risk Management
- Followers own size and risk caps. Providers own pair, direction, and order logic. Never assume the provider's SL will save you — set your own.
- Sources can pause, drift, or break. Treat copy trading like every other trade: with sizing rules, a max-loss-per-day, and an exit plan.
- TVH is a tool. Outcomes are the user's responsibility on both sides of the channel.
The override model gives followers full control over sizing and risk caps. That is both the strength and the catch — full control means full responsibility. This page collects the patterns that prevent the most common copy trading blow-ups.
Override hierarchy reminder
There are exactly four things a follower controls:
| Follower controls | Override rule |
|---|---|
| Position size | Follower wins (unless unitsType: "signalSource" — then inherit) |
| Leverage (if set) | Follower wins if set, else broadcast's default |
| Stop Loss (if non-zero) | Follower wins if non-zero, else broadcast's SL |
| Take Profits (if non-empty) | Follower wins if non-empty, else broadcast's targets |
Everything else — pair, direction, order type, DCA, trailing SL, break-even, hedge mode, scaled orders — is locked to the provider's broadcast.
For the canonical field-by-field truth table, see Broadcast — What followers receive vs. what they override.
The practical takeaway: never rely on the provider's SL. The fields that protect you (size, leverage, SL) are exactly the ones you control. Use that power.
Best practices for followers
| # | Practice | Why |
|---|---|---|
| 1 | Always set your own Stop Loss. | Providers can forget to attach an SL. If they do, your Copy Trade has none either. Override with a percent SL that matches your risk tolerance. |
| 2 | Size for max-drawdown, not best-case. | Pick a position size such that five consecutive losses still leave you operational. If 5 losses kill you, your size is wrong. |
| 3 | Do not max-leverage. | Providers may sit at 10x in their head and quote sizes assuming 10x. Use what makes sense for your equity, not theirs. |
| 4 | Test with small size first. | Run 1-2 weeks of minimal-size copy trades before scaling up. Watch how the provider behaves in different market regimes. |
| 5 | Diversify across signal sources. | One source = one point of failure. Two or three uncorrelated sources is healthier. |
| 6 | Monitor weekly. | Performance drifts. Strategies stop working. Check your Activity Log every weekend. |
| 7 | Pause around high-risk events. | FOMC, CPI, earnings (for stocks), exchange maintenance windows. Toggle off in My Copy Trades; toggle back on after. |
| 8 | Set a personal max-loss-per-day rule. | If you hit -X% in a day, disable the Copy Trade. Re-enable tomorrow with a cooler head. |
| 9 | Keep withdrawal permissions off the exchange API key. | This is the standard TVH best practice — see Account & API Keys. Copy trading does not change it. |
| 10 | Never share your TVH Token with the provider. | They only need your email to invite you. Anyone with your TVH Token can fire trades on your account. |
Best practices for signal sources
| # | Practice | Why |
|---|---|---|
| 1 | Document the strategy clearly. | Followers cannot calibrate risk if they do not know what they are getting. Strategy, timeframe, expected drawdown — put it in the description. |
| 2 | Stay consistent. | If you advertised "scalping BTC" and pivot to "swing ETH", tell followers first. Sudden strategy changes get people hurt. |
| 3 | Include a default SL in broadcasts. | Even if you trade discretionarily, broadcast a wide SL (5-10%) as a backstop. Cautious followers will tighten it; lazy ones will at least be capped. |
| 4 | Avoid revenge trading. | A bad day for you is a bad day for everyone you broadcast to. Step away after big losses. |
| 5 | Communicate pauses. | Tell your Telegram / Discord when you stop trading. TVH does not auto-notify followers. |
| 6 | Do not promise returns. | Past performance is not future performance. Promising returns is a legal liability in most jurisdictions. |
| 7 | Test on demo before going live. | If you cannot back-test a strategy, your followers cannot either. Validate before broadcasting real money. |
| 8 | Have backup infrastructure. | If your TradingView alert engine breaks, broadcasts stop. Followers do not know why. Use a second alert as failsafe and document where to check status. |
What can go wrong
A non-exhaustive catalogue of failure modes seen in production. Skim it once, then use it as a checklist.
| Failure | Effect | Mitigation |
|---|---|---|
| Provider's API key expires. | Provider's own trades fail; broadcasts may still fan out depending on flow. Activity Log shows API errors on the provider side. | Provider rotates the key. Followers are unaffected if the broadcast was already queued. |
| Provider pauses mid-trade. | Open positions on follower accounts stay open. Provider stops broadcasting closes. | Followers maintain their own exit logic, ideally via SL/TP in their Copy Trade. |
| Exchange downtime on a follower's exchange. | Broadcast arrives, follower's exchange rejects. Order fails silently unless logged. | Check your Activity Log; cross-exchange diversification helps. |
| Provider's strategy starts losing. | Provider keeps broadcasting; followers keep losing. | Personal max-loss-per-day rule. Pause and reassess. |
| Provider revokes invitation. | Follower's Copy Trade goes dormant. No notification. | Check Signals tab if broadcasts stop arriving unexpectedly. |
| Follower forgets to set SL. | Provider's optional SL is used (if any). Otherwise position runs unguarded. | Always override SL — see best practice #1. |
| Pair format mismatch on cross-exchange copy. | Broadcast arrives, follower's exchange rejects the symbol. | Pre-check pair format compatibility before subscribing. See Follow on a different exchange. |
| Provider's TradingView alert engine breaks. | No broadcasts fire. Followers see nothing in the Activity Log. | Provider should run a duplicate alert as failsafe. |
Override examples — common patterns
Conservative follower (provider's trailing is OFF)
You trust the provider's setup but not their leverage. The provider does not broadcast trailing SL — fine, you just want a hard SL and a tight size.
{
"exchange": "binance",
"pair": "BTCUSDT",
"unitsType": "percent",
"unitsPercent": 1,
"leverage": 3,
"marginType": "isolated",
"stopLossType": "percent",
"stopLossPercent": 1.5,
"broadcastSignal": "SIGNAL_SOURCE_ID",
"token": "YOUR_TVH_TOKEN"
}
What this does:
- 1% of balance per trade, isolated margin (caps loss at the position level).
- 3x leverage even if the provider runs 10x.
- Hard 1.5% SL even if the provider sets a wider one or none at all.
- No trailing fields set. Since the provider has trailing off, no trailing logic runs. Predictable.
Conservative follower (provider broadcasts a trailing SL you want)
Same setup, but this provider deliberately broadcasts useTrailingStopLoss: true with a 2% trail. You can leave the trailing fields out of your Copy Trade — the broadcast's trailing will run on your account automatically.
{
"exchange": "binance",
"pair": "BTCUSDT",
"unitsType": "percent",
"unitsPercent": 1,
"leverage": 3,
"marginType": "isolated",
"stopLossType": "percent",
"stopLossPercent": 1.5,
"broadcastSignal": "SIGNAL_SOURCE_ID",
"token": "YOUR_TVH_TOKEN"
}
The key thing to understand: you cannot override the provider's trailing SL. useTrailingStopLoss, trailingStopLossPercent, and stopLossToBreakEven are always taken from the broadcast — putting them in your Copy Trade has no effect. If the provider has trailing off, you get no trailing. If they have it on, you get their trail.
Inherit the provider's sizing exactly
You trust the provider's risk-sizing model and want a 1-to-1 mirror.
{
"exchange": "bybit",
"pair": "BTCUSDT",
"unitsType": "signalSource",
"broadcastSignal": "SIGNAL_SOURCE_ID",
"token": "YOUR_TVH_TOKEN"
}
The broadcast copies the provider's unitsType, unitsPercent, units, leverage, marginType, useFixedSize, and fixedQuoteSize into your Copy Trade at broadcast time. Use this only when you have actively verified the provider's sizing is sane for your account.
Aggressive (not recommended)
For completeness — this is what you should not do:
{
"exchange": "binance",
"pair": "BTCUSDT",
"unitsType": "percent",
"unitsPercent": 20,
"leverage": 20,
"broadcastSignal": "SIGNAL_SOURCE_ID",
"token": "YOUR_TVH_TOKEN"
}
20% balance per trade at 20x leverage, no SL — and no trailing override either. Three consecutive losses wipe most of the account. If the provider also has no SL, the first big move ends the experiment. Do not do this.
Liability disclaimer
TVH is a routing and execution tool. It does not vet signal sources, evaluate strategies, or guarantee outcomes.
- TVH is not responsible for losses caused by signal providers, follower configuration, exchange outages, or strategy underperformance.
- Signal sources are not financial advisors unless they hold the relevant license in your jurisdiction.
- Followers retain full responsibility for their own accounts, API keys, position sizing, and risk discipline.
- Past performance is not predictive of future results. Any historical chart, backtest, or testimonial from a provider should be treated as a marketing claim, not a guarantee.
The full Terms of Service apply — see the link in the footer of the main site. Trade carefully.
Next steps
- Refresh on how broadcasts merge into follower commands → Follow a Signal — How override works
- Lock down your provider configuration → Broadcast a Signal — What followers receive
- Review your API key hygiene → Account & API Keys