Skip to content
Algo Trade Analytics Docs

CSV import paths

CSV import is an alternative alert source and a way to load a TradingView Strategy Tester baseline. It does not replace the Alpaca connection used to load broker-reported fills.

Choose the workflow first

Section titled “Choose the workflow first”
WorkflowCSV inputOther source
Backtest vs Alerts All plansA TradingView Strategy Tester → List of Trades export, plus either an alert-history CSV or captured webhooksNo broker connection is required for the comparison itself
Alerts vs Fills Basic or ProfessionalAn alert CSV can replace captured webhooksFill records are loaded from the selected Alpaca connection

Do not upload an account statement or broker fill export into an alert CSV control. The Alerts vs Fills page retrieves the supported fill records from Alpaca for the selected account and window.

Backtest vs Alerts imports

Section titled “Backtest vs Alerts imports”

  1. Export List of Trades from TradingView Strategy Tester. Keep the original file unchanged.

  2. Open Backtest vs Alerts. Under Data Scope, choose CSV, select the timezone that produced timestamps without an offset, open Upload File, and choose the alert CSV.

  3. Under Backtesting Results, choose the baseline CSV timezone and upload the List of Trades file.

  4. Confirm the parsed counts, time range, entry/exit direction, and warnings for both sources before running the comparison.

The importers detect supported TradingView-style headers. There is no manual schema-mapping step in the current page. Rows missing a usable timestamp or event type can be skipped and reported; read the import summary rather than assuming a successful file selection means every row was accepted.

Use the Backtesting Upload reference for exact accepted timestamp, type, direction, price, and optional-column behavior. Use Data Scope for the alert CSV rules.

Alerts vs Fills alert import

Section titled “Alerts vs Fills alert import”

  1. Open Alerts vs Fills and select the Alpaca connection, symbol, and bounded time window.

  2. Choose CSV as the TradingView source, select the timestamp timezone, and upload the supported alert export.

  3. Confirm the alert count and source range, then let the page load Alpaca fills for the same scope.

  4. Check both source counts before interpreting full, partial, or unmatched groups.

CSV timestamps with minute-level precision receive a minimum 60-second matching window in Alerts vs Fills. That parser behavior does not make 60 seconds a recommended tolerance for every strategy.

Test the importer without private data

Section titled “Test the importer without private data”

The Backtest vs Alerts quick start provides a parser-tested sample baseline and sample alerts. Use them to confirm the workflow before diagnosing a private export.