Before you begin: Start with the Smart Trader onboarding checklist and the V2 automation overview. Never use a live account until you have confirmed symbol, order quantity, all intended entry/exit types and risk settings with a demo or minimum-size test.
9. Quantity and Symbol Mapping
Quantity is the #1 setup risk
The word quantity can mean very different things across markets and providers. Before a live test, write down what one unit means at every step.
| System | Possible meaning of quantity |
|---|---|
| TradingView strategy | Contracts/shares/base units calculated by the strategy’s order sizing logic |
| Crypto bot | Base asset amount, quote-currency amount, percentage, or provider-side fixed size |
| Stock broker | Shares |
| Futures broker | Contracts |
| MetaTrader / PineConnector | Lots when using vol_lots |
| Custom server | Whatever your receiver defines |
| Never guess a multiplier If you cannot explain the conversion from the Strategy Tester order quantity to the live broker order size in one sentence, do not enable live automation yet. |
|---|
Symbol mapping
-
Leave Symbol Override blank when the provider accepts TradingView’s ticker exactly.
-
Use the override when the destination requires a suffix/prefix or a different symbol alias.
-
Test long and short on the same mapped instrument before scaling size.
-
Provider-Native routes should normally use the provider’s own recommended TradingView placeholders/mapping rather than the V2 adapter override.
10. Exits, Partial TP, DCA, Add-Ons and Flips
Who owns stops and targets?
Decide this deliberately. There are two broad designs:
| Design | How it works | Main trade-off |
|---|---|---|
| TradingView-owned exits | The V2 strategy sends exit webhooks when its strategy orders fill. | Closest parity to the V2 backtest logic, but exits depend on TradingView alerts/webhook/provider availability. |
| Provider/broker-owned protection | The entry message creates a real broker/provider SL/TP immediately. | Protection can exist even if later TradingView alerts fail, but provider-side stop/TP behavior may not exactly match the strategy’s dynamic exit logic. |
| Avoid accidental double-management Do not have TradingView and the provider independently place conflicting full-size stops/targets unless the integration was designed and tested for it. |
|---|
Partial TP
-
Verify that the provider supports partial reduction rather than interpreting an opposite-side order as a reversal.
-
Verify the closed quantity after lot/contract rounding.
-
Verify the remaining position and any remaining SL/TP after the partial.
DCA and add-ons
-
Start with DCA and Add-On disabled while validating base entry/exit automation.
-
Enable one feature at a time.
-
Confirm the provider allows multiple entries/position increases on the same symbol.
-
Confirm the strategy’s total exposure and the provider’s resulting total exposure match.
Flip/reversal
An opposite signal is not universally interpreted the same way. It can close, reverse, hedge, or partially reduce. Start with Close First Then Wait For Next Signal. Only enable One-Step Reversal after a controlled demo test proves the destination behavior.
11. Strategy-Specific Notes
ORB V2
-
ORB can use breakout orders and may have intrabar-sensitive behavior depending on its selected mode.
-
An order-fill webhook is sent when TradingView’s broker emulator fills the strategy order, not necessarily when the breakout order was first created.
-
OCO/re-entry behavior can create more than one order event in a short period; inspect the alert log during testing.
-
Keep overlap/re-entry conservative until provider parity is confirmed.
Wickless Candle V2
-
Wickless can use resting retest limit logic. The external provider normally receives an order after TradingView considers the strategy limit filled; it is not automatically mirroring the pending limit at the broker in advance.
-
Fast touches/retests can therefore produce live fill-price differences.
-
Verify the exact entry side, quantity, stop behavior and retest fill timing with demo/minimum size.
-
Swing-stop and retest logic can change execution-relevant prices; recreate the alert after any relevant setting or script update.
Other synchronized V2 strategies
Best Strategy V2, EMA Channel + ADX + Andean + CCI V2, MACD Double Cross + 3 EMA V2 and future synchronized V2-framework strategies use the same automation decision tree. Strategy logic can differ, but the alert creation rules do not change as long as the script keeps the V2 order-fill automation framework and its @strategy_alert_message directive.
Based on the TradeSmart V2 Premium Universal Automation Guide, September 2026 edition. Provider interfaces can change; compare provider instructions before real-money deployment. This guide describes V2 framework strategies, not every legacy V1 integration.
Download the complete TradeSmart V2 Automation Guide
Download the complete September 2026 universal guide (DOCX). This is the complete source handbook covering all providers and safety checks.