Transparency

Activity Logs.
Complete Execution Visibility.

Every trade your copier touches generates a timestamped record - from the moment the signal arrives to the millisecond the broker confirms execution. When something goes wrong, you'll know exactly where, when, and why - no guesswork, no silent failures.

copier_debug.log
[14:20:05.0]INFO: Order #183390 copied successfully to [Slave_02] (15ms)
[14:21:05.13]DEBUG: Heartbeat check... Pulse confirmed.
[14:22:05.26]DEBUG: Heartbeat check... Pulse confirmed.
[14:23:05.39]INFO: Order #183393 copied successfully to [Slave_02] (15ms)
[14:24:05.52]DEBUG: Heartbeat check... Pulse confirmed.
[14:25:05.65]ERROR: Rejected by broker "Market Closed" (User error usually)
[14:26:05.78]INFO: Order #183396 copied successfully to [Slave_02] (15ms)
[14:27:05.91]WARN: Slippage detected > 2.0 pips. Executing anyway.
[14:28:05.5]DEBUG: Heartbeat check... Pulse confirmed.
[14:29:05.18]INFO: Order #183399 copied successfully to [Slave_02] (15ms)
[14:210:05.31]ERROR: Rejected by broker "Market Closed" (User error usually)
[14:211:05.44]DEBUG: Heartbeat check... Pulse confirmed.
[14:212:05.57]INFO: Order #1833912 copied successfully to [Slave_02] (15ms)
[14:213:05.70]DEBUG: Heartbeat check... Pulse confirmed.
[14:214:05.83]WARN: Slippage detected > 2.0 pips. Executing anyway.
[14:215:05.96]INFO: Order #1833915 copied successfully to [Slave_02] (15ms)
[14:216:05.10]DEBUG: Heartbeat check... Pulse confirmed.
[14:217:05.23]DEBUG: Heartbeat check... Pulse confirmed.
[14:218:05.36]INFO: Order #1833918 copied successfully to [Slave_02] (15ms)
[14:219:05.49]DEBUG: Heartbeat check... Pulse confirmed.
[14:30:05.0]INFO: Order #183390 copied successfully to [Slave_02] (15ms)
[14:31:05.13]DEBUG: Heartbeat check... Pulse confirmed.
[14:32:05.26]DEBUG: Heartbeat check... Pulse confirmed.
[14:33:05.39]INFO: Order #183393 copied successfully to [Slave_02] (15ms)
[14:34:05.52]DEBUG: Heartbeat check... Pulse confirmed.
[14:35:05.65]ERROR: Rejected by broker "Market Closed" (User error usually)
[14:36:05.78]INFO: Order #183396 copied successfully to [Slave_02] (15ms)
[14:37:05.91]WARN: Slippage detected > 2.0 pips. Executing anyway.
[14:38:05.5]DEBUG: Heartbeat check... Pulse confirmed.
[14:39:05.18]INFO: Order #183399 copied successfully to [Slave_02] (15ms)
[14:310:05.31]ERROR: Rejected by broker "Market Closed" (User error usually)
[14:311:05.44]DEBUG: Heartbeat check... Pulse confirmed.
[14:312:05.57]INFO: Order #1833912 copied successfully to [Slave_02] (15ms)
[14:313:05.70]DEBUG: Heartbeat check... Pulse confirmed.
[14:314:05.83]WARN: Slippage detected > 2.0 pips. Executing anyway.
[14:315:05.96]INFO: Order #1833915 copied successfully to [Slave_02] (15ms)
[14:316:05.10]DEBUG: Heartbeat check... Pulse confirmed.
[14:317:05.23]DEBUG: Heartbeat check... Pulse confirmed.
[14:318:05.36]INFO: Order #1833918 copied successfully to [Slave_02] (15ms)
[14:319:05.49]DEBUG: Heartbeat check... Pulse confirmed.

Latency Analysis

Every execution is timestamped across three checkpoints: signal arrival at our cloud, transformation processing, and broker confirmation. This gives you a precise millisecond-by-millisecond breakdown of where time was spent in your execution chain - whether it was network latency, broker processing delay, or platform overhead.

Error Diagnosis

Broker rejection codes and execution failures are automatically translated into plain-language descriptions. Instead of seeing raw broker error strings, you see a clear explanation of what happened, which account was affected, which order triggered the error, and what the likely cause is - so you can resolve it without digging through broker documentation.

Searchable History

Filter your complete trade log by ticket number, symbol, account, error type, date range, or event category. Whether you're auditing a specific session, investigating a pattern of slippage, or reviewing a week's execution performance, you can isolate exactly the data you need within seconds.

What Our Activity Logs Actually Track

Our activity logging system records every event that occurs across your entire copy trading chain - from the moment a master order is detected to the final broker confirmation on each slave account. This level of detail exists because "silent failures" are the most damaging problem in automated trading. A trade that should have opened, didn't, and neither the system nor the software gave any indication - that scenario costs accounts and erodes confidence. Our logs are designed to make that scenario impossible.

What Is Logged on Every Trade

Every single copy event generates a structured log entry that captures the following data points in sequence. The Signal Arrival Time records the exact timestamp when the master order was detected by our cloud infrastructure. The Transformation Log records any modifications applied to the order - including lot size scaling, symbol remapping, or compliance filters such as news blocking or session restrictions. The Broker Request records the precise API instruction sent to the slave account's broker, including the exact price, volume, and order type submitted. Finally, the Broker Response records the confirmation, rejection, or partial fill returned by the broker, along with the execution price and any slippage measured against the master entry.

Log Retention & Storage

All activity logs are retained for a minimum of 90 days in your dashboard. This covers the full duration of most prop firm challenges and provides sufficient history for performance auditing, dispute resolution, or strategy review. Logs are stored in our cloud infrastructure and are accessible at any time from your dashboard - no downloads required to browse recent history.

Export Formats

Your complete log history can be exported in both CSV and TXT formats directly from the dashboard. CSV exports are structured for easy import into spreadsheet tools for performance analysis, while TXT exports are formatted for submission to brokers or prop firms as execution evidence when disputes arise.

Real-Time Error Alerts

When a rejection or slippage threshold breach occurs, the system flags it immediately in the live log feed with colour-coded severity indicators - INFO, WARN, and ERROR levels - so you can identify critical events at a glance without scrolling through hundreds of routine confirmation entries. Configurable slippage alert thresholds allow you to define what level of deviation triggers a warning, keeping your log feed relevant to your specific risk tolerance.

Who This Is For

Whether you manage one funded account or twenty, having a verifiable, exportable, filterable execution record is the difference between professional account management and hoping for the best. Our activity logs give you the data to be accountable - to yourself, your prop firm, and your clients.

See Every Trade. Know Every Outcome.

Turn on full execution visibility across all your accounts. Real-time logs, exportable history, and instant error diagnostics - all in one dashboard.

View Demo Logs
FAQ

Frequently Asked Questions — Activity Logs