DXtrade Analysis for Traders: Review Decisions and Data

DXtrade analysis is most useful when it answers a specific question about recorded decisions, costs or outcomes. Start with a reconciled account record, then add the context needed for that question. More charts do not compensate for missing trades or an unclear accounting basis.

MyVeridex does not currently offer a DXtrade connection. This guide explains a review and journaling method for records available from your account provider, not a MyVeridex DXtrade-sync tutorial.

Establish the data route and baseline

The official DXtrade trader FAQ directs account questions to the broker or prop firm. It also explains provider control over permitted API IPs and external API access. Ask your provider which reports and data fields it makes available; do not assume a universal desktop export workflow or that every CSV file is compatible with an analytics service.

Before interpreting results, reconcile the account, period, currency, transaction counts, charges and cash movements. The separate DXtrade report reconciliation guide covers that accounting task. Keep unresolved discrepancies visible in the analysis.

Turn a broad concern into a review question

Write down the question and group definitions before repeatedly slicing the results. If a pattern is discovered after exploring the data, label it exploratory. Do not describe the same selected data as a separate confirmation of that pattern.

Keep a journal with explicit missing values

For each reviewed decision, record the strategy version, relevant time, intended setup, planned risk, actual action and available transaction identifier. Add notes on interventions or interruptions when they occurred, rather than inferring emotions from a losing outcome.

Separate account-record fields from your own notes. The provider's fill price is an account observation; a written reason for entering is a journal entry. Neither proves the other. If a field was not captured, mark it unavailable.

An R-multiple needs a defined initial risk amount. A closed profit/loss figure alone cannot establish that amount when the original sizing or stop information is missing. Do not invent a stop level afterwards to make a favourable ratio.

Compare results without changing the units

Use consistent periods, time zones, currencies and definitions of positions, deals and partial closes. Show counts and total results next to group averages so a small subgroup is not mistaken for a broad record.

The mean net outcome per closed record is an observation about the selected records, not a guaranteed expectancy for future trades. Profit factor needs the same accounting basis for winning and losing records and is undefined when its loss denominator is zero. A ratio threshold alone does not approve a strategy.

State whether drawdown uses balance or equity and how often values were observed. Closed-trade results cannot reveal every floating loss. Do not use a reconstructed balance curve as proof that the account remained within every intraday provider limit.

Record a change as a new test

If the review suggests a rule or parameter change, save the change and its reason separately from the original record. Keep earlier results visible. A later test should identify which version it evaluates and what data it holds separate from development; the forward-test protocol guide explains those boundaries.

A report may reveal an operational error, a missing charge or a rule deviation. It cannot establish that changing a schedule or increasing a position will improve future performance. Describe what was observed and what remains uncertain.

Current MyVeridex scope

MyVeridex currently offers MT4 and MT5 account connections using a read-only investor password and supported MT4/MT5 closed-trade imports in HTML, XLSX and CSV. DXtrade, cTrader, Match-Trader and TradeLocker connections are not currently offered. A general statement-import feature does not promise DXtrade export compatibility.

The current statement reconstruction derives balance history from closed results; it does not recover complete historical floating equity. Connected or imported analytics depend on their source records and can still contain gaps. They are not automatically an independent audit, immutable proof of skill or a guarantee of evaluation success.

Frequently asked questions