Why doesn’t Strategy Report appear for my TradingView indicator?

Indicators · Pine Script · Strategy Tester
SOURCE-CHECKED FIX Source checked Aug 29, 2026 TradingView documentation ✓
Short answer

Strategy Report does not appear for a normal Pine indicator. The script must be a strategy declared with strategy() and simulate orders before TradingView can generate backtest results.

What you may be seeing

  • Your indicator shows buy and sell signals but no Strategy Report
  • The bottom report panel does not populate for a custom indicator
  • You expected plotted arrows to become historical trades automatically

Most likely causes

  1. The script is declared with indicator() instead of strategy()
  2. Indicators display calculations and signals but do not automatically simulate orders
  3. The script has no strategy order logic

Try this first

  1. Open the script in Pine Editor
  2. Confirm whether it is declared with indicator() or strategy()
  3. If you need a backtest, create a separate strategy version with explicit order rules
  4. Use strategy entry and exit commands that represent the rules you actually want to test
  5. Add the strategy to the chart and open Strategy Report

If that didn’t fix it

  1. Keep the original indicator unchanged and create a separate strategy script for testing
  2. Use the indicator only for visual analysis if you do not need simulated performance results

Verify the fix

A valid strategy version is active on the chart and TradingView opens Strategy Report with simulated trade results.

Why this happens

TradingView’s Strategy Report is generated by strategy scripts, not ordinary indicators. An indicator can plot signals, labels, lines, or buy/sell markers without simulating orders, so those visuals do not automatically create a backtest report.

If you want Strategy Report metrics, the Pine script must be declared with strategy() and use strategy order commands to simulate trades. Converting an indicator into a meaningful strategy also requires explicit entry, exit, sizing, and execution assumptions.

Sources & next steps

Did this fix your problem? Your answer helps us rank fixes by real-world usefulness.
← Back to Resolve