Audit & import help

Execution Leak Audit (paste)

Paste comma-separated rows: Date, Time, Symbol, Side, Qty, P&L. Preview the parsed trades, submit one session, and receive an execution audit. Save later audits to measure whether a pattern recurs. No account is required to try the guest route.

Run Execution Leak Audit · public, browser session only until you create an account

Broker history import (optional)

Supported broker CSV upload and Tradovate sync populate trade history for Dashboard and Review. Use this optional route when you want multiple sessions for longer-range measurement; it is not required before receiving a one-session audit.

Open broker import · requires sign-in

Supported broker sources (CSV / sync)

• Tradovate: in-app connect and scheduled sync, or CSV import.
• NinjaTrader: CSV import.
• AMP / Rithmic: CSV import.
• AMP / CQG: CSV import.
• AMP / TT (Trading Technologies): CSV import.
• Interactive Brokers (IBKR): CSV import.

Tradovate sync vs CSV

Export and file prep tips

• Export fills/executions or closed-trade history from a supported broker platform.
• Prefer files with realized PnL per row; they map most reliably to discipline cost analysis.
• Keep date/time columns intact (date + time or full timestamp).
• Do not remove core columns such as symbol, side, quantity, price, and timestamp.

Export layouts vary. Use the matching in-app broker guide and preview mapping; arbitrary CSV formats are not guaranteed to parse.

Why rows may be skipped (broker import)

• Missing required fields (for example symbol, side, size, price, or time).
• Non-trade ledger rows mixed into export (deposits, transfers, interest, fees-only lines).
• Timestamp parsing failures from malformed or inconsistent date/time formats.
• Duplicates already present in your trade history.

Timestamp and timezone notes

Imports rely on parseable trade timestamps. Include full date and time values in your export, and keep one consistent timezone convention across the file. Mixed or partial timestamps are a common cause of skipped rows.

Current import limitations

• Non-trade filtering is conservative and may depend on broker export wording.
• Duplicate matching is strict and may preserve broker-specific split fills as separate rows.
• Timestamps need an explicit offset, timezone, Z/UTC, or selected file timezone.
• If a file cannot be detected confidently, choose the source manually.

If import still fails, send this to support

• Broker/platform name and whether you used Tradovate sync or CSV.
• Date range of the export and timezone used in the file.
• CSV header row plus 5-10 sample rows (sensitive fields redacted).
• Screenshot of preview skip reasons from the import screen.