Strategy Properties

The Strategy Properties section identifies your strategy for analysis tracking and reporting. This context helps the system accurately match signals and provides meaningful labels in your reports.

---

Overview

Strategy identification serves three purposes:

1. Signal Matching — Filters alerts to only those from your target strategy
2. Report Labeling — Names your analysis for easy identification
3. AI Context — Provides background for AI-powered insights

---

Configuration Options

How you configure strategy properties depends on your alert data source:

Using Webhooks

Auto-Population from Webhooks

When you selected Webhooks as your data source, strategy and symbol information is automatically extracted from your webhook payloads.

Strategy Dropdown:

• Lists all unique strategy names found in your webhook data
• Select the strategy you want to analyze
• Multi-strategy users: filter to one strategy at a time

Symbol Dropdown:

• Lists all symbols associated with the selected strategy
• For single-symbol strategies, this auto-fills
• For multi-symbol strategies, select your target

Tip

Consistent naming matters. If your TradingView alerts use different strategy names (e.g., “MA Cross” vs “MA Crossover”), they’ll appear as separate entries. Standardize your alert messages for cleaner analysis.

Using CSV

Manual Entry for CSV

When using CSV Import, you’ll manually enter your strategy details:

Strategy Name:

• Enter a descriptive name for your strategy
• Examples: RSI Mean Reversion v2.1, MACD Crossover, Breakout Scanner
• This becomes the label for your analysis reports

Symbol:

• Enter the exact ticker symbol
• Match the format used in your data (e.g., TSLA or NASDAQ:TSLA)
• Case-insensitive, but consistency helps

Note

The strategy name you enter should match what’s in your backtest and alert CSVs for accurate matching.

---

Field Reference

Field	Required	Description	Example
Strategy Name	✅	Identifier for your trading strategy	MA Crossover v2.1
Symbol	✅	Trading instrument ticker	TSLA

---

Strategy Properties Upload (Legacy)

Caution

Note: TradingView has removed the Strategy Properties CSV export feature from recent versions. This section is for historical reference and users on older TradingView versions.

Previously, TradingView allowed exporting a “Strategy Properties” file containing:

• Strategy settings (inputs, parameters)
• Timeframe configuration
• Commission and slippage settings
• Entry/exit rules metadata

If you have this file:

1. Click the upload zone in the Strategy Properties section
2. Upload the CSV file
3. Fields auto-populate from the file contents

Extracted properties:

• Strategy name and version
• Chart timeframe (e.g., 1H, 4H, 1D)
• Symbol information
• Raw configuration parameters

---

Best Practices

Naming Conventions

Use consistent, descriptive names:

✅ Good	❌ Avoid
RSI_MeanReversion_v2.1_TSLA	Strategy 1
MACD_Crossover_15min	test
Breakout_Scanner_Crypto	my strat

Symbol Formatting

Match the format used in your data sources:

Source	Format
TradingView US Stocks	NASDAQ:AAPL or NYSE:IBM
TradingView Crypto	BINANCE:BTCUSDT
Alpaca Trades	AAPL, TSLA (no exchange prefix)

Tip

When in doubt, check your webhook payloads or CSV files to see exactly how symbols appear.

---

Completion Criteria

The Strategy Properties step is marked complete (✓) when:

• Strategy Name is entered (not empty)
• Symbol is entered (not empty)

Both fields can be satisfied by either:

• Webhook auto-population + manual selection, OR
• Direct manual entry

Once complete, the Backtesting Results step automatically expands.

---

Common Issues

Webhooks Show No Strategies

Cause: No webhook events exist for the selected date range, or payloads don’t contain strategy info.

Solutions:

1. Expand your date range in the Data Scope step
2. Check your webhook Payload Standard includes strategy field
3. Switch to CSV Import and enter manually

Symbol Mismatch Warnings

Cause: The symbol in your strategy properties doesn’t match your backtest or alert data.

Solutions:

1. Check exact formatting (case, exchange prefix)
2. Ensure consistency across all data sources
3. Use the exact symbol shown in your CSV files

Multi-Symbol Strategies

Cause: Your strategy trades multiple instruments.

Solutions:

1. Run separate analyses for each symbol
2. Select one symbol at a time from the dropdown
3. Compare results across symbols to identify inconsistencies

---

Related Sections

• Data Scope — Previous step: configure date range
• Backtesting Upload — Next step: import trade data
• Payload Standard — Webhook message format reference