Support Board
Date/Time: Fri, 18 Apr 2025 04:33:23 +0000
Post From: Issue Managing Multiple Strategies on Same Product with CQG – No Support for Child Account
| [2025-03-26 15:05:02] |
| User368741 - Posts: 57 |
|
I’m currently in the process of shifting my Sierra Chart setup from Trading Technologies (TT) to CQG for order routing and have encountered a significant challenge. In my trading setup, I run multiple automated strategies on the same product simultaneously. When using TT, I was able to manage this efficiently through the use of child accounts, which are supported within the TT ecosystem. Each strategy could be linked to a separate child account, allowing for clear segregation of positions, risk management, and PnL reporting within Sierra Chart. This feature made it possible to operate multiple strategies on the same symbol without conflict or confusion. However, after switching to CQG, I’ve found that this level of account separation is no longer available within Sierra Chart. While CQG itself offers a form of subaccount or strategy tagging through its QT Trader platform—where a user can manually enter a “comment” or “memo” in the order confirmation window to identify orders by strategy—Sierra Chart does not currently offer any mechanism to pass a comment or strategy identifier along with an order routed through CQG. As a result, when using Sierra Chart with CQG, all orders from all strategies are routed through the same account without any way to distinguish them, making it extremely difficult to reconcile strategy-level execution, PnL, or position tracking when trading the same symbol. My key questions are: (1) Is there any current method in Sierra Chart to attach an order comment or strategy tag to orders sent via CQG, similar to what’s possible in QT Trader? ( (2) Are there any recommended workarounds or best practices for managing multiple strategies on the same symbol through a single CQG account within Sierra Chart? My goal is to maintain clean separation between strategies while continuing to use CQG as my execution route, ideally achieving something similar to the child account functionality that is currently possible with TT. |