Cloud Trade Copier Setup:
Connection Checks and Test Record
Platform support update (September 25, 2026): TradeCopier supports MT4, MT5, cTrader, NinjaTrader 8, DXTrade, TradeLocker, MatchTrader and VertexFX. The inspected self-service menu showed MT5, TradeLocker and cTrader; ask support for setup instructions for the other platforms. Confirm your exact broker, account mode, copying direction, instrument and order actions before live use.
Cloud trade copier setup starts with a verified account route: identify what connects each account, what must remain available, which instructions can be copied and how you will check the destination result. A platform logo or a connected indicator does not establish all of those facts. Use a separate acceptance record for each source-to-follower combination before expanding it to more accounts.
This is a connection-dependency and test-record guide for proposed routes, including MT4 and NinjaTrader checks. It is not a universal installer manual. TradeCopier publishes this article about its own product; the proposed checks and fictional example below are not a report of completed TradeCopier tests. The inspected self-service flow offered MT5, TradeLocker and cTrader choices, not an MT4 or NinjaTrader connection. TradeCopier supports both MT4 and NinjaTrader 8; obtain their current setup instructions and demonstrate the specific account-pair route.
Separate the cloud service from the account connection
The TradeCopier cloud service hosts its core copying logic. That does not, on its own, explain every account connector. For a specific route, establish whether the current connection requires a desktop component, an authenticated session, a provider connection or another dependency. Record where each component runs and who restores it after an interruption.
Do not install an EA, cBot, DLL or NinjaTrader AddOn just because an old tutorial mentions one. Platform extension mechanisms are not interchangeable product instructions. Obtain the current instructions for the exact route from the signed-in product or support, and verify the package and publisher through that official path. Do not grant administrator privileges, enable DLL access or change security settings as a generic troubleshooting shortcut.
| Layer | Question to resolve | Record to retain |
|---|---|---|
| Source account | Which account events are visible to the supported connection? | Account alias, provider, platform/build, environment and event scope |
| Connection component | What must remain running, connected or authenticated? | Current component/version, location, dependency and recovery instructions |
| Cloud routing | Which configured route receives the source event? | Route alias, direction, configuration revision and eligibility rule |
| Destination account | Which provider and account receive the instruction? | Follower alias, permissions, instrument and quantity rules |
| Observation | Where can you establish the actual result? | Request, order, fill and resulting-position references, when available |
Write one route record, not a blanket compatibility claim
A route has a direction. Confirmation that one account can send an instruction to another does not confirm the reverse direction, a different broker server, another account environment or a later connector build. Give the route a neutral alias and list those dependencies explicitly.
Keep three evidence states separate: documented means current instructions describe the operation; observed means a dated test produced retained evidence; unconfirmed means the required fact or test is still missing. Documentation alone should not be marked as a passed test. An unavailable test should remain unavailable rather than being counted as a success.
The TradeCopier Forex and Futures page covers supported NinjaTrader 8 workflows while the inspected self-service app did not show a NinjaTrader choice. This article does not establish an exact supported patch version, installation package, provider matrix or tested order-action list. Request current connector, broker and account-pair evidence before planning a TradeCopier NinjaTrader route. A generic NinjaTrader guide, including an AddOn-development guide, cannot prove which connector TradeCopier uses.
| Platform family | Connection question | Acceptance question |
|---|---|---|
| MT4 | Which broker server, account and current connection method are approved for this direction? | How are the requested action, destination order and account state reconciled? |
| MT5 | Which account mode, symbol specifications and trading permissions apply? | How do opening, closing and opposite-side actions affect the intended position? |
| cTrader | Which account/environment and current authorization method belong to this route? | Can accepted, rejected, partially filled and filled outcomes be distinguished? |
| NinjaTrader | Which build, provider, trading account and connection dependencies have been confirmed? | Which order, ATM/OCO and recovery cases are supported and separately verified? |
For detailed MT5 instrument and account-mode diagnosis, use the MT5 connection checks guide. For a small product setup and event sequence within the Free plan, use the Free MT5 setup guide. Use this record to document connection dependencies across the complete route.
Check the trading account separately from market data
NinjaTrader's multiple-connections documentation distinguishes data-source selection from the account selected for an order. A chart receiving prices is therefore not proof that the intended follower account is connected, authorized or selected for trading. Record both facts when investigating a connection that looks healthy but produces no destination order.
For futures, identify the exact instrument and contract month rather than relying on a familiar ticker or continuous chart. For other instruments, retain the provider symbol and contract specification. A quantity label such as lots, units or contracts is incomplete without its applicable definition. Map and size only the verified instrument; a similar display name is not evidence of equivalent exposure.
For MT5, MetaQuotes explains that a successful OrderSend return does not establish a completed execution. cTrader's Open API messages likewise distinguish order outcomes. These are platform concepts, not claims about the fields exposed by every TradeCopier connection. Use the actual supported records for the route.
Download a blank connection and acceptance record
Download the cloud copier connection record (CSV). The worksheet contains proposed cases and starts every result as not_run. It has no account connection, executable code or completed product measurements. Edit a local copy using account aliases; do not place passwords, API keys, authentication tokens or unredacted customer identifiers in it.
Use one copy per route and configuration revision. Fill in the applicable platform/build, connector, account environment, provider, instrument and observation time. Record an expected result before running a permitted test. Afterward, enter what you observed and a reference to sanitized evidence. Keep the original expectation if the result differs.
Use pass only when the declared expected outcome is supported by the retained observation, fail when the observation contradicts it, and unresolved when evidence is incomplete. Use not_supported only when current documentation or support confirms that status; record the source. An unknown capability remains not_run with a note that confirmation is needed.
Define acceptance cases before a demo test
Start in an authorized demo or simulation environment that supports the intended workflow. Confirm the operating procedure before producing an order or interrupting a connection. These are proposed acceptance cases, not instructions to stress a live account, manufacture a rejection or disconnect while carrying exposure.
| Case | What to establish | What remains separate |
|---|---|---|
| Open and close | Expected account, instrument, direction and quantity; destination fills and final position | Pending orders, modification and recovery behavior |
| Modify or cancel | Which order is selected and whether the intended change or cancellation is confirmed | A cancellation response does not erase an earlier partial fill |
| Protection instructions | Which stop/target instruction exists, where it is managed and what the current route supports | A price field alone does not prove ATM/OCO behavior |
| Partial execution | All linked fills, remaining working quantity and resulting exposure | An order count is not a filled-quantity total |
| Unavailable or rejected action | Explicit supported error behavior and retained account evidence | A timeout is unresolved until the destination is checked |
| Reconnect and recovery | Documented behavior for missed, pending or repeated events in a permitted test environment | Do not infer safe replay or automatic flattening from reconnection alone |
NinjaTrader's order-location documentation describes provider-dependent behavior. Establish where the relevant orders and OCO management reside before assuming a desktop shutdown or network loss leaves everything managed. One successful market-order copy does not validate ATM, OCO, cancellation or reconnect behavior.
Read a fictional acceptance record without overstating it
Suppose an operator proposes three cases for a fictional route between two unspecified demo accounts. This example is not TradeCopier test data and makes no claim about a supported platform pair.
| Case | Recorded observation | Result |
|---|---|---|
| Open | The intended demo destination shows the declared filled quantity and direction | Pass for this case only |
| Cancel | No test or cancellation evidence exists | Not run |
| Reconnect | No test or recovery evidence exists | Not run |
The report is one passed case and two not-run cases out of three planned cases. It is not a 100% route success rate. It does not establish a complete opening-and-closing lifecycle, safe recovery or a live-use decision. Expand the case set to the operations actually needed, and resolve unavailable observations explicitly.
Record interruption and retry behavior before expanding
A timeout can mean that evidence arrived late, not that the destination did nothing. Before a retry, reconcile the destination orders, fills and current exposure using the supported procedure. Do not turn an unknown result into a fresh instruction simply because a dashboard has reconnected.
Define what a pause actually pauses. Stopping new copying, cancelling a working order and closing an existing position are different operations. Document the supported behavior and the operator responsible for each one. If you cannot establish the current account state, retain the uncertainty and seek route-specific assistance before issuing a duplicate instruction.
Retest the affected cases after changes to connector/build, provider, account environment, instrument specification, mapping or sizing configuration. A previously passed case belongs to its recorded conditions; it is not permanent certification for all future combinations.
Keep account permission, plan limits and test evidence separate
TradeCopier is live, and its permanent Free plan currently includes one trading group and three total connected accounts. Review current pricing and limits and the getting-started path before configuring a group. A Free-plan limit is not a compatibility statement, and paying for capacity does not establish that an unverified route is supported.
For a prop-firm copying workflow, independently confirm permission for the owners, account stages, providers and copying method involved. Technical support does not grant contractual permission or guarantee challenge completion. Keep the dated rule or provider response with the route record.
Finish the handoff with the configuration revision, confirmed dependencies, passed cases, failed or unresolved cases, unsupported actions, evidence references and the recovery owner. Keep speed, uptime and profitability claims out of the acceptance record unless separately measured by an appropriate documented study. The illustration is conceptual; it is not a screenshot of the TradeCopier interface.
Platform connection choices were rechecked September 24, 2026; other platform references and product pages were reviewed September 22, 2026. Instructions and account rules can change; verify the current route documentation before use.
Quick answers
Frequently Asked Questions
Find answers to the most common questions about this topic.
Does cloud trade copying mean every connection works with the computer switched off?
No. TradeCopier hosts its core copying logic, but the exact account connection can have separate runtime and authentication dependencies. Confirm the current connector, where it runs and what must remain available for the specific route.
Should I install an EA, cBot or NinjaTrader AddOn from this guide?
No. This guide is a connection and evidence record, not a universal installer manual. Use current official product instructions for the exact route; the existence of a platform extension mechanism does not establish that TradeCopier uses it.
Does the guide confirm every NinjaTrader build and account provider?
No. The inspected TradeCopier self-service flow did not show NinjaTrader as a connection choice. TradeCopier supports NinjaTrader 8; this article does not establish its connector, build, broker matrix or tested actions for every account. Request current route documentation and a demonstrated account-pair test before relying on it.
What does the downloadable connection record contain?
It is a blank CSV worksheet with proposed acceptance cases, route fields, expected and observed results, evidence references and notes. Every case starts as not_run. It contains no account connection or completed product measurements.
Does one successful copied order validate the whole route?
No. That observation only supports the case and conditions recorded. Closing, modification, cancellation, partial fills, protection behavior and reconnection require separate checks where supported.
What should I do if a copied instruction times out?
Keep the result unresolved until the destination orders, fills and current exposure are reconciled. Follow the supported recovery procedure; a timeout or reconnection alone does not prove that replaying the instruction is safe.
Is a supported route automatically permitted on a prop-firm account?
No. Confirm the current rules for the owners, account stages, providers and copying method. Technical support and plan capacity do not grant permission or guarantee challenge completion.
