Skip to content
Algo Trade Analytics Docs

Identify the strategy and symbol

Backtest vs Alerts

In Backtest vs Alerts, the Strategy Properties step asks for two identifiers:

FieldWhat it controls
StrategyLabels the comparison, saved snapshot, and AI context.
SymbolSelects the instrument used for webhook orders and chart data, and labels imported rows.

Both values are required before the step is complete. They do not verify that the two datasets came from the same strategy; you still need to confirm that when reviewing the inputs.

The strategy field suggests names already found in your saved trade orders. You can select a suggestion or type a new name.

After you select or finish typing a strategy, the symbol field suggests symbols associated with it. If none are available, you can type the symbol. The symbol is normalized to uppercase.

Enter a strategy name and symbol manually. Use a name that will make the saved snapshot recognizable, and use the instrument represented by both CSV files.

If the account already contains saved trade orders, the symbol field may offer those symbols as suggestions. You can still type another value.

Use the format expected by the connected market-data or order source. A webhook history may use a broker symbol such as AAPL, while another source may include an exchange-qualified identifier. Do not assume two visually similar formats will be treated as the same instrument.

When the formats differ:

  1. inspect the symbol in the alert rows or saved orders;
  2. inspect the instrument represented by the TradingView export; and
  3. choose the value appropriate for the comparison and any chart-data request.

The product does not currently expose a Strategy Properties CSV uploader. Strategy name and symbol are configured in the two visible fields. Older saved snapshots may still contain additional strategy properties, but a new comparison does not require them.

Confirm that:

  • both fields are non-empty;
  • the symbol matches the instrument in the backtest and alert data;
  • the strategy name clearly distinguishes this configuration from other versions; and
  • the selected date range contains the intended webhook orders when Webhooks is the source.

Then import the TradingView List of Trades CSV. For webhook payload fields, see the Webhook Payload Standard.