Advanced Strategies
Complex multi-order patterns for sophisticated trading
What Makes a Strategy "Advanced"?
Advanced strategies combine multiple order types, time-based logic, and conditional execution to create sophisticated trading systems.
These patterns require deep understanding of order management, risk control, and market dynamics. Start with simpler strategies before attempting these.
Multi-Level Take Profit
Scale out of an existing long position; keep cleanup tied to the position.
ASSUMPTIONS AND LIMITS:
Percentages are calculated at placement. A fill during placement changes the later quantities. Reduce-only, limits and rounding depend on the market.
IMPLEMENTATION:
BTCUSDT on My_API_Key
if posLong continue
stoploss off e2%
limit short 25%p off e3% reduce #tp1
limit short 25%p off e5% reduce #tp2
limit short 25%p off e8% reduce #tp3
limit short 25%p off e12% reduce #tp4
smart-oco sellPosition Flip Strategy
Use separate alerts to confirm closure before entering the opposite side.
ASSUMPTIONS AND LIMITS:
One-way futures only. Verify closure on the exchange before the second message. With 40% total-balance notional and a 2% stop, estimated price risk is 0.8% of total balance before fees, funding and slippage; setting leverage does not multiply this quantity.
IMPLEMENTATION:
ETHUSDT on My_API_Key
pos 0Separate alert, after confirming the first result:
ETHUSDT on My_API_Key
if posNone continue
set leverage 5
market short 40% sl off 2% tp off 6%Dollar-Cost Averaging (DCA)
Schedule separate alerts for each purchase.
ASSUMPTIONS AND LIMITS:
Repeat only on your chosen schedule after checking the previous result. Each message reads its own balance. This percentage is total balance, not the remaining free balance; adding to a position requires reviewing its existing protections.
IMPLEMENTATION:
BTCUSDT on My_API_Key
market long 20% sl off 4%Breakout with Ladder Entry
Trigger entries above the market on supported stop-entry markets.
ASSUMPTIONS AND LIMITS:
Illustrative absolute prices must be above the current market for this buy breakout. Confirm fills before sending the protection message; unfilled entries and the delay before protection remain exposure. Bitunix stop entries are not integrated.
IMPLEMENTATION:
BTCUSDT on My_API_Key
stop long 0.002 at 51000 #ladder
stop long 0.003 at 51500 #ladder
stop long 0.005 at 52000 #ladderSeparate alert, after confirming the first result:
BTCUSDT on My_API_Key
// Send after confirmed fills; cancel pending entries first
cancel #ladder
if posLong continue
sl-or-tp short 100%p sl off e3% tp off e8%Stop Loss Adjustment
Adjust a stop after an externally confirmed price condition.
ASSUMPTIONS AND LIMITS:
Time passing does not prove profit. Check the entry and current price first. Cancelling an old stop creates a protection gap; replacement can fail. Entry price is not a zero-loss guarantee after costs or slippage.
IMPLEMENTATION:
ETHUSDT on My_API_Key
if posLong continue
cancel #initial_stop
stoploss off e0% #breakeven_stopPyramiding into Trends
Add to a position only after a separate signal confirms your strategy condition.
ASSUMPTIONS AND LIMITS:
The posLong condition checks side, not profit or a price move. This adds 25% total-balance notional. Review the protection for the accumulated position and inspect the exchange result after each alert.
IMPLEMENTATION:
BTCUSDT on My_API_Key
if posLong continue
market long 25% sl off 2%Key Advanced Concepts
Position Targeting
Using pos command for precise position control
// Target 0.5 BTC long in one-way mode
pos 0.5Order Tagging
Tag orders for selective cancellation and management
limit long 1 off 100 #entry
// Later cancellation removes open orders, not fills
rem #entryEntry-Based Offsets
Set stops and targets relative to entry price, not market price
// Entry reference: latest market entry in block, otherwise position
stoploss off e5%Execution Delays
wait delays the next command; it does not check price or fills
// Delay; not a fill condition or durable scheduler
wait 1s⚠️ Advanced Strategy Risk Management
1.
Test Extensively
Verify fills and protections in a supported Demo/Testnet environment before considering live use
2.
Start Small
Choose sizes within the exchange limits and your own risk budget
3.
Monitor Closely
Check Execution History after every webhook to verify behavior
4.
Have Exit Plans
Know how to manually exit if strategy behaves unexpectedly
5.
Track Performance
Document wins/losses to evaluate if strategy is profitable over time
Next Steps
→
Review Common Examples if these strategies seem too complex
→
Test strategies in Signal Factory with matching Demo/Testnet credentials where supported
→
Study Command Syntax for detailed parameter documentation
→
Join community discussions to learn from other traders' experiences