If you’re evaluating OneUp Trader or already trading a funded account, the question that matters most for automation traders is simple: can you run a TradingView strategy through it without breaking the rules? Short answer: OneUp Trader’s published rules don’t ban algorithmic or bot-driven trading. A few specific restrictions, especially the 10-second trade duration rule,
Search “tradingview webhook alerts official documentation” and you land on posts that read the same way: a paragraph about what webhooks are, a screenshot of the alert box, a vague mention of JSON near the bottom. [ORIGINAL DATA] Eight near-identical variations of that search, “documentation,” “official docs,” “webhook alerts docs,” currently rank positions 7 through
You place a bracket. Price hits your target, the trade closes, and you walk away thinking you’re flat. Twenty minutes later the stop-loss order is still sitting there, live, attached to a position that no longer exists. If it fills, you open a fresh position in the opposite direction you never intended to take. This
If you’ve built a strategy on TradingView and want to see it fire real orders before you fund it with real money, Tradovate’s simulation account is the obvious testing ground for futures traders. It runs the same platform, the same real-time data, and the same order types as live trading. The only thing missing is
If you trade Tradovate futures off TradingView alerts, you’ve probably run into both names. AlertDragon markets itself as a Tradovate specialist. PickMyTrade covers Tradovate plus a longer list of brokers and prop firms. Both do the same core job: turn a TradingView alert into a live order without you manually clicking a mouse. This comparison
You set up one crossover condition. You get two orders, same symbol, same direction, thirty seconds apart, and your broker account is holding double the size you intended. This is one of the most common tickets traders open with automation tools. It almost always traces back to the same cause: your Pine Script condition is
Key Takeaways• TradingView alerts fire once per condition; they don’t natively support multi-leg exits from a single message.• PickMyTrade’s documented workaround uses an advance_tp_sl array inside the alert JSON to split one position into up to three exit blocks.• Quantity per target must be hardcoded at alert-generation time; strategy.position_size is not pulled dynamically.• The workaround
If you searched “trailing stops” on this blog before today, you probably landed on something about trailing drawdown. That’s a different animal. Trailing drawdown is a prop-firm risk rule that shrinks your account’s maximum loss ceiling as your balance grows. A trailing stop is an order-management tool: a stop-loss that follows price in your favor
You’re already in the trade. Price moved, your stop is sitting in the wrong place, and you need to move it now without closing the position. If you run TradingView alerts through PickMyTrade into Tradovate, one webhook does this, but three things about how that update behaves will bite you if nobody warns you: it
You set a limit order on your TradingView strategy for a better entry. Price runs 15 points past your level without touching it. Your strategy tester still shows a clean, filled trade. In Tradovate, there’s a resting order that never became a position. Nothing closed, nothing opened, and the next signal has no idea which
