Inside PMTS: How Real-Time Data Synchronization Between MetaTrader 5 and the Dashboard Works

For a capital allocator evaluating a managed trading program, the single most important question is rarely how high are the returns. It is can I trust the numbers. A performance figure is only as credible as the pipeline that produces it. At PMTS, that pipeline begins inside MetaTrader 5 at the moment a trade is executed and ends, seconds later, on the screen of an investor reviewing their dashboard. This article walks through how that synchronization works, why the architecture was designed the way it was, and what it means for the integrity of the numbers you see. The date of writing is June 26, 2026.

The synchronization problem in managed trading

Most retail trading dashboards are built on a simple but fragile assumption: that a periodic snapshot of an account is good enough. A cron job queries the broker once an hour, writes a row to a database, and the front end reads from that row. The problem is that markets do not wait for cron schedules. Between two snapshots, a position can open, run, and close; equity can swing; a drawdown can appear and recover. If the dashboard only sees the endpoints, it tells a smoothed, lossy story that omits exactly the information a serious allocator needs to assess risk.

The PMTS design rejects the periodic-snapshot model as the source of truth. Instead, the platform treats the MetaTrader 5 terminal as a continuously emitting event source and builds the dashboard on top of a layered ingestion pipeline that captures deals, orders, positions, and account state as they change. The result is a record that is granular enough to reconstruct the account's history trade by trade, not just day by day.

Architecture: from MT5 execution to dashboard render

The pipeline has three distinct layers, each with a single responsibility. Keeping them separate is what makes the system both fast and auditable.

The MT5 DataSync Expert Advisor

The first layer lives inside the trading terminal itself. PMTS deploys a dedicated DataSync Expert Advisor — an MT5 program written in MQL5 — that runs alongside the trading logic. Its only job is observation and transmission. On every relevant terminal event — a deal closing, an order filling, a position updating, or simply the passage of a heartbeat interval — the Expert Advisor serializes the current state of the account and pushes it to the PMTS ingestion API over an authenticated channel. Because the Expert Advisor reads directly from the terminal's own trade history and account functions, the data it sends is the broker's record, not a reconstruction. There is no manual entry, no spreadsheet, and no opportunity for the figures to drift from what actually happened in the market.

The ingestion API and the snapshot model

The second layer is the server-side REST API that receives those transmissions. Each payload is authenticated with a per-account API key carried in an X-API-Key header and validated against the database before a single byte is written. Once validated, the API decomposes the payload into the platform's normalized data model: individual deals, orders, and positions are written to their own tables, while a rolling series of account snapshots captures balance, equity, margin, free margin, and floating profit and loss at each sync point. A separate equity-curve series records the account's value over time at high resolution.

This separation matters. The deal-level tables provide the immutable, append-only audit trail — the ground truth of every fill. The snapshot and equity-curve series provide the time-resolved view that powers charts and risk metrics. Because both are derived from the same authenticated stream, they can never disagree: the aggregate statistics on the dashboard are always reconcilable back to the underlying deals that produced them.

The dashboard layer

The third layer is what the investor actually sees. The PMTS dashboard is a single-page application that reads from the normalized model through the user API, converts every figure into the investor's preferred display currency, and renders the result with live charts. It does not talk to MetaTrader 5 directly — it never needs to, because the ingestion pipeline has already done the work of capturing and structuring the data. The dashboard's job is presentation and interpretation: equity curves, win-rate and profit-factor breakdowns, drawdown analysis, and per-position detail, all refreshed as new syncs arrive. You can see this layer in action on your own investor dashboard.

What gets synchronized, and how often

The pipeline synchronizes four categories of data. First, completed deals — every fill, with its price, volume, profit, swap, and timestamp — which form the permanent performance record. Second, open positions, so the dashboard reflects live exposure, including floating profit and loss, stop levels, and the symbol and direction of every active trade. Third, account state — balance, equity, margin level, and free margin — captured as snapshots. Fourth, derived statistics, which the server recomputes from the underlying deals rather than trusting any pre-aggregated number from the terminal.

Sync frequency is event-driven rather than fixed. A quiet account with no open positions may transmit only on its heartbeat interval; an active account working multiple positions through a volatile session transmits far more often, because every meaningful change is an event. This is the opposite of the hourly-cron model: the system spends its bandwidth precisely when there is something worth recording.

Why this matters: verifiable performance

The entire point of this architecture is that the headline numbers are not marketing — they are the arithmetic output of an auditable trade ledger. As of the most recent synchronization, the reference PMTS account shows a win rate of 90.41% across 73 trades — 66 winning and 7 losing — with a profit factor of 10.0557 and a Sharpe ratio of 12.03. Over the tracked period, from July 21, 2025 through June 25, 2026 across 155 trading days, the account produced a total return of 17.70%, turning a $50,000 initial deposit into $58,849.31 of equity, a net profit of $8,849.31. Critically, this was achieved with a maximum drawdown of just 0.41%, or $202.74 in absolute terms.

What makes those figures meaningful is not their magnitude but their provenance. Every one of them can be traced back through the snapshot series to the individual deals captured directly from MetaTrader 5. The Sharpe ratio is computed from the same equity curve the dashboard plots; the profit factor is the literal ratio of gross profit to gross loss recorded in the deal table; the drawdown is measured against the high-water mark of the synchronized equity series. There is no separate, polished number living in a brochure that cannot be reconciled with the data behind the login.

Multi-currency and multi-account handling

A further consequence of the layered design is clean handling of heterogeneity. PMTS-connected accounts run across multiple brokers and base currencies — EUR, USD, and others — at different leverage settings. The ingestion layer stores every amount in the native currency of the account that produced it, preserving fidelity to the broker's books. Conversion happens only at the presentation layer, where the dashboard translates figures into each investor's chosen display currency using cached exchange rates. This means the audit trail is never distorted by currency math, while each investor still sees a coherent, single-currency view of their position.

Transparency as a design principle

It would be simpler, and cheaper, to build a dashboard that shows curated figures. PMTS deliberately did not. The decision to anchor every displayed number to an authenticated, deal-level stream from MetaTrader 5 is a statement about what managed trading should be: a relationship in which the manager and the investor look at the same ground truth. The synchronization pipeline is, in that sense, less a feature than a commitment — the technical expression of an institutional standard for transparency.

For allocators evaluating systematic programs, this is the layer worth scrutinizing first. Returns can be impressive for many reasons, some of them durable and some not. A pipeline that makes those returns continuously verifiable, trade by trade, is what separates a track record you can underwrite from one you simply have to believe. If you want to examine the live data for yourself, you can create an account and review the synchronized performance directly.

Past performance does not guarantee future results. Trading involves substantial risk of loss and is not suitable for every investor. The figures cited reflect a specific reference account over a defined period and should not be interpreted as a promise of comparable returns.