Do I need to buy API access from Tradovate to use PickMyTrade?
Tradovate API Requirement
No. You do not need to purchase API access from Tradovate.
PickMyTrade is an authorized Tradovate vendor with fully integrated API access.
When you connect your Tradovate account, the API connection is included automatically with no extra fees and no API purchase required.
What You Need
• A valid Tradovate account (live or demo)
• An active PickMyTrade subscription
• A TradingView account
What You Do Not Need
• A Tradovate API add-on or upgrade
• Any additional API fees
• Any third-party API service
Do I need multiple PickMyTrade subscriptions for multiple prop firm accounts?
Do You Need Multiple Subscriptions for Multiple Prop Firm Accounts?
It depends on how your prop firm accounts are organized within Tradovate.
Same Tradovate Login = One Subscription
If all your prop firm accounts exist as sub-accounts under the same Tradovate login, then one PickMyTrade subscription is sufficient.
• You can trade an unlimited number of sub-accounts under that single login.
• When creating alerts, simply select the accounts you want to execute trades on.
• Only one API connection is required.
Different Tradovate Logins = Multiple Subscriptions
If your prop firm accounts use different Tradovate logins, then each login requires its own PickMyTrade subscription.
• Each Tradovate login maintains its own API connection.
• You can manage multiple separate subscriptions through the Account Management section.
Examples
• Apex Account 1, Apex Account 2, and a TopStep account under one Tradovate login require only one PickMyTrade subscription.
• An Apex account under Login A and a TopStep account under Login B require two PickMyTrade subscriptions.
How do I connect my Tradovate account to PickMyTrade?
How to Connect Your Tradovate Account
To connect your Tradovate account, log in to your PickMyTrade dashboard at pickmytrade.trade.
Click Connect to Tradovate.
Choose the appropriate mode:
• Demo Mode: for demo or prop firm accounts such as Apex, TopStep via Tradovate, TakeProfit, or Bulenox
• Live Mode: for live trading accounts
Enter your Tradovate login credentials when prompted.
Once the connection is successful, the status indicator will turn green.
Important Notes
• You do not need to purchase API access from Tradovate. PickMyTrade is an authorized Tradovate vendor and includes API access automatically.
• If you see the message “Tradovate Account is Bound With Another Account,” the account was previously connected to a different PickMyTrade account during a trial. A subscription is required to unlock and reconnect it.
• One PickMyTrade subscription supports unlimited sub-accounts under a single Tradovate login.
Alert Configuration & JSON
Should I manually edit the JSON code from PickMyTrade?
No. Never edit the JSON manually. Always use the exact code generated by PickMyTrade when creating alerts.
Can I use both “quantity” and “risk_percentage” in the same JSON?
No. You must use only one. If you use both, the system will reject or miscalculate your order.
Use one of these:
• Fixed quantity → set quantity and keep risk_percentage = 0
• Risk percentage → set risk_percentage and keep quantity = 0
Rule: Only one sizing method can be active in each alert.
Why am I getting “could not convert string to float: ‘{{close}}’” error?
This happens when TradingView sends the literal text {{close}} instead of the actual numeric price (e.g., 4512.75). PickMyTrade expects a number — so when it receives "{{close}}", it fails.
Why It Happens
• Your indicator/strategy is sending {{close}} as a string, not a number
• The placeholder is inside quotes incorrectly
• Your Pine Script alert message is not formatted correctly
• The alert is created manually instead of using the JSON generator
• The indicator developer coded alerts incorrectly
Solutions
• Use a strategy instead of an indicator
Strategies handle placeholders correctly; many indicators don’t.
• Fix your Pine Script alert message
Ensure {{close}} is not wrapped in quotes inside JSON.
Example (correct): "price": {{close}}
Example (wrong): "price": "{{close}}"
• Ask the indicator developer to correct formatting
Some indicators hard-code alerts incorrectly.
• Try a different placeholder
For strategies: "price": {{strategy.order.price}}
If price is not required, you may use: "price": 0
• Use PickMyTrade’s JSON generator
Never manually edit JSON.
Always copy the exact JSON from PickMyTrade → Create Alert.
Summary
This error means TradingView sent a string instead of a number.
Fix your alert message or script formatting, or switch to a properly coded strategy.
If you want, I can review your JSON or Pine Script and fix it.
Can I use dynamic Take Profit and Stop Loss from my strategy?
Dynamic TP and SL Using TradingView Plot Placeholders
Yes. PickMyTrade can use dynamic TP and SL values by reading them from TradingView plot placeholders.
TradingView only exposes variables to alerts if they are plotted.
How It Works
Step 1: Plot the variables in your Pine Script
Every value you want to use inside the alert JSON must be plotted.
Example:
strategy(“My Strategy”, overlay = true)
long_tp = close * 1.02 // two percent take profit
long_sl = close * 0.98 // two percent stop loss
plot(long_tp, title = “TP_Price”, display = display.none)
plot(long_sl, title = “SL_Price”, display = display.none)
TradingView will not expose a variable to alerts unless it is plotted.
Step 2: Verify the plots in TradingView
Before creating the PickMyTrade alert, confirm that TradingView detects your plots.
To verify:
• Open TradingView
• Create an alert
• Choose your strategy or indicator under Condition
• Scroll to the Message section
• Click Add Placeholder
• Check under the PLOTS section for your plot names
If a plot does not appear under PLOTS, TradingView will not output it and it cannot be used.
Step 3: Use plot placeholders in the PickMyTrade alert
When generating the alert in PickMyTrade, choose Price from TradingView for TP or SL, then select the plot placeholder you verified.
Examples (plain text):
tp: {{plot_0}}
sl: {{plot_1}}
Or by plot title:
tp: {{plot(“TP_Price”)}}
sl: {{plot(“SL_Price”)}}
TradingView will replace these placeholders with live values when the alert fires.
Important Notes
• A plotted variable must appear under the PLOTS section of the TradingView alert interface.
• Plot indices start at zero: plot_0, plot_1, plot_2, etc.
• Dynamic plots work for both strategies and indicators.
• Plots can be used for TP, SL, entry price, quantity, ATR-based values, volatility targets, or any computed value needed by your trade logic.
I’m getting JSON errors when creating alerts. How do I fix them?
Do Not Manually Edit the JSON
Always generate a fresh alert from the PickMyTrade dashboard. Manual edits frequently introduce syntax or field errors.
Common JSON Errors and How to Resolve Them
Boolean values quoted as strings
Wrong: “update_tp”: “true”
Correct: “update_tp”: true
• Fix: Regenerate the alert from the PickMyTrade dashboard.
Missing or unknown connection_name
Typical error: Connection name PROJECTX not found
Cause: The connection does not exist in PMT, or the name is misspelled, or the case does not match.
• Fix: Create the connection with the exact name, then regenerate the alert.
Incorrect Account ID
Wrong: email, username, or a partial ID
Correct: the exact account_id shown in the PMT alert generator dropdown
• Fix: Copy the account ID directly from the dropdown; do not type it manually.
Symbol not mapped
Typical error: Symbol mapping not found
Cause: The symbol is not mapped for that broker in PMT.
• Fix: Create the symbol mapping in Settings → Symbols, then regenerate the alert.
Missing or invalid token
Typical error: Invalid token
Cause: The alert token is expired or invalidated.
• Fix: Regenerate the alert; the token refreshes automatically.
Trailing commas, missing brackets, or smart quotes
Cause: Manual edits or copy/paste operations introducing invalid characters.
• Fix: Do not edit the JSON. Regenerate it and paste as plain text into TradingView.
How do I set up multiple Take Profit levels (TP1, TP2, TP3)?
Multiple TP/SL Compatibility Overview
Support for multiple take-profit (TP) and stop-loss (SL) levels depends on two factors:
• Your broker integration
• Whether you are automating a TradingView strategy or indicator
Details are outlined below.
Tradovate (pickmytrade.trade)
Multiple TP/SL Support for Indicators
Tradovate supports multiple TP and SL levels only when using Indicator Mode with the Advanced TP/SL feature enabled.
• Select “Multiple TP/SL (Advanced)” when generating an indicator alert
• Configure each target using price, ticks, or percent
• Assign a quantity or percentage to each level
Example configuration:
• Entry with 2 contracts
• TP1: close 1 contract at plus ten points
• TP2: close half a contract at plus twenty points
• TP3: close half a contract at plus thirty points
Multiple TP/SL Not Supported for Strategies
Tradovate does not support multiple TP levels from a single TradingView strategy alert.
• If you need multiple TP levels, code all partial exits inside the TradingView strategy
• PickMyTrade will execute each exit exactly as the strategy emits it
Partial Exit Strategy Mode
If the TradingView strategy already includes partial exit logic, select “Partial Exit Strategy” when generating the alert.
PickMyTrade will execute each exit order as generated by the strategy.
Other Brokers (pickmytrade.io)
ProjectX and TopStepX
• Supports one TP and one SL per symbol
• Multiple TP levels are not supported
TradeLocker
• Multiple TP is not yet available
Interactive Brokers
• Multi-TP support varies by routing, account type, and order-handling rules
• Check the latest PickMyTrade documentation for current IB compatibility
Workaround for Indicators on Unsupported Brokers
For brokers that do not support multiple TP/SL natively, use separate TradingView CLOSE alerts:
• CLOSE alert at TP1 to exit one contract
• CLOSE alert at TP2 to exit half a contract
• CLOSE alert at TP3 to exit half a contract
PickMyTrade will process each CLOSE alert independently.
What’s the difference between automating a Strategy vs an Indicator?
Strategy Automation vs Indicator Automation in PickMyTrade
Strategies and indicators can both be automated through PickMyTrade, but they serve different purposes and require different alert configurations. The comparison below explains how each method works.
TradingView Strategy Automation
Pros
• Requires only one alert and handles buy, sell, and close actions automatically
• Uses {{strategy.order.action}} to determine trade direction
• Position sizing is taken from the strategy’s internal settings
• Simple to set up and well suited for beginners
Cons
• Supports market orders only; limit and stop orders are not supported
• Less flexibility for custom take-profit or stop-loss logic
• Must be coded in Pine Script as a strategy
• Requires complete and correct entry and exit logic inside the script
Setup Complexity: Low
Alerts Required: One
Best For: Fully coded, backtested strategies with complete entry and exit logic
TradingView Indicator Automation
Pros
• Supports limit, stop, and stop-limit orders
• Provides flexible TP and SL configuration, including dynamic values
• Works with standard indicators (RSI, MACD, moving averages, etc.)
• Does not require Pine Script coding for basic signals
• Allows use of plot placeholders for dynamic TP and SL values
Cons
• Requires three separate alerts: Buy, Sell, and Close
• More complex to configure because each alert must be set up correctly
• Position sizing must be defined manually in the JSON payload
Setup Complexity: Medium to high
Alerts Required: Three
Best For: Traders automating indicator-based signals or workflows requiring advanced order types
Which Should You Choose
Choose Strategy Automation if you:
• Have a backtested TradingView strategy
• Want a simple single-alert setup
• Are comfortable using market orders
• Already coded full entry, exit, and risk logic inside the script
Choose Indicator Automation if you:
• Trade using standard technical indicators
• Need limit, stop, or stop-limit orders
• Require more precise control over TP/SL
• Want to use dynamic plot values for trade parameters
My TradingView alerts are triggering but trades aren’t executing. Why?
TradingView Alert Fired but No Trade Executed
This is one of the most common troubleshooting scenarios. Review the items below in order, as they resolve most failed executions.
Missing Webhook URL
Open your TradingView alert and go to the Notifications tab.
My trades are closing immediately after opening. What is happening?
Why Trades Immediately Reverse or Close Right After Entry
This issue is almost always caused by TradingView sending both a buy signal and a sell signal at the same time.
Root Cause
Your TradingView strategy or indicator is triggering a buy alert and a sell alert (or a close alert) at the same moment or within seconds of each other.
How to Diagnose
Open TradingView and go to the Alerts section.
Select Alert History.
Review recent alerts or export them to a CSV file.
Look for buy and sell alerts with identical or nearly identical timestamps.
Common Causes
Strategy logic errors
• The script enters and exits on the same bar
• The script uses strategy.close_all incorrectly
• Multiple entry or exit conditions fire at the same time
Alert condition configured incorrectly
• Alert is set to Once Per Bar instead of Once Per Bar Close
• Alert fires on both the bar open and the bar close
Conflicting indicators
• One indicator sends a buy and another sends a sell
• Both indicators are connected to the same PickMyTrade account
Solutions
Fix your Pine Script logic
Use position-state checks to prevent entering and exiting on the same bar.
Plain-text example:
if (buy_condition and strategy.position_size == 0)
strategy.entry(“Long”, strategy.long)
if (sell_condition and strategy.position_size > 0)
strategy.close(“Long”)
Enable same_direction_ignore in PickMyTrade
This setting prevents PMT from opening or closing positions if the incoming signal matches the current direction.
Plain-text example:
same_direction_ignore: true
Separate your alerts properly
• Use different alerts for entry and exit
• Do not use a single alert for both conditions
Check alert logs
Compare TradingView alert logs with PickMyTrade alert logs:
• A healthy sequence shows: buy → wait → sell
• A problematic sequence shows: buy → sell immediately
Why are my trades being rejected by my broker? (Tradovate)
PickMyTrade may show that the order was sent, but Tradovate provides the official rejection reason.
Check it directly in the Tradovate platform.
Where to Check
Log in to Tradovate → Orders → Order History
Rejected orders are highlighted in red.
Click the order to view the rejection reason.
Common Tradovate Rejection Reasons
Insufficient margin
• Not enough buying power to support the position
• Reduce position size or add funds
Invalid quantity
• Decimal quantities used for futures
• Quantity exceeds account or prop firm limits
• Verify the quantity in your PickMyTrade alert
Expired contract
• The symbol refers to an expired futures contract
• Update your symbol mapping to the current active contract
Account restrictions
• Daily or weekly loss limits reached
• Symbol blocked by prop firm
• Trading attempted outside permitted hours
Risk limits exceeded
• Max-contract-per-order or position-size limits triggered
• Review Tradovate → Account → Risk Settings
Invalid or unknown symbol
• Symbol not recognized or not mapped correctly
• Ensure symbol is mapped and tradable
Market closed
• Order submitted outside trading hours
• Confirm the session schedule
Symbol Mapping & Contract Rollover
Can I Trade Crypto Futures or Forex with PickMyTrade? (Tradovate)
Support depends entirely on Tradovate’s product offering.
Crypto Futures Support
• Supports Bitcoin futures (BTC)
• Supports Ethereum futures (ETH)
• Only CME crypto futures are available
• Does not support spot crypto or exchange-traded crypto pairs
• Crypto product selection is limited compared to crypto exchanges
Forex Support
• Tradovate does not support forex
• Tradovate is strictly a futures-only broker
If you need spot crypto or forex, Tradovate is not the appropriate broker.
How does contract rollover work? Do you need to do anything?
PickMyTrade handles contract rollover automatically in most cases.
Your automation continues running normally as long as you use continuous TradingView symbols such as MNQ1!.
How Auto-Rollover Works
Monitoring
PickMyTrade tracks expiration dates for all mapped futures contracts.
The rollover process begins about four days before expiration.
Automatic update
PickMyTrade updates the symbol mapping to the next contract month automatically.
Example: MNQZ25 → MNQH26 when December rolls into March.
This occurs in the background with no action required.
No action required from you
Your TradingView alerts continue using continuous symbols like MNQ1!.
PickMyTrade translates that symbol to the active contract month.
Trading continues normally during and after the rollover.
What You Should Do
Before expiration
• Close any open positions in the expiring contract manually
• Brokers do not roll open positions automatically
• Avoid holding positions into expiration unless you intentionally want to
After rollover
• Open PickMyTrade → Settings and confirm the new contract month is mapped
• Run a small test trade to verify mapping and execution
If You Trade a Specific Contract Month Instead of the Front Month
If you prefer to stay on a specific month:
• Do not use continuous symbols such as MNQ1!
• Use the exact contract month in TradingView, e.g., MNQZ25
• Create a matching symbol mapping in PickMyTrade (MNQZ25 → MNQZ25)
This disables auto-rollover for that symbol and keeps you locked to the chosen month.
Rollover Frequency
Quarterly contracts
• Stock indices (ES, NQ, YM)
• Metals (GC, SI)
These roll in March, June, September, December.
Monthly contracts
• Products like CL (Crude Oil) and various agricultural contracts roll monthly.
Checking Expiration Dates
You can verify expiration schedules:
• Inside the Tradovate contract specifications
• By contacting Tradovate support
I’m getting “Symbol mapping not found” error. How do I fix it?
Why Am I Getting “Symbol Mapping Not Found”?
This error means PickMyTrade does not know how to translate your TradingView symbol into your broker’s contract symbol.
Why Symbol Mapping Is Needed
TradingView uses continuous symbols such as MNQ1!, ES1!, or GC1!
Tradovate uses specific contract months such as MNQZ25, ESH25, or GCZ25
PickMyTrade needs a symbol mapping table to convert the TradingView symbol into the correct broker contract.
How to Create Symbol Mapping
Creating the mapping yourself
• Open the Settings section in your PickMyTrade dashboard
• Select Create Setting
• Enter your TradingView symbol (example: MNQ1!)
• Enter the broker symbol for the current active contract (example: MNQZ25)
• Best for: Traders who want consistent dollar risk every trade
• Pros: Simple and consistent
• Cons: Position size changes depending on SL distance
3. percentage_sl
• Stop loss is a percentage away from the entry price
• Example: 2% SL on $100 entry → stop at $98
• Best for: Stocks and forex
• Pros: Adapts to price and volatility
• Cons: May not match technical levels
Which one should you use?
• Use sl (ticks): Futures / technical-level traders
• Use dollar_sl: Want fixed dollar risk per trade
• Use percentage_sl: Stocks/forex or volatility-based systems
Critical Rule:
Use only ONE stop-loss method per alert. Set all others to 0.
Can I update stop loss or take profit for an existing position?
Yes, you can update your stop loss (SL) or take profit (TP) for an active position by using the update_sl and update_tp parameters in your alert.
How It Works:
• update_sl = true → Your existing stop loss is cancelled and replaced with the new SL.
• update_tp = true → Your existing take profit is cancelled and replaced with the new TP.
• When these are set to false, your existing SL/TP remains unchanged.
Example Use Cases:
• Move stop to breakeven when your trade reaches a certain profit level.
• Trail the stop loss by sending periodic alerts as price moves in your favor.
• Tighten risk when your indicator detects a potential reversal.
Important Notes:
• Every SL/TP update sends a new modification order (your broker may charge fees).
• Not all brokers support the same level of SL/TP modification — behavior depends on the broker.
• Always ensure you send only one active SL and TP method at a time.
If you want, I can give a short “best-practice” version too.
Why aren’t my stop losses triggering?
Stop losses may fail for several reasons depending on your broker setup and alert configuration.
Possible Causes:
• Stop loss not included — Your JSON may have sl/dollar_sl/percentage_sl set to 0, so no stop is placed.
• Broker rejected the stop — Check PickMyTrade alert logs for errors (e.g., invalid price, too close, or ProjectX 1000-tick limit).
• Your strategy replaced the stop — If update_sl is enabled, new alerts can cancel or modify the previous stop.
How to Troubleshoot:
• Check your PickMyTrade alert logs for any SL rejection messages.
• Verify your JSON configuration and ensure exactly one SL method is used.
• Test with a larger stop loss to confirm the order is being placed.
• Check your broker’s transaction/order history to see if the SL was sent or cancelled.
• Contact PickMyTrade support with order IDs and your alert JSON if the issue continues.
What does reverse_order_close mean?
The reverse_order_close setting controls how PickMyTrade behaves when an opposite signal is received while you already have an open position.
This parameter is intended only for indicator-based alerts.
If your TradingView strategy sends explicit entries and exits, you should not rely on reverse_order_close.
How It Works When Enabled
When reverse_order_close: true is used:
• An opposite signal fully closes your current position
• A new position in the opposite direction is opened immediately
• Behavior becomes: long → flat → short, applied automatically
Example:
If you are long and a sell signal arrives, the long position is closed and a short position of the same size is opened.
How It Works When Disabled
When reverse_order_close: false is used:
• An opposite signal only closes your current position
• No new position is opened
• Behavior becomes: long → flat
Example:
If you are long and a sell signal arrives, the long position is closed and you remain flat.
Configuration (Plain Text)
reverse_order_close: true (close and reverse)
reverse_order_close: false (close only, no reversal)
Example with reverse_order_close: true
Assume you are long two contracts at forty-five hundred.
• A sell signal arrives
• The long is closed
• A short position of two contracts is opened
• Your new position is short
Example with reverse_order_close: false
Assume you are long two contracts at forty-five hundred.
• A sell signal arrives
• The long is closed
• No short is opened
• You remain flat
When You Should Use reverse_order_close: true
• For indicator-based systems that continuously alternate between long and short
• For trend-following or swing systems that always want to stay in the market
• When you want smooth, fully automatic transitions between long and short
When You Should Use reverse_order_close: false
• When your system sends explicit entries and exits separately
• When a sell signal should close the long but not open a short
• When flattening at end-of-day
• When your TradingView strategy already manages direction changes internally
Best Practice
• Use true only for indicator-driven signals needing automatic reversal logic
• Use false for strategies with explicit entry/exit logic
• If unsure, false is usually safer
Related Parameter: data set to close
If you want an alert to function strictly as a close command:
data: close
reverse_order_close: false
Important Note
reverse_order_close should be used only with indicator-based alerts.
TradingView strategies generate their own entry/exit instructions and should not rely on this parameter.
What does same_direction_ignore do?
The same_direction_ignore setting determines whether PickMyTrade prevents multiple entries in the same direction or allows pyramiding (stacking positions).
How It Works When Enabled
When same_direction_ignore: true is used:
• Duplicate signals in the same direction are ignored
• If you are already long and another buy signal arrives, it is ignored
• If you are already short and another sell signal arrives, it is ignored
• Prevents stacking/pyramiding
• Ensures only one position per direction is open at any time
How It Works When Disabled
When same_direction_ignore: false is used:
• Multiple entries in the same direction are allowed
• If you are long, additional buy signals increase your long position
• If you are short, additional sell signals increase your short position
• Supports pyramiding and scale-in logic
Configuration (Plain Text)
same_direction_ignore: true (one position at a time)
same_direction_ignore: false (allow pyramiding)
When You Should Use same_direction_ignore: true
• When your strategy sometimes issues duplicate signals
• When you want conservative, controlled position management
• When you want to prevent accidental pyramiding due to imperfect logic
• Useful as a safety mechanism for most traders
When You Should Use same_direction_ignore: false
• When your trading approach intentionally scales into winning positions
• When your TradingView strategy uses multiple strategy.entry calls to build size
• When pyramiding is a core part of your system
Example Scenarios
Scenario with same_direction_ignore: true
• At ten o’clock you buy two contracts at forty-five hundred
• At ten oh five another buy signal appears but is ignored; you remain with two contracts
• At ten ten a sell signal arrives and the entire position closes
Scenario with same_direction_ignore: false
• At ten o’clock you buy two contracts
• At ten oh five a second buy signal appears and executes; now you hold four contracts
• At ten ten a sell signal arrives and all four contracts close
Related Setting: Pyramid Mode
PickMyTrade includes a Pyramid toggle in advanced risk settings:
• Pyramid ON → same_direction_ignore is false (stacking allowed)
• Pyramid OFF → same_direction_ignore is true (one position only)
Best Practice
• If unsure, set same_direction_ignore: true, as it is safer for most strategies
• Only set it to false when pyramiding is explicitly required
• If enabling pyramiding, test with small position sizes first
What is Break-even and how do I enable it?
Break-even automatically moves your stop loss to your entry price once your trade reaches a defined profit level.
This removes risk from the trade and secures a neutral outcome even if the market reverses.
How Break-Even Works
In a traditional setup:
• Enter at forty-five hundred
• Stop loss at forty-four ninety
• Price moves to forty-five fifteen
Your stop remains at forty-four ninety, and you are still risking ten points.
With break-even enabled:
• Once price reaches the break-even trigger level
• Your stop loss moves to your entry price
• The worst possible outcome becomes a neutral exit (no loss)
Configuration
To enable break-even, include:
breakeven: 15
This example means the stop loss moves to break-even once the trade is fifteen points in profit.
Example Scenarios
Long trade example
• Enter at eighteen thousand (NQ)
• Initial stop loss: seventeen thousand nine hundred eighty
• Break-even trigger: twenty-five points
When price hits eighteen thousand twenty-five, the stop moves to eighteen thousand.
You can no longer lose on the trade.
Short trade example
• Enter short at forty-five hundred
• Initial stop loss: forty-five twenty
• Break-even trigger: thirty points
When price drops to forty-four seventy, the stop moves to forty-five hundred.
The trade becomes risk-free.
Combining Break-Even with a Trailing Stop
Break-even and trailing stop features work together.
Break-even first, then trailing
breakeven: 20
trail_trigger: 40
trail_stop: 15
trail_freq: 5
The stop moves to break-even at twenty points, then switches to trailing at forty points.
Break-even as a safety net
breakeven: 10
trail_trigger: 25
trail_stop: 12
The stop locks in safety early and trails only after reaching a higher profit zone.
Best Practices
Conservative break-even
• Trigger at one and a half to two times your initial stop distance
• Example: twenty-point stop → thirty to forty-point break-even trigger
• Reduces premature exit risk
Aggressive break-even
• Trigger at one to one and a half times your stop
• Removes risk sooner but may cut strong trends early
• Do not manually type values like “4500” or “long” — let TradingView fill them.
• Placeholders are case-sensitive.
• Always use the JSON generated by PickMyTrade to avoid formatting issues.
Do I need to keep TradingView open for alerts to work?
No. After your alerts are configured, you do not need to keep TradingView or PickMyTrade open — both run entirely in the cloud.
Do I need a paid TradingView account to use PickMyTrade?
Yes. You need a paid TradingView plan (Pro, Pro+, or Premium) to use PickMyTrade automation.
Why a paid plan is required:
Free TradingView accounts have very limited alerts
Webhook alerts (required for PickMyTrade) are only available on paid plans
Automated trading typically requires multiple active alerts (entries, exits, SL/TP)
Bottom line:
A paid TradingView subscription is required for PickMyTrade to receive alerts and execute trades automatically.
Platform Features
What is the News Filter feature and how does it work?
The News Filter automatically pauses trading during scheduled high-impact economic events, but it only applies to the symbols that are supported in the News Filter list inside your dashboard.
How it works:
• Enable it in Dashboard → Settings → Trading Time Settings
• Turn News Filter ON
• It only affects symbols that appear inside the News Filter supported-symbols list
• Choose which impact levels to block (High, Medium, Low)
• Set buffer times before and after news releases
• During the news window, PickMyTrade ignores new alerts for supported symbols
• Existing positions remain active (SL/TP still work)
Impact levels you can block:
• High impact (NFP, CPI, FOMC)
• Medium impact
• Low impact
Buffer time behavior:
• Stops trading X minutes before the news
• Resumes trading X minutes after the news
Example:
• High impact enabled, 5-minute pre-buffer, 10-minute post-buffer
• CPI at 8:30 AM
• 8:25 AM → trading paused (for supported symbols only)
• 8:30 AM → news released
• 8:40 AM → trading resumes
Benefits:
• Avoids volatility spikes
• Reduces slippage
• Blocks trades during unstable conditions
• Fully automatic
Important:
• ✅ Works only for symbols listed under the News Filter section
• ❌ Does not apply to symbols that are not in the supported list
• Does not close existing positions
What is the “Saved Alerts” feature?
The Saved Alerts feature lets you save your alert configurations and reuse them later without regenerating settings each time.
How it works:
• Go to the Create Alert page and configure your settings
• Click Save Alert and give it a name
• Go to the Saved Alerts section anytime
• Click Load / Use This Alert to instantly regenerate the same configuration
• Edit and re-save if you want to update the template
Benefits:
• Save time by not rebuilding alerts from scratch
• Store multiple strategies with different risk settings
• Keep templates for different accounts or symbols
• Quickly regenerate JSON if a TradingView alert is deleted
• Great for A/B testing different SL/TP or risk profiles
Use cases:
• One template for ES, one for NQ
• Separate templates for scalp, swing, or day-trade setups
• Different templates for small vs. large account configurations
Where to find it:
• In your PickMyTrade dashboard → Saved Alerts section
Does PickMyTrade have a referral program?
Yes, PickMyTrade has a referral program available for all users.
How it works:
• Log in to your PickMyTrade dashboard
• Go to the Referral System section
• Copy your unique referral link
• Share it with friends, communities, or social platforms
• When someone signs up and subscribes using your link, you earn rewards