TradingView Stop Loss & Take Profit Automation Setup

TradingView stop loss and take profit automation starts with deciding who manages the exit. If your Pine strategy sends complete exit alerts, configure the strategy-controlled workflow. If your signal needs attached protection, enable supported SL/TP in PickMyTrade, choose the units and generate the message for your connected broker.

A stop or target drawn on a chart does not prove that protection exists on your trading account. Check the generated instructions and then the actual broker or platform order records. The setup is complete only when the entry, protection and exit behave as intended.

This guide covers pickmytrade.io. It explains the five commonly documented SL/TP methods, indicator-versus-strategy setup, dynamic plot values and a demo verification process. Available controls and order behavior vary by broker, so use the current guide for your connection.

Quick setup: Choose one exit owner, confirm the instrument and quantity, select the SL/TP units, and generate the broker-specific message. Test the entry, protective orders and exit in demo. Points and percentages describe price distance; neither tells you total account risk without quantity and contract value.

In this guide: Exit ownership → five SL/TP methods → worked calculations → IBKR demo setup → strategy exits → dynamic plot values → advanced-feature checks → troubleshooting and final verification.

TradingView stop loss and take profit automation: exit ownership

A Pine strategy’s simulated exit and an external protective order are separate mechanisms. TradingView can simulate an exit and send an alert, while PickMyTrade can configure supported protection for the routed entry. Choose the mode that matches your source logic rather than enabling every available exit mechanism.

The Rithmic strategy guide describes these exit choices. Its Multiple Exits workflow uses TradingView exit alerts rather than SL/TP attached to the entry. Check the corresponding guide for other brokers before transferring the same settings.

If you combine strategy exits with independent protection, define what happens after either mechanism closes the position. A later sell exit must not create a new short because the earlier stop already flattened the account. Test that sequence explicitly.

How do the five SL/TP methods differ?

Choose the method that expresses your intended levels most clearly. Points, percentage and ticks describe distance; Price describes a level; Total Profit/Loss expresses a monetary input that the workflow converts using instrument information. Similar field labels can hide different calculations, so inspect Calculation Details where available.

The Interactive Brokers futures setup guide documents the modes and calculation popups. Some labels use “USD” while their examples calculate a price distance. Check the formula and resulting level instead of assuming every dollar-labeled box represents total account loss.

For a long position, an ordinary protective stop is below the entry and a target above it. For a short, the directions reverse. Check price increments and broker restrictions too; a mathematically sensible level may still be rejected if it violates the instrument’s rules.

Points, percentages and ticks: worked calculations

The following examples are illustrative calculations, not executed trades or recommended stop distances. They exclude commissions, slippage and any gap beyond the planned stop. Use your broker’s instrument specification and actual entry reference when verifying the result.

Point distance is not total dollar risk

Suppose a long entry is 20,000 and the selected mode uses price points. A 10-point stop is 19,990, and a 20-point target is 20,020. The cash amount depends on the instrument’s value per point and the quantity. Subtracting 100 would create a 100-point distance, not a 10-point stop.

Percentage of price differs from risk percentage

At an illustrative entry price of 100, a 2% stop distance is 2, producing a long stop at 98. A 4% target distance produces a level of 104. This does not mean the trade risks 2% of account equity; position quantity determines the account exposure.

Ticks require the correct contract specification

CME’s Micro E-mini Nasdaq-100 specification gives MNQ a value of $2 per index point and a minimum increment of 0.25 points. That is $0.50 per tick per contract. A 20-tick distance is 5 points, or $10 per contract before costs.

Use either tick count × cash value per tick × quantity, or tick count × tick size × value per point × quantity. Do not multiply by value per point again if your tick value already includes it. That double-counts the contract multiplier.

Price mode: absolute levels for a long or short trade

An absolute price identifies a level, while a distance specifies how far that level sits from a reference price. In a supported Price workflow, enter the intended stop and target levels. Then confirm whether the integration preserves them or converts them relative to its reference and actual fill.

For the long example, entering 2 as the stop price is different from requesting a two-point stop. For the short example, 102 is the intended stop level. Check valid price increments and broker stop-distance restrictions as well as the direction.

These are arithmetic examples, not a universal JSON template. Use the broker-specific Price controls to generate the appropriate field values. If the entry fills at 100.25 instead of 100, compare the submitted stop with the actual order record to establish how that route handled the difference.

Does Total Profit/Loss apply per contract or to the whole trade?

Check the selected workflow’s basis before entering a dollar amount. PickMyTrade’s TradeStation indicator guide describes Total Profit/Loss as fixed dollar values per contract. Its quantity multiplier therefore changes the planned total amount. The word “Total” alone does not establish a whole-position cap.

If a hypothetical per-contract loss input is $100 and the order is three contracts, the planned price loss is $300 before costs. To express a $100 whole-position budget with three contracts, first confirm the mode’s calculation and permitted values. Do not simply enter $100 and assume quantity has no effect.

Changing contract count without reviewing this mode can change the dollar exposure while leaving the entered number unchanged. Record both the per-unit input and the calculated whole-position amount in your test notes.

Step-by-step: configure an indicator with attached SL/TP

For an indicator route, enable the available SL/TP settings in PickMyTrade’s alert generator and use the message generated for your broker. Begin with fixed quantity so the expected position size is clear. Add calculated sizing only after you can verify the basic entry and protection.

1. Sign in to PickMyTrade on pickmytrade.io and connect the intended Demo or Live account.
2. Open Generate Alert and select the broker and INDICATOR alert type.
3. Choose the instrument type and exact symbol or required mapping.
4. Select the entry action, order type and a known fixed quantity.
5. Enable Stop Loss / Take Profit where supported.
6. Choose one SL/TP mode and enter the stop and target values in its stated units.
7. Inspect Calculation Details and record the expected levels or dollar exposure.
8. Add the destination account and check any quantity multiplier.
9. Generate the JSON message and copy the current webhook URL.
10. Create the matching TradingView condition alert and paste the generated message and URL.

For an illustrative MNQ long test, use one contract, a 20-tick stop and a 40-tick target on a broker route that supports this mode. At a hypothetical fill of 20,000, those distances correspond to 19,995 and 20,010. Confirm the route’s actual reference-price calculation and filled quantity before treating these as the live levels.

Do not copy a Tradovate JSON example into a Rithmic, IBKR, ProjectX or other .io route. Generated fields, connection identifiers and protection handling can differ. Use the current broker-specific generator rather than guessing a universal payload.

Complete IBKR demo example: MNQ entry, stop and target

This is an unexecuted configuration example for the IBKR indicator workflow documented in the linked futures guide. It uses a connected IBKR paper account, fixed quantity and tick distances. The test verifies routing and protection; it does not establish live execution quality or recommend these distances.

Connect the IBKR paper account through its supported PickMyTrade connection process and confirm the account identifier. Open Generate Alert, choose IBKR, INDICATOR and Futures, select the correct mapped MNQ contract, and configure BUY with one contract. Enable SL/TP, choose Ticks, enter 20 and 40, then inspect Calculation Details.

Add only the intended paper account with multiplier 1, generate the message, and copy it into the relevant TradingView indicator alert. Paste the current webhook URL into Notifications. Use a condition that can be observed during an eligible trading session. Do not send this test to a live account.

When the condition fires, locate the TradingView alert event, the received PickMyTrade message and the IBKR entry order. Record requested quantity, filled quantity and average entry. Then inspect the actual protective orders, their price levels, quantities and relationship to the entry.

At an illustrative fill of 20,000, the distances produce a stop of 19,995 and target of 20,010 if the route references that fill. If its documented calculation uses another reference, reconcile that result instead. An entry success message is insufficient when one protective leg was rejected or never established.

Verify the exit behavior in paper. After the intended target, stop or supported close operation completes, confirm the expected position is flat and inspect whether any sibling exit remains working. OCO cancellation and order relationships must be checked in the actual route; do not assume a completed exit cancels every other order automatically.

Repeat the relevant failure cases: entry rejected, protection rejected, partial fill and a later exit alert after a protective exit. Preserve the order IDs and messages. This walkthrough follows published configuration guidance, but no order has been placed or tested as part of preparing this article.

Step-by-step: configure a strategy’s exits

For a Pine strategy, decide whether its own exit events are complete before attaching SL/TP. The ProjectX strategy guide distinguishes No SL/TP, Attach SL/TP and Multiple Exits. Its broker-specific protection notes should be checked against the current platform controls when configuring the route.

1. Select STRATEGY in PickMyTrade and choose the actual connected broker and instrument.
2. Use strategy-controlled exits when the script already sends the intended entries and complete exits.
3. Use Attach SL/TP only for the workflow that needs supported protection supplied by PickMyTrade.
4. Use the documented Multiple Exits configuration when the strategy scales out through exit alerts.
5. Generate the message for that account and create the matching TradingView strategy alert.
6. For the standard order-fill route, select Order fills only; use custom alert() events only when the script and integration intentionally use that custom workflow.
7. Test a complete entry-and-exit sequence, including partial exits or reversals if the script uses them.

A TradingView order-fill event reports a simulated fill in its broker emulator. It is not an external broker-fill confirmation. Compare the alert’s instructions with the broker record, especially when a reversal quantity or another strategy changes the account’s actual position.

For stocks and options, use the Tradier strategy guide and confirm whether quantity means shares or option contracts. A stop distance applied to the underlying stock is not automatically an appropriate option-premium stop.

Send dynamic indicator levels with plot placeholders

If an indicator plots an intended stop and target, a supported Price workflow can use those plot values in its generated message. TradingView’s placeholder documentation explains numbered plot placeholders and referencing plots by title. Choose the plot for the indicator that supplies the alert condition.

1. Open the indicator’s Data Window and identify the actual plotted level names.
2. In TradingView’s alert dialog, use Add Placeholder → Plots where available to inspect the plot choices.
3. Match each placeholder with its current chart/Data Window value.
4. Place the target’s placeholder in the Take Profit field and the stop’s placeholder in Stop Loss for the supported Price configuration.
5. Generate the message and confirm the delivered values resolve to numeric levels.

For a Bollinger Bands example on a long setup, the upper band might supply the target and the lower band the stop. Verify the exact indicator plot names and current values; do not assume the upper band is always plot_0 or the lower band always plot_1.

These levels are unknown until the indicator supplies the values at the alert event. Sending them once does not necessarily make the broker orders follow the bands continuously. Moving an existing order requires a supported update workflow, which must be configured and tested separately.

Also confirm whether the integration preserves an absolute level or converts it into a distance before applying it to an actual fill. Entry slippage can change the result. Do not assume a Price input eliminates slippage or keeps every risk/reward calculation unchanged.

Breakeven, trailing stops and multiple targets are separate checks

Advanced exits require broker-specific verification. A supported initial stop does not establish support for automatic breakeven, trailing updates or several attached targets. Check the current connection’s guide and generated controls before adding these features.

Use the TradeLocker indicator guide for its supported controls and calculations. Other broker guides may expose different options. Avoid transferring Tradovate-only update fields or manual-copier behavior to a different platform.

The IBKR futures source checked for this article documents the basic SL/TP calculations; it does not establish every advanced feature above. Accordingly, this guide makes no general IBKR breakeven, trailing or stop-update support claim. Enable an advanced feature only when the selected connection’s current controls and documentation establish it, then test its resulting orders.

For an illustrative scale-out, a three-contract position could reduce by one contract at each of three intended targets. After the first exit, confirm two contracts remain and the protective quantity is appropriate. A later stop or close must not sell more than the intended remaining exposure.

Why did the entry fill without the intended stop or target?

Trace the actual entry message and protection result. The configured form is only a starting point: confirm which generated message the running TradingView alert sent, which exit mode was selected and whether the destination accepted the intended protection. Do not diagnose from the chart line alone.

Changing a value in Generate Alert does not prove that a running alert now sends that value. Paste the regenerated message into the intended alert. TradingView’s alert documentation explains that script inputs, symbol and timeframe are saved at creation; recreate the affected alert when that context changes.

For a support request, provide the account’s broker, symbol, entry and protective order IDs where available, event timestamp with timezone, exact log message and relevant delivered values. Share the identifiers privately and redact tokens, API keys and passwords.

Verify the SL/TP setup in demo before going live

The strongest verification is a complete demo round trip with the intended protection and exit behavior. Start from a known position state and use a small fixed size. Test the actual broker route, not only TradingView’s Strategy Tester or a chart annotation.

1. Record the intended stop, target, quantity and selected mode.
2. Confirm the destination account and environment.
3. Trigger the intended entry and inspect requested versus filled quantity.
4. Verify protective orders or the selected platform-managed exit mechanism and its scope.
5. Check the actual levels against your calculation and the fill reference.
6. Test the exit, partial exit or supported modification used by your system.
7. Confirm the intended final position and any remaining working orders.

Do not remove existing protection from an open position without a deliberate replacement or exit plan. After a rejection, keep account state and working orders visible before sending another instruction. Stop-loss settings describe intended behavior, not a guaranteed fill price or maximum realized loss.

Frequently asked questions

To configure your route, open PickMyTrade, choose the connected broker and generate the SL/TP message. Complete the demo entry, protection and exit checks before enabling live alerts.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: Brokers That Connect to TradingView for Automated Trading