Crypto alerts dashboard
Every alert you have set sits in one filterable list: type, coin, exchange, condition, channel, status. A second tab holds the trigger history: what fired, when, which channel it went to, and whether the notification was delivered.
All your alerts in one list
The alerts tab collects every alert into a single list and answers three questions: what it is watching, where it will notify you, and whether it is still active.
- Filter by type. Every alert type is in the dropdown: price, percentage, momentum, RSI, MACD, volume, wick, market cap, multi-condition, the four funding-rate types and the rest.
- Filter by status. Active, Paused, Completed and Expired each have a tab. The header counts your alerts, how many are active and how many fired today, so you always know how much of your free-plan allowance is spoken for.
- The condition, in words. Each row spells out what the alert is waiting for rather than showing a raw parameter dump, with the coin, the venue, and the delivery channel beside it.
- Bookmarkable views. Search, type, status and page all live in the URL, so the view you check every morning is one saved link.
- BTC/USDTActive
Price · above 105,000 · Binance · → Telegram
- ETH/USDTActive
RSI · RSI(14) below 30 · 4h · → Email
- SOL/USDTActive
Percentage · down 5% in 15m · → Discord
- Any CoinPaused
Volume · all USDT pairs · volume spike · → Webhook
- AVAXCompleted
FR Spread · spread above 0.05% · cross-venue · → Telegram
Filter by any of 25 alert types · free plan: 5 active
Trigger history and delivery status
The history tab records two things separately: the trigger, and the delivery outcome of the notification it produced.
- Delivery status per event. Sent, failed or pending. Sent is written only once the send succeeds, not when the message is handed to the queue.
- The error message. A failed row shows the underlying reason inline, so a revoked Discord webhook or a bouncing mailbox is visible instead of silent.
- The numbers behind the trigger. Price at trigger against the target you set, or the percentage move that qualified, alongside the coin, exchange and timestamp.
- It outlives the alert. Deleting an alert de-links its history rows rather than destroying them, so the record of what was sent to you stays intact.
- 14:02:11BTC ▲ 105,140Sent
Price · target 105,000 · Binance · Telegram
- 13:47:03SOL ▼ 5.4%Failed
Percentage · 15m window · Discord
webhook returned 401
- 12:15:00ETH RSI 28.6Sent
RSI · 4h close · Email
- 11:58:42AVAX funding 0.061%Pending
FR Threshold · Bybit · Webhook
Sent means the send succeeded, not that it was queued.
How to manage your crypto price alerts
- 01Find the alertSearch by coin or exchange, pick an alert type from the type filter, and open the Active, Paused, Completed or Expired tab. The list narrows as you go and the count tells you how many of your alerts matched.
- 02Read the rowEach row states the condition in plain language (above 105,000 on Binance, RSI(14) below 30 on the 4h) next to the channel it will use and its current status. Any-coin scanner alerts read as Any Coin with the quote they track, so a market-wide alert never hides behind a single ticker.
- 03Check what it actually didSwitch to Trigger History for the firing record: when it fired, the price at trigger against the target you set, the channel, and whether the notification was delivered or failed. Filter that tab by delivery status when you are chasing a message that never arrived.
- 04Prune, export, or start againDelete a spent alert from its row to free a slot, or clear an entire alert type in one action. Export either tab to CSV when you want the record outside the app; the history export includes the error text on every failed send.
One-shot and recurring alerts
On most single-coin alerts, you decide which when you create it. Tick disable after first trigger and it fires once, marks itself completed, and stops. Leave it unticked and it keeps working: a price alert in crossing mode sends one message per cross, then re-arms as soon as price returns to the other side of your level: one alert per crossing, not a stream while it sits there.
This matters for your allowance. The free-plan cap counts alerts in the active state, so a completed one-shot hands its slot straight back. See what the free plan includes.
- 01
Active
Armed and watching. A recurring alert that has already fired stays active and keeps watching for the next one. This is the state the 5-active-alert free-plan cap counts.
- 02
Completed
A one-shot alert that has fired and switched itself off. Its slot is free again.
- 03
Expired
The alert ended without firing, as with percentage alerts that have a fixed time window.
- 04
Paused
CoinBeacon is not checking it: you paused it, its notification channel stopped working and there was no verified email to move it to, the account was suspended, or a one-time alert's message could not be delivered. Resume switches it back on if you have a free slot.
Common uses
Auditing a channel that went quiet
Filter the history to failed and you learn in one look whether the silence was the market or a broken route. Each of the six delivery channels (email, push notifications, Telegram, Discord, Slack, webhook) reports its own outcome per event.
Freeing a slot before you set the next alert
Five active alerts is the free-plan limit, and only active ones count: completed and expired alerts have already given their slot back. Open the Active tab, delete the alerts you no longer need, and set the next one.
Checking which alerts fire most
Filter the trigger history by type to see which alerts fire most. If an alert fires more often than is useful, a wider threshold or a longer cooldown reduces it.
Reconstructing a move after the fact
Timestamped trigger rows put your own alerts on the same timeline as the day. Read them next to the markets overview or the signal terminal (both browsable without an account) to see what happened around them.
Alerts dashboard FAQ
- What does the CoinBeacon crypto alerts dashboard show?
- Two tabs. My Alerts is every alert you have set, one row each: type, coin, exchange, the condition in plain language, the channel it will use, its status, and the date you created it. Trigger History is the record of what already fired: timestamp, the numbers behind the trigger, the channel it went to, and whether the message was delivered. A counter at the top keeps the running total, how many are active, and how many fired today.
- How do I manage my crypto price alerts after I set them?
- Filter the list down and act on what you find. Search by coin or exchange, narrow by alert type, and switch between the All, Active, Paused, Completed and Expired tabs. Delete a single alert from its row, or clear a whole type at once. The filter set lives in the URL, so a view you check often is just a bookmark.
- Can I see a history of the crypto alerts that already fired?
- Yes. That is the Trigger History tab, a separate record from the alert itself. Each row carries the exact trigger time, the alert type, the coin and exchange, the numbers involved (the price at trigger against the target you set, or the percentage move that qualified), the delivery channel, and the outcome. Filter it by type and by delivery status, or search a single coin.
- How do I know whether an alert notification was actually delivered?
- Every history row carries a delivery status of its own: sent, failed, or pending. Sent means the message left for your channel and the send succeeded, not merely that it was queued. Failed rows show the underlying error inline, so a Discord webhook you revoked or a mailbox that bounced reads as a broken route instead of a silent gap in your alerts.
- How many crypto alerts can I keep armed at once for free?
- Five active alerts and 10 notifications a day, across all six delivery channels and every alert type. The cap counts alerts in the active state, so an alert that has finished no longer occupies a slot; delete or complete one and the slot comes back immediately.
- What do Active, Completed, Expired and Paused mean?
- Active means the alert is armed and can fire again; a recurring alert that has already fired stays active. Completed means a one-time alert has fired and will not fire again. Expired means it ended without firing, as when a percentage alert's time window runs out. Paused means CoinBeacon is not checking it: you paused it, its notification channel stopped working and there was no verified email to move it to, the account was suspended, or a one-time alert's message could not be delivered, so it has not finished. Resume switches it back on if you have a free slot. Each state has its own tab.
- Does an alert stop after it fires, or does it keep watching?
- On most single-coin alerts, that is your choice at creation time. Tick disable after first trigger and the alert fires once and marks itself completed. Leave it unticked and it keeps watching: a price alert in crossing mode sends one message per cross, then re-arms the moment price returns to the other side of your level, so it never repeats while price sits past the level. If price chops back and forth across it, each new cross in the direction you picked can send another message, up to your daily limit.
- Can I export my crypto alert history?
- Yes. Both tabs export to CSV. The alerts export carries the full definition of each alert: type, coin, exchange, condition, target, channel, status, total sent, and the created and triggered timestamps. The history export adds the delivery status and the error text on any failed send, which is what you want when you are reconciling a day of alerts against what actually landed.
More ways to watch the market
All features →- 01Market overview: Movers, volume, funding and liquidations on one screen
- 02Crypto narratives: Which sectors are actually leading today
- 03Live signals: Pumps, dumps and scored setups as they fire
- 04Command center: Market regime, dominance and Fear & Greed at a glance
- 05Key levels: Pivots, Fibs, round numbers & prior ATH/ATL
- 06Volume analysis: Spikes, level crosses, possible exhaustion & dry-ups