Skip to content

Knowledge Base & FAQ

Find quick answers to the most common questions about Algo Trade Analytics. If you can’t find what you’re looking for, contact our support team.

1. Webhook Integration Problems (#1 Support Issue)

Section titled “1. Webhook Integration Problems (#1 Support Issue)”

❓ My webhook isn’t receiving signals from TradingView

Section titled “❓ My webhook isn’t receiving signals from TradingView”

Check these first:

  1. Webhook URL: Copy exact URL from Algo Trade Analytics webhook management
  2. auth_key: Ensure it’s included in your JSON payload
  3. Alert Status: Verify TradingView alert is active and not expired
  4. JSON Format: Validate JSON syntax using online JSON validator

Quick Test:

Terminal window
curl -X POST https://algo-trade-analytics.com/api/webhooks/YOUR_WEBHOOK_ID \
-H "Content-Type: application/json" \
-d '{"auth_key":"YOUR_AUTH_KEY","ticker":"AAPL","direction":"long","marketPrice":150.00}'

❓ Getting “Rate Limit Exceeded” errors

Section titled “❓ Getting “Rate Limit Exceeded” errors”

Cause: Algo Trade Analytics limits webhooks to 30 requests per minute (not built for HFT)

Solutions:

  • Reduce signal frequency in your strategy
  • Combine multiple signals into single webhook call
  • Use CSV import for bulk historical data instead

❓ How do I set up dual webhooks (execution + analytics)?

Section titled “❓ How do I set up dual webhooks (execution + analytics)?”

The dual webhook pattern (most effective setup):

  1. Execution Webhook → TraderPost/Alpaca (for trading)
  2. Analytics Webhook → Algo Trade Analytics (for analysis)

Pine Script Example:

if longCondition
// 1. Execution webhook
alert('{"ticker":"' + syminfo.ticker + '","action":"buy","qty":100}')
// 2. Analytics webhook
alert('{"auth_key":"YOUR_KEY","ticker":"' + syminfo.ticker + '","direction":"long","marketPrice":' + str.tostring(close) + '}')

See: Complete Webhook Integration Guide


❓ CSV import fails with “Invalid format” error

Section titled “❓ CSV import fails with “Invalid format” error”

Most common causes:

  1. TradingView format changes: TV updates their CSV format occasionally
  2. Missing columns: Required fields: ticker, action, price, time
  3. Date format: Must be ISO 8601 (YYYY-MM-DDTHH:mm:ssZ)
  4. Symbol naming: Use “AAPL” not “NASDAQ:AAPL”

Solution: If TradingView changed their format, contact support. We’ll update the import parser within 24-48 hours.

❓ Imported signals don’t match my TradingView alerts

Section titled “❓ Imported signals don’t match my TradingView alerts”

Check these:

  • Timezone settings match between TV and Algo Trade Analytics
  • Alert frequency set to “Once Per Bar Close”
  • CSV export includes all your alerts (not filtered)
  • Time range covers your expected period

See: CSV Export & Import Guide


❓ My live trading doesn’t match TradingView backtest

Section titled “❓ My live trading doesn’t match TradingView backtest”

This is THE most common frustration. Causes:

  1. calc_on_every_tick=false: Signals only fire at bar close
  2. Magnifier disabled: Missing intrabar price action
  3. Perfect fill assumptions: Backtests assume zero slippage
  4. Network delays: Real execution has latency

Solutions:

  • Set calc_on_every_tick=true for live strategies
  • Enable magnifier checkbox in chart settings
  • Test in paper trading before going live
  • Add realistic slippage simulation

See: Strategy Configuration Guide

❓ Should I use calc_on_every_tick=true or false?

Section titled “❓ Should I use calc_on_every_tick=true or false?”

For live trading: ALWAYS use true

  • calc_on_every_tick=true: Real-time signals, better fills
  • calc_on_every_tick=false: Signals only at bar close (major delay)

Trade-off: Real-time calculation is slower and noisier, but essential for live trading.


Currently: Yes (manual API setup required) Future: No (Alpaca Connect integration planned)

Current Setup:

  1. Get Alpaca API keys from your Alpaca account
  2. Add them to Algo Trade Analytics settings
  3. Enable read-only permissions (we don’t execute trades)

Future Plan: Direct Alpaca Connect integration - no manual API setup needed.

❓ Can Algo Trade Analytics execute trades directly?

Section titled “❓ Can Algo Trade Analytics execute trades directly?”

No. Algo Trade Analytics is for analytics only, not trade execution.

For trade execution, use:

  • TraderPost → Alpaca
  • Direct broker API integration
  • Other execution platforms

Algo Trade Analytics focuses on: Signal analysis, execution monitoring, performance comparison.

Check these:

  1. API Keys: Correct keys with read permissions
  2. Paper vs Live: Make sure you’re using the right account type
  3. Date Range: Trades within selected time period
  4. Symbol Filter: No symbol filters blocking your trades

❓ Exported Pine Script shows no markers on chart

Section titled “❓ Exported Pine Script shows no markers on chart”

Most common causes:

  1. Symbol mismatch: Chart symbol differs from exported data
  2. Timeframe mismatch: Wrong chart timeframe
  3. Date range: No trades in visible chart period
  4. Timezone differences: Marker times don’t align

Quick fixes:

  • Ensure chart symbol exactly matches export symbol
  • Check chart timeframe matches your trading timeframe
  • Verify date range includes your trades

Template: No, the export template is fixed Generated code: Yes, freely modify after export

You can customize:

  • Marker colors and shapes
  • Performance table position
  • Additional indicators
  • Custom labels and alerts

See: Pine Script Export Guide


Algo Trade Analytics Limits (intentionally conservative):

  • Webhooks: 30 requests/minute
  • API calls: 100 requests/15 minutes
  • Auth requests: 10 requests/15 minutes

If you hit limits:

  • Wait for the time window to reset
  • Optimize webhook frequency
  • Use CSV import for bulk data
  • Missing auth_key in webhook payload
  • Incorrect auth key for the webhook
  • Webhook URL copied incorrectly
  • Malformed JSON syntax
  • Missing required fields: auth_key, ticker, direction, marketPrice
  • Incorrect data types (price as string instead of number)
  • Use standard symbol format: “AAPL” not “NASDAQ:AAPL”
  • Check for typos in ticker symbols
  • Ensure symbol is supported by your broker
  • Incorrect webhook URL
  • Webhook was deleted
  • URL copied from wrong environment (dev vs prod)

Required Fields for all webhooks:

  • auth_key (string) - Your unique webhook key
  • ticker (string) - Trading symbol (e.g., “AAPL”)
  • direction (string) - “long” or “short”
  • marketPrice (number) - Current market price

Optional Fields (enhance functionality):

  • orderType, qty, stopPrice, limitPrice
  • takeProfit, stopLoss objects
  • metadata object with custom fields

Signal Analysis: Compare TradingView signals vs real execution ✅ Performance Analytics: Detailed trade performance metrics
Execution Monitoring: Track slippage, timing, fill quality ✅ Multi-Platform Comparison: Compare brokers and execution venues ✅ Data Export: Pine Script export back to TradingView ✅ Webhook Processing: Real-time signal capture and analysis

Trade Execution: We don’t place trades (analytics only) ❌ High-Frequency Trading: Not built for HFT or scalping ❌ Portfolio Management: No position management features ❌ Real-time Alerts: No trading alerts or notifications ❌ Social Trading: No copy trading or signal sharing


  1. [ ] Connect Alpaca API (if using Alpaca broker)
  2. [ ] Create first webhook in webhook management
  3. [ ] Test webhook with manual payload
  4. [ ] Set up TradingView strategy with dual webhooks
  5. [ ] Test in paper trading before going live
  6. [ ] Monitor signals in webhook events log
  7. [ ] Analyze performance in analytics dashboard
  8. [ ] Export results to Pine Script for visualization

TradingView Strategy Settings:

  • calc_on_every_tick=true
  • ✅ Magnifier enabled
  • ✅ Alert frequency: “Once Per Bar Close”
  • ✅ Webhook URL configured correctly

Algo Trade Analytics Webhook Settings:

  • ✅ Descriptive webhook name
  • ✅ Auth key securely stored
  • ✅ Webhook status: Active
  • ✅ Event monitoring enabled

Best Practices:

  • Create separate webhooks for each strategy
  • Use descriptive naming conventions
  • Tag strategies with metadata
  • Monitor each strategy’s performance separately

Strategy Level:

  • Use calc_on_every_tick=true for real-time signals
  • Test extensively in paper trading
  • Monitor execution quality metrics
  • Adjust based on real execution data

Platform Level:

  • Monitor webhook delivery success rates
  • Watch for rate limiting issues
  • Regular CSV exports as backup
  • Keep webhook URLs secure

Organization:

  • Export data regularly for backup
  • Use consistent naming for strategies
  • Document strategy changes and versions
  • Keep historical performance records

Privacy & Security:

  • Never share webhook URLs publicly
  • Rotate auth keys if compromised
  • Use read-only API permissions only
  • Monitor for unauthorized webhook calls

Email: support@algo-trade-analytics.com Response Time: 4 hours during business hours

When contacting support, include:

  • Your webhook URL (first 20 characters only)
  • Error messages (exact text)
  • Screenshots of the issue
  • TradingView strategy name
  • Date/time when issue occurred

Documentation: All guides and tutorials Example Strategies: Sample Pine Script code Best Practices: Community-shared configurations

Have an idea for improvement? Submit feature requests through our platform. Popular requests are prioritized for development.


{
"auth_key": "YOUR_AUTH_KEY",
"ticker": "AAPL",
"direction": "long",
"marketPrice": 150.50,
"orderType": "market",
"qty": 100,
"positionIntent": "entryLong"
}
alert('{"auth_key":"YOUR_KEY","ticker":"' + syminfo.ticker + '","direction":"long","marketPrice":' + str.tostring(close) + '}', alert.freq_once_per_bar)
  • calc_on_every_tick=true
  • Magnifier enabled
  • Webhook auth_key correct
  • Alert frequency set correctly
  • Paper trading tested