Updated .
Can you backtest a crypto price alert?
Yes. You can replay a price-alert rule on stored prices and count how often it would have fired. That count is not a strategy test. A strategy test simulates orders on past data. The replay counts fires and does not place a trade.
What the three checks are
Three checks get called a backtest: a replay count, a strategy test, and the prices stored after a live alert. What the preview shows before you save covers the chart and a short history. How to read a crypto alert receipt covers one alert's later prices.
What a replay counts
On 12 November 2026 the preview help page said the builder checks the rule against stored prices from the last 30 days. You see the 30-day count and the last 7 days. The label reads "Backtest, last 30 days, hypothetical, not a forecast".
Nothing is sent while you preview. Saving turns the alert on. The preview uses the same rules as a live alert and does not say what the price will do next.
The window ends at the start of the current UTC minute and starts 30 days earlier. Every whole minute is one check, with a time and a price. The price after the fire is not shown.
What a strategy test does
On 12 November 2026, TradingView's strategies page said backtesting recreates a strategy on historical data. A strategy can send, modify, execute, and cancel orders and simulate trading on the chart. The Strategy Report has Metrics and a List of Trades, and the report updates with the chart.
TradingView Strategy Report: How to start shows one strategy at a time, on historical data, over a date range you pick.
Strategy alerts names an Add Alert button in the Strategy Tester menu. After calculating on history, the strategy moves to realtime calculations, and an alert fires when the broker emulator executes an order. No notice is sent for orders on historical bars. The alert stops after more than 15 triggers in 3 minutes.
Freqtrade's Backtesting page uses historic candles, a starting balance, a timerange, and a fee applied twice, on trade entry and on trade exit. The test never replaces a dry run.
What other pages say they check
On 12 November 2026 Santiment Academy's whale-activity page, printed "Updated Aug 14, 2025", showed a Whale Transactions example: 79 triggers in three months, which could be excessive, then 21 alerts in a 3-month period.
On Bellchain's MCP docs, an example replays the BTC Dip Buyer on ETH, 1-hour candles, RSI below 30, last 90 days, and creates nothing. replay_chain, replay_template, and replay_price_alert also report fires against exit levels you choose. Alerts cover 90 days. A replay goes as far as the plan allows, and a read-only key can replay.
SmartAlert's home page tests thresholds on the past month for contract events on Ethereum, BNB Chain, Base, and Arbitrum.
Algo Trade Analytics' Backtest vs Alerts page pairs a List of Trades export with webhook events or an alert-history CSV. Those observations do not prove why a difference occurred.
Why a replay and a live check can differ
The replay checks every whole minute. On Free, live checks run about every 5 minutes, so a preview can show a fire a 5-minute check would miss. A 15-minute window on Free says it can miss a move between checks. Paid plans are not open yet.
What a count over 30 means
More than 30 fires in 30 days is more than once a day on average. You can raise the wait, or raise the amount, before you save. Wait, quiet hours, and the daily limit are on Cooldowns, quiet hours, and the daily limit.
What is stored after a live alert
After a live alert, the price is stored at 1 hour, 4 hours, 24 hours, and 7 days. Until that time, the slot says not in yet. Flat and down moves stay. Later prices use the same feed as the alert price. Receipt help says so, and How alert receipts are recorded gives the rules. The Scoreboard counts by rule type, with no account names and no ranking of coins.
On 12 November 2026 the prices page, printed "Updated October 23, 2026", said spot prices come from Coinbase public market data. If Coinbase sends nothing for 30 seconds, Kraken public trades are used for coins Kraken lists, only when Kraken's price is within 5% of Coinbase's last price from the past 10 minutes. When Coinbase has sent again for 20 seconds, Coinbase is used. Receipts use that feed.
Free keeps the history for 7 days. A preview stops at the fire.
Three checks side by side
| Check | Question | Uses | Does not say |
|---|---|---|---|
| Replay count | How often would it have fired? | Stored prices, the live rule, 30 days. | What the price does next. |
| Strategy test | How would simulated orders have come out? | Past data and order rules. The bot page adds a balance and a fee. | That a price alert placed an order. |
| Later prices | What was stored after the alert? | 1 hour, 4 hours, 24 hours, and 7 days. | That the next fire is followed by a move. |
Where you can run the replay before you save
The home try form offers Bitcoin (BTC), Ethereum (ETH), and Solana (SOL), with no account, on the last 30 days. Nothing is sent until you press the button.
On 12 November 2026 the API reference called the preview a 30-day count, said nothing is saved, and required the read scope. Free includes 10 a UTC day on the quotas page, then 2 cents from credits. Packs are on sale only while paid plans are open. Those plans are not open, so a preview past 10 can be refused. The MCP page offers the same count on the read scope. A free account can run it.
Terminal replays a rule on the last 30 days of stored prices before you save and labels that count "Backtest, last 30 days, hypothetical, not a forecast". After a live alert it records the price at 1 hour, 4 hours, 24 hours, and 7 days. It is not investment advice.
FAQ
Does a replay count say what the price does next?
No. It counts past fires on stored prices and stops there. A later price starts only after a live alert.
Can I replay a rule without saving it?
Yes. A preview sends nothing and saves nothing. The home page replays Bitcoin, Ethereum, and Solana with no account.
Is a later-price record the same as a backtest?
No. It stores the price 1 hour, 4 hours, 24 hours, and 7 days after a live alert, and flat and down moves stay on the record. A strategy test simulates orders. A replay only counts fires.
Sources
Opened 2026-11-12 unless a page prints its own date.
- Strategies and backtesting: historical data, orders, report sections.
- Strategy Report how-to: one strategy, a date range.
- Strategy alerts: no notice on historical bars. Stop after 15 in 3 minutes.
- Backtesting: candles, balance, fee, dry run.
- Whale activity alert: "Updated Aug 14, 2025". 79, then 21.
- AI assistants: replays and exit levels.
- SmartAlert: past-month thresholds.
- Backtest vs Alerts: trades against webhook events or a CSV.
- API reference: 30-day count, nothing saved.
- Home: no account. Flat and down kept. Paid plans not open.
- Preview help: both counts and the label.
- Receipt help: four later times. 7 days on Free.
- Where prices come from: Coinbase, then Kraken. "Updated October 23, 2026".
- Quotas: 10 a UTC day on Free, then 2 cents.
- MCP: the count on the read scope.