In short
- Configure alerts by frequency first and by threshold second — the number is an output, not an input.
- Four to eight alerts a day is a usable budget for one person. Forty is a live feed you will mute.
- Narrow the universe of coins before you lower the threshold.
- Pick one side of the market per rule; “buys or sells, anything” is not a rule, it is a firehose.
- Revisit thresholds after a volatility regime change — a number set in a quiet week breaks in a loud one.
Ask anyone who has used a crypto alerting app for more than a month and you get the same story. They set it up enthusiastically, chose a threshold that felt significant, got forty notifications on the first volatile day, and turned the whole thing off. The app was not the problem. The configuration method was.
The mistake: configuring by number
“Alert me on trades over $100,000” feels like a decision. It is not — it is a guess about a distribution you have never seen. On BTC/USDT, six-figure trades print continuously. On a mid-cap altcoin, one might happen twice a week. The same number produces a firehose in one market and silence in another, and you have no way to know which until the notifications start.
The fix: configure by frequency
Invert the question. Do not ask “what size is big?”. Ask “how many times a day am I willing to be interrupted?” — then find the threshold that produces that number.
For most people trading their own book alongside a job, the honest answer is somewhere between four and eight a day. Few enough that each one still gets attention; enough that you are not missing whole sessions. Anything above roughly fifteen crosses the line where a notification stops being an event and becomes ambient noise.
Working backwards from a frequency target has a pleasant side effect: it makes the threshold self-calibrating per market. Whatever number produces six alerts a day on that pair is the definition of unusual for that pair, without you needing to know anything about its typical trade size.
Narrow the universe before lowering the number
When a rule fires too often there are two knobs: raise the threshold, or cover fewer coins. Reach for the second one first.
A threshold high enough to keep “every coin on the exchange” quiet is so high that it will never fire on the mid-caps where an early warning is actually worth something. Cut the universe to a watchlist of ten or twenty pairs you would genuinely act on, and you can afford a threshold low enough to be early.
This is also the honest test of a watchlist. If you would not open the chart when the alert fires, the coin does not belong on the list.
One side per rule
“Buys or sells, anything unusual” doubles your notification count and halves the information each one carries. When the phone buzzes you already have to open the app to find out which direction it was.
Split it. A rule for aggressive buying on your favourites, and — if you want it — a separate rule for heavy selling on the majors, with its own threshold and its own sound. Now the notification tells you something before you have looked at it, and you can switch one off without losing the other.
A worked example
Say you follow twelve mid-cap pairs and want roughly six interruptions a day.
- Start with a rule scoped to those twelve pairs, buy side only.
- Set a threshold that looks conservative — something you expect to be too high.
- Check the expected frequency. In Pharos this is shown on the rule before you save it; elsewhere you may have to run it for a day and count.
- Walk the threshold down one step at a time until the estimate lands near six.
- Leave it for a week without touching it.
Step five is the one people skip. A threshold needs a week of ordinary market to reveal whether it was set during an unusually quiet or unusually loud stretch.
Re-tune after a regime change
Volatility is not stationary. A threshold that produced six alerts a day in a flat August will produce thirty in a week when the whole market is moving, and two during the dead stretch that follows. That is not a malfunction — it is the alert correctly reporting that conditions changed.
The practical rule: if a rule has been either silent for several days or noisy for several days, it is telling you to re-tune it. Two minutes with the threshold beats another month of a muted app.
What not to bother alerting on
- Round-number price levels on coins you do not hold. They fire constantly and mean nothing on their own.
- Percentage moves over long windows. By the time a 10%-in-24-hours alert fires, the move is on every chart and every feed.
- Everything, “just in case”. An alert you do not act on trains you to ignore the ones you would have.
Common questions
What is a volume spike alert?
A notification triggered when trading activity on a coin exceeds a level you defined — either a single unusually large trade, or unusual total volume over a short window. It is distinct from a price alert, which fires when the price crosses a level regardless of how much was traded to get there.
How many crypto alerts a day is reasonable?
For one person watching their own positions, roughly four to eight a day keeps each notification worth opening. Above about fifteen a day, most people stop reading them; that is the point at which an alert has become a live feed.
Should I alert on price or on volume?
They answer different questions. A price alert tells you a level you already cared about has been reached. A volume alert tells you something is happening now that you had not planned for. Most people want a small number of both.
Why do my alerts arrive in bursts?
Because volume is bursty. Activity clusters around news, funding times, and the opening hours of large markets, so alerts cluster too. If bursts are the problem rather than the total, add a cooldown per coin instead of raising the threshold.
Pharos turns this into a push
Set one rule — say, buys above 5 BTC on your favourites — and the app tells you how often it will fire before you save it. Then it pushes you the moment it does.
See how Pharos worksWritten by the team building Pharos Trade. We make an alerting tool, not a trading service — nothing here is investment advice, and none of it predicts a price. Figures in examples are illustrative. Last reviewed 2026-08-23.