Skip to content
Algo Trade Analytics Docs

Data Scope Configuration

The Data Scope section is the first step in your analysis workflow. Here you define the time window for comparison and select where your real-time alert data comes from.

Overview

Section titled “Overview”

This section contains two key configuration areas:

  1. Analysis Time Frame — The date range that scopes your comparison
  2. Alert Data Source — Where your real-time signals come from (webhooks or CSV)

Both must be configured before proceeding to the next workflow step.

Analysis Time Frame

Section titled “Analysis Time Frame”

The date range picker lets you define the exact window of time to analyze.

Date Selection

Section titled “Date Selection”
FieldDescription
Start DateThe beginning of your analysis window
End DateThe end of your analysis window
Start TimeOptional: specific time on the start date
End TimeOptional: specific time on the end date
Section titled “Recommended Date Ranges”
Strategy TypeRecommended RangeReasoning
First-time analysisLast 30 daysEnough data for meaningful patterns
Scalping strategiesLast 7-14 daysRecent behavior is most relevant
Swing strategiesLast 60-90 daysCaptures multiple trade cycles
After code changesSince the change dateIsolate new behavior

Date Range Best Practices

Section titled “Date Range Best Practices”
  1. Match your backtest period — Ensure your date range is covered by both your backtest export AND your alert data
  2. Avoid partial days — Select full calendar days when possible to avoid edge cases
  3. Account for warmup periods — Some strategies need initial bars to calculate indicators; exclude that period

Alert Data Source

Section titled “Alert Data Source”

You must select how to load your real-time alert signals. Choose between two sources:

Using Webhook Data

Section titled “Using Webhook Data”

Best for: Active strategies with webhook integration already configured.

When you select Webhooks:

  • The system automatically queries your webhook event history
  • Alerts are filtered to your selected date range
  • Symbol and strategy info is extracted from webhook payloads

Requirements:

  • Webhook endpoint configured in Webhook Settings
  • TradingView alerts sending data to your webhook URL
  • Alert data exists for the selected date range

Advantages:

  • No manual data preparation
  • Always up-to-date with your latest alerts
  • Timestamp precision down to milliseconds

Completion Criteria

Section titled “Completion Criteria”

The Data Scope step is marked complete (✓) when:

  • A valid date range is selected (both start and end dates)
  • An alert data source is chosen (Webhooks or CSV)
  • If CSV: At least one alert signal is loaded
  • If Webhooks: Date range is confirmed (signals fetch on demand)

Once complete, the Strategy Properties step automatically expands.

Common Issues

Section titled “Common Issues”

”0 signals loaded” with Webhooks

Section titled “”0 signals loaded” with Webhooks”

Cause: No webhook events exist in the selected date range.

Solutions:

  1. Expand your date range to cover when alerts were active
  2. Check your Webhook Configuration is correct
  3. Verify TradingView alerts are set to your webhook URL
  4. Use CSV Import as an alternative

CSV Parse Errors

Section titled “CSV Parse Errors”

Cause: File format doesn’t match expected structure.

Solutions:

  1. Ensure your CSV has column headers in the first row
  2. Check date format matches YYYY-MM-DD HH:MM:SS or similar
  3. Remove any extra columns or formatting
  4. Try pasting the content directly instead of uploading

Date Range Doesn’t Cover Data

Section titled “Date Range Doesn’t Cover Data”

Cause: Selected dates don’t overlap with your backtest or alert data.

Solutions:

  1. Check your backtest CSV for the actual date range of trades
  2. Verify your webhook history covers the selected period
  3. Align the date range with both data sources
Section titled “Related Sections”