Why read-only sync matters
MetaTrader integrations fail trust tests when they request trading or withdrawal permissions. FXTradeJournal uses read-only API access so your terminal workflow stays identical while executions copy into a structured journal.
That model matches what institutional reporting tools use: observe history, never act on behalf of the trader. Credentials are stored per workspace with encryption and can be revoked instantly from account settings.
Latency and data fidelity
Sync runs near real time for fills, fees, and swaps so end-of-day reviews reflect the same numbers you saw on the terminal. Partial closes and multi-leg exits are preserved with enough detail for post-mortems.
MT4 accounts follow the same pipeline when enabled for your workspace. If your broker exposes standard API access, connection steps are identical across brands.
Troubleshooting connection issues
Most connection failures trace to expired investor passwords, API access disabled at the broker, or terminal logged into a different server than the credentials provided. FXTradeJournal surfaces actionable error messages and support articles for each case.
If trades appear delayed, verify terminal connectivity first — sync cannot pull fills while the MetaTrader session is offline. Historical backfill runs after reconnection so gaps close automatically.