1. Introduction #

This guide explains three powerful beta features recently introduced in PickMyTrade:

• advance_tp_sl: Enables assigning different take-profits and stop-losses to portions of a trade.
• reverse_action: Allows reversing trade direction for selected accounts within a multi-account setup.
• same_direction_ignore: Prevents duplicate orders in the same direction if an order or position is already open.

All three features are optional, in beta, and designed to give you more control and flexibility in automated trading.

---

Table of Contents #

• What Is advance_tp_sl and How It Works
• Multi-Account Trade Management Using reverse_action
• Avoiding Duplicate Orders with same_direction_ignore
• Integration Notes for Existing Users

---

2. What Is advance_tp_sl and How It Works #

The advance_tp_sl field allows assigning different take-profit and stop-loss levels to individual contract quantities within a single alert.

How to Enable It #

Add the advance_tp_sl key inside your webhook JSON alert.

JSON Example: #

"advance_tp_sl": [
  {
    "quantity": 1,
    "tp": 0,
    "dollar_tp": 5,
    "sl": 0,
    "dollar_sl": 5
  },
  {
    "quantity": 1,
    "tp": 0,
    "dollar_tp": 10,
    "sl": 0,
    "dollar_sl": 10
  }
]

Explanation: #

Let’s say you’re trading 2 contracts of NQ (Nasdaq Futures) and you want to manage each one differently:

• Exit the first contract at $5 profit or $5 loss
• Exit the second contract at $10 profit or $10 loss

In this case, use the advance_tp_sl field with two entries, one for each quantity.

Result:

• First contract exits early for quick profit.
• Second contract stays in longer for larger gain.

This is called scaling out, and is commonly used by professional traders to lock partial profits while giving the rest of the position more room to run.

---

3. Multi-Account Trade Management Using reverse_action #

The reverse_action flag allows you to invert the trade direction for specific accounts within a multi-account configuration.

JSON Example: #

"multiple_accounts": [
  {
    "account_id": "demo124",
    "token": "xxx",
    "reverse_action": true
  },
  {
    "account_id": "demo459",
    "token": "yyy"
  }
]

Explanation: #

Let’s say you’re trading NQ (Nasdaq Futures) and your TradingView alert sends a Buy signal.

You have two accounts connected:

• Client 1 (demo124) should take a Sell
• Client 2 (demo459) should take a Buy

In this case, apply reverse_action: true for demo124.

Result:

• demo124 will place a Sell
• demo459 will place a Buy

This setup is useful when testing opposite strategies, running hedged positions, or balancing exposure across two different clients or firms.

---

Important Notes: #

• reverse_action only works inside the multiple_accounts array.
• It does not apply to single-account setups.
• This feature is currently in beta, monitor execution closely before using it in Live accounts.

---

4. Avoiding Duplicate Orders with same_direction_ignore #

The same_direction_ignore feature helps prevent duplicate orders in the same direction when there’s already an open position or active order, especially useful to stop repeated entries from overlapping signals or rapid re-alerts.

How It Works:

"same_direction_ignore": true

Example Scenario: NQ (Nasdaq Futures) at 20,173

Let’s say the current market price of NQ is 20,173, and your TradingView strategy sends a Buy alert:

• A Buy market order is sent and remains open.
• A few seconds later, a second Buy alert is triggered possibly due to indicator overlap or recalculation.

Since same_direction_ignore is enabled, this second Buy alert will be ignored, because a Buy trade is already active.

Now, let’s say the next alert is a Sell:

• The Sell alert is allowed and will be executed, because it is in the opposite direction.

Similarly, if a Close alert is sent:

• It will close the existing Buy position, regardless of direction.

---

Behavior Summary:

Alert Type	Status	Explanation
First Buy	Executed	No position exists — trade is placed
Second Buy	Ignored	Same direction — already active
Sell	Executed	Opposite direction — allowed
Close	Executed	Closes the current position

Best Practice:
Always add a 2-second gap between alerts to avoid duplicate triggers or execution clashes.

Ignored Alert Message:

Alert Ignored, Same Direction Found on (Open Order/Position)

5. Integration Notes for Existing Users #

• These features are optional — if not included, your alerts will work as usual.
• advance_tp_sl overrides any tp, sl, or risk_percentage settings when defined.
• reverse_action only works in multi-account mode; do not include it in single-account setups.
• same_direction_ignore helps avoid unintentional order duplication.

Final Notes #

Since all features are in beta, we strongly recommend:

• Testing on Demo accounts first
• Monitoring execution carefully
• Reporting bugs or feedback directly to our support team

Email: [email protected]
Discord Community: Join & Connect