If you've ever spent hours backtesting a strategy, only to realize you can't pull your TradingView alert history into a spreadsheet, you know the frustration. TradingView dominates charting, but it locks you in when it comes to data portability. There is no "Export Alerts to CSV" button.
For traders who rely on audit trails—whether for tax purposes, strategy optimization, or simply understanding why a bot missed a signal—this lack of native export is a major workflow gap.
But the ecosystem has adapted. In 2026, you don't need a native export button to get your alert data into a structured CSV format. By leveraging webhooks, Google Sheets, and Pine Script, you can build a real-time alert logging pipeline that actually outperforms a manual export.
> About this guide: I'm Lawrence, the writer behind supa.is. Between February and May 2026 I've published 150+ articles on supa.is across crypto and brokerage tooling — including 50+ TradingView-specific guides (recent examples: TradingView Webhook to Google Sheets, Fix TradingView Webhook Duplicates, TradingView Alert Not Triggering). The most-repeated reader question across that TradingView archive is exactly how to build an audit trail for missed alerts, which is why I'm publishing this standardized guide instead of answering one-off.
> Disclosure: This article contains affiliate links. We may earn a commission at no extra cost to you if you sign up for TradingView through our links.
Why You Need an Alert Audit Trail
Why does your alert log matter?
If you are using TradingView purely for visual analysis, you don't need an export. But if you are running automated strategies—connecting TradingView to OKX, Interactive Brokers, or a Telegram bot—your alert log is your only proof of what the system *thought* it was doing.
When a trade goes wrong, you need to answer three questions:
1. Did the alert fire at the right price? 2. Did the webhook payload contain the correct data? 3. Did the execution platform (like OKX) actually receive the signal?Without a CSV log, you are forced to scroll through the TradingView alert history UI, which has a limited window and zero sorting capabilities. You cannot filter by "missed alerts" or "alerts fired on Friday nights." An external CSV log solves this instantly.
Workaround 1: The Webhook-to-Google Sheets Pipeline (Best for Real-Time CSV)
The most robust way to get a CSV export is to bypass the TradingView UI entirely. Log alerts directly into a Google Sheet as they happen, and you have a live, exportable audit trail.
This method requires no paid third-party services like Zapier. You only need a TradingView account (Essential plan or higher for webhooks) and a Google account.
Step 1: Set Up the Google Sheet
1. Create a new Google Sheet. 2. In the first row, set up your headers. For a proper audit trail, I recommend:Timestamp, Symbol, Condition, Price, Direction, Payload.
3. Go to Extensions > Apps Script.
4. Delete the default code and paste the following script:
function doPost(e) {
var sheet = SpreadsheetApp.getActiveSpreadsheet().getActiveSheet();
var data = JSON.parse(e.postData.getDataAsString());
// Extract data from TradingView webhook payload
var timestamp = new Date().toISOString();
var symbol = data.symbol || 'N/A';
var condition = data.condition || 'N/A';
var price = data.price || 'N/A';
var direction = data.direction || 'N/A';
// Append the row
sheet.appendRow([timestamp, symbol, condition, price, direction, JSON.stringify(data)]);
return ContentService.createTextOutput('OK');
}
5. Click Deploy > New Deployment.
6. Select Web App. 7. Set "Who has access" to Anyone. 8. Click Deploy and copy the Web App URL. This is your webhook URL.Step 2: Configure TradingView Alerts
1. Open your chart and set up an alert. 2. In the alert settings, select Webhook URL and paste your Apps Script URL. 3. In the Message field, you can send custom JSON. For example:{
"symbol": "{{ticker}}",
"condition": "Crossed Above",
"price": "{{close}}",
"direction": "Long"
}
4. Click Create.
Every time the alert fires, TradingView sends a POST request to your Google Sheet. The data is logged instantly. When you need your CSV, you simply go to File > Download > Comma-separated values (.csv).
*Note: If you are dealing with high-frequency alerts, Google Apps Script has a rate limit (about 30 executions per minute). For most swing and day trading strategies, this is more than enough. If you are doing HFT, you will need a paid middleware service.*
Workaround 2: Pine Script Table Logging (Best for Visual Audit)
If you don't want to deal with webhooks and external APIs, you can log your alerts directly onto the chart using Pine Script. While this doesn't give you a CSV file, it gives you a visual, scrollable audit trail that lives permanently on your chart until you close it.
Like what you're reading? Try it yourself — this link supports ChartedTrader at no cost to you.
Try TradingView →This is incredibly useful for backtesting. You can see exactly when your strategy would have fired alerts, and compare it against the price action.
Here is a simple Pine Script v5 snippet that logs alert conditions to a table on your chart:
//@version=5
indicator("Alert Logger Table", overlay=true)
// Initialize the table
var table alertLog = table.new(position.top_right, 2, 10, bgcolor=color.new(color.black, 80), border_color=color.gray, border_width=1)
// Update table header every bar
table.cell(alertLog, 0, 0, "Timestamp", text_color=color.white)
table.cell(alertLog, 1, 0, "Condition", text_color=color.white)
// Example condition: EMA Cross
emaFast = ta.ema(close, 9)
emaSlow = ta.ema(close, 21)
longSignal = ta.crossover(emaFast, emaSlow)
shortSignal = ta.crossunder(emaFast, emaSlow)
// Log the signals
if longSignal
table.cell(alertLog, 0, 1, str.tostring(time, "yyyy-MM-dd HH:mm"), text_color=color.green)
table.cell(alertLog, 1, 1, "LONG", text_color=color.green)
if shortSignal
table.cell(alertLog, 0, 1, str.tostring(time, "yyyy-MM-dd HH:mm"), text_color=color.red)
table.cell(alertLog, 1, 1, "SHORT", text_color=color.red)
Add this to your chart and you get a live log of every signal. You can manually transcribe it to a CSV if needed, but for most of us, the visual confirmation is enough to prove the logic is working.
Workaround 3: Browser Extensions (The "Lazy" Method)
If you are not a coder and don't want to set up Google Sheets, there are browser extensions designed specifically to scrape TradingView's alert history.
Extensions like TradingView Alert Logger (available for Chrome and Firefox) inject a small UI directly into the TradingView interface. They capture the alert data as it renders on the screen and give you a "Download CSV" button right in the extension popup.
Pros:- Zero setup. Install and use immediately.
- Works with the free TradingView plan (since it reads the UI, not the API).
- You must be actively logged into TradingView on your desktop for the extension to capture the data.
- If you close your browser, the log is lost unless the extension has cloud sync (most don't).
- Relies on TradingView's UI remaining the same. If TradingView updates their HTML structure, the extension breaks.
Workaround 4: Webhook to Notion or Airtable (Best for Structured Databases)
If you are already using Notion or Airtable for your trading journal, you can pipe your TradingView alerts directly into them. This is similar to the Google Sheets method but gives you a much more powerful database structure.
For example, in Airtable, you can create a "Trades" table and a "Signals" table. When a TradingView alert fires, it creates a record in the "Signals" table. You can then link that signal to the actual trade record when you execute it. This allows you to calculate your "hit rate" by comparing how many alerts fired versus how many trades you actually took.
To set this up:
1. Create an Airtable base with fields forTimestamp, Symbol, Type, and Price.
2. Use a tool like Make.com (formerly Integromat) or Zapier to connect TradingView webhooks to Airtable.
3. Map the JSON fields from TradingView to the Airtable fields.
4. Download the Airtable view as a CSV whenever you need it.
*Note: Make.com and Zapier have free tiers that are usually sufficient for a few hundred alerts a month. If you are a heavy user, the cost of these services might outweigh the benefit, making the Google Sheets method more cost-effective.*
Best Practices for Your Alert CSV
Once you have your CSV file—whether from Google Sheets, Airtable, or a browser extension—how should you structure it for maximum utility?
Here are the columns you should always include:
1. Timestamp (ISO 8601): Always use UTC. If you are trading across multiple timezones, local time will cause confusion.
2. Symbol: The ticker symbol (e.g.,BTCUSDT, EURUSD).
3. Condition: What triggered the alert? (e.g., EMA Cross, RSI Oversold, Price > 50000).
4. Price: The price at which the alert fired.
5. Direction: Long or Short.
6. Payload: The raw JSON string. This is crucial for debugging. If your bot fails to execute a trade, you can look at the raw payload to see if the data was malformed.
By including the raw payload, you protect yourself against future API changes. If TradingView changes their webhook format, your historical data will still contain the exact data that was sent at the time of the alert.
Troubleshooting Common Export Issues
Issue: My Google Sheet is not receiving alerts.- Check your Apps Script deployment. Make sure it's set to "Anyone" has access.
- Check the TradingView alert history. If the alert fired but the sheet didn't update, the issue is with the webhook delivery. You can test your webhook URL using a tool like
webhook.siteto see if TradingView is actually sending the request.
- This is a known TradingView issue, especially with the "Once Per Bar" setting. If you are using "Once Per Bar," TradingView might fire the alert multiple times if the bar closes and reopens rapidly. Set your alerts to "Once Per Bar Close" to prevent this. For a deep dive on this, read our guide on Once Per Bar vs Once Per Bar Close.
- TradingView webhooks can sometimes fail if the server is under heavy load. This is why the "Payload" column is so important. If a row is missing, you won't know why. By logging the raw JSON, you can see if the alert fired but the data was incomplete.
FAQ
Can I export TradingView alerts to CSV on the free plan?
Yes, but not natively. The free plan does not support webhooks. You will need to use the browser extension workaround or the Pine Script table method to log your alerts. Webhooks require at least the Essential plan.Is there a native TradingView API for alert logs?
No. TradingView does not provide a public REST API for users to fetch their alert history. The only way to get alert data out of TradingView in real-time is through webhooks.How far back can I retrieve alert history?
If you are using the TradingView UI, you can only see alerts that fired while your browser tab was open or recently active. If you use the webhook-to-Google Sheets method, your history is only limited by your Google Sheet's storage capacity, which is effectively infinite for most traders.Will the Google Sheets method work for high-frequency trading?
No. Google Apps Script has a rate limit of about 30 executions per minute. If you are firing more than 30 alerts a minute, your sheet will start dropping data. For HFT, you need a dedicated middleware service or a custom server.Can I use this method to log alerts from multiple charts?
Yes. You can use the same Google Sheet webhook URL for multiple charts. Just make sure thesymbol field in your webhook payload is accurate so you can filter by ticker later.
Risk Warning
> Risk Warning: Crypto trading involves substantial risk of loss. Never invest more than you can afford to lose. This is not financial advice. The workarounds described in this article are technical solutions and do not guarantee profit. Always test your webhook pipelines in a paper trading environment before using them with real capital.
Final Thoughts
The lack of a native "Export to CSV" button is a genuine pain point. But you don't have to wait for TradingView to fix it. By piping your alerts into Google Sheets or Airtable, you build an audit trail that actually gives you more control than a native export ever could.
If you are just getting started with webhooks, I highly recommend checking out our guide on TradingView Webhook to Google Sheets for a step-by-step visual walkthrough.