MT4/MT5 Analytics Connections: Credentials and Data Checks
To connect an MT4 or MT5 account to analytics, check the platform, account number, exact broker server and read-only credential before judging the resulting charts. A successful login and a complete, correctly interpreted data record are separate checks.
MyVeridex currently offers MT4 and MT5 investor-password connections and supported MT4/MT5 closed-trade statement imports. cTrader, DXtrade, Match-Trader and TradeLocker connections are not currently offered. Do not choose another platform to force an unsupported connection.
Prepare the correct account details
MetaQuotes documents read-only investor authorisation for both MT4 and MT5. An account number, password and server belong together. The broker's name alone is not a complete server identifier, and similarly named demo and other servers can host different accounts.
| Check | What to confirm |
|---|---|
| Platform | The account actually uses MT4 or MT5, matching the selected connection type. |
| Account and server | The numeric trading account identifier and exact server shown by your provider. |
| Credential | The account's investor password, not its trading/master password or broker-portal password. |
| Availability | The service can reach and support this particular account/server combination. |
| Data handling | What records the service receives, retains and makes visible to others. |
Use the supported MyVeridex connection form
The current account-connection form offers MT4 and MT5, with broker/server, account number and investor-password fields. Supply the details through the official application after checking the account and the recipient. The investor-password field does not require the master credential.
The offered connection uses a server-side bridge rather than requiring a download to your local terminal. Availability and refreshes still depend on the connection service and account/server support. Do not interpret the absence of a local-terminal requirement as a guarantee of continuous updates or a fixed initial-sync duration.
If authentication fails, first recheck the platform, server and account details through your own provider records. Do not substitute the master password or invent a server address. Report the error through support without including passwords in the message or screenshot.
Validate the records after connection
- Identity and environment: confirm that the displayed account, provider, currency and demo/evaluation/other classification match the source.
- Coverage: record the earliest and latest transactions received and any missing interval. A connected status is not proof of complete historical coverage.
- Transactions: reconcile available identifiers and whole-period counts, distinguishing positions, deals and partial closes.
- Costs and movements: check whether results include charges and separate deposits, withdrawals and adjustments from trading outcomes.
- Freshness: inspect the actual update status and time. A historical record can be accurate for its period while the connection is currently stale.
Keep unresolved differences visible and retain the original report. Do not choose whichever total looks better or assume an automated import cannot contain errors.
Use statement imports within their limits
MyVeridex imports supported MT4/MT5 closed-trade statements in HTML, XLSX and CSV formats. The extension alone does not establish compatibility: the file still needs the fields the parser expects. It is not a universal importer for every platform's export.
The current reconstruction builds a balance history from closed-trade results. It does not recover every floating gain or loss between entry and exit. A historical balance curve therefore cannot by itself certify an equity-based daily loss rule or the account's complete intraday drawdown path.
Keep the conclusions within the evidence
A report can organise the records received and explain their calculation basis. It is not automatically an independent audit, immutable proof of skill or a guarantee of funding, profitability or evaluation success. The provider's own account rules remain separate.
For the credential's scope, read what an MT4 investor password means. For MT5 password creation and a read-only login check, use the MT5 setup guide. Those tasks are separate from verifying a service's resulting data.
Frequently asked questions
Which password does the MyVeridex connection form need?
The current MT4/MT5 form uses the investor password with the broker/server and trading account number. Do not enter the master trading password or broker-portal password in that investor-password field.
Must my local terminal stay open for the offered connection?
The current MyVeridex form uses a server-side bridge rather than a local-terminal download. Account/server and connection-service availability still apply, so inspect actual update status instead of assuming continuous synchronisation.
Does a connected status prove the full history was imported?
No. Reconcile account identity, dates, transaction identifiers, whole-period totals, costs and cash movements. Check gaps and the actual refresh state.
Does every HTML or CSV statement work?
No. MyVeridex imports supported MT4/MT5 closed-trade schemas in HTML, XLSX and CSV. An extension alone does not prove compatibility, and closed-trade reconstruction does not recover full historical floating equity.
Review your trading history
Use MyVeridex trading analytics to review and share an imported trading history. Check connection support and metric definitions for your account.
Start Free 7-Day Trial