How many flight deal emails is too many?

Somewhere in your inbox is a trail of “price alert” emails you stopped reading a while ago. A few you opened out of habit and closed without acting on. Most you did not open at all. That is not a minor annoyance. That is the alert failing at the one job it had.

The real question is not the count

Ask “how many is too many” and the honest answer is not a number, it is a ratio: emails worth opening against emails sent. Three useless alerts a week teach you to skim the fourth, and the fourth might have been the one that mattered. A tool that sends constantly has not necessarily failed. A tool whose emails you stop reading has, regardless of how often it fires.

Flydar is built around that ratio directly, not around a target inbox size. An email exists only because a fare fell clearly below what a route you named normally costs. There is no separate “too many” setting to tune, because the trigger itself is the volume control.

That distinction is worth sitting with, because it points at the actual fix. Cutting volume without improving the ratio just delays the same fatigue by a few weeks.

Where the flood usually comes from

A few ordinary causes account for most of it, and none of them is a malfunction so much as a design choice made somewhere upstream of your inbox.

The trigger is “something changed,” not “something worth acting on.” Most free tracking fires on any meaningful price movement in either direction, which means a fare ticking up a few dollars produces the same email as a real drop. Read enough of those and you stop distinguishing between them, which is the exact judgement the alert was supposed to save you from making. Why your alerts never go off covers this cause in more detail, including why it is usually a setting rather than a bug. Flydar never sends on a rise, and never sends on a fare that is merely lower than yesterday if it is still ordinary for the route.

You are watching more than you remember. Alerts for a trip you already booked, a route you decided against, a city you searched once out of curiosity, all keep mailing you long after the reason for setting them has gone. Nobody prunes these on a schedule, so the pile only grows.

The same trip is covered by more than one alert. One city, several airports, several separate saved searches. Every one of them fires independently for what is, from where you are sitting, a single event. Flydar collapses this at the source: name a city and every airport in it sits under one tracker, so a metro area never quietly becomes three or four separate alert streams.

What a reasonable alert owes you, in principle

Whatever tool you use, three questions are worth asking before deciding the volume itself is the problem.

Does it tell you why it fired? An email that states the fare dropped, and by how much against what the route normally costs, is doing different work than one that just reports a new number. Every Flydar email states both.

Does it distinguish a real change from ordinary drift? A route that moves a few percent every day should not produce a few percent worth of email every day. This is the whole reason Flydar compares a fare against the route’s normal range before deciding whether to speak at all, rather than watching the number move and reporting the movement.

Does it stop mailing you about a trip that is over? A tracker for dates that have passed should not sit there silently doing nothing, and it should not keep firing on a trip you no longer want either. Flydar flags a tracker with passed dates on your dashboard instead of quietly letting it die, so a stale alert is a decision you make, not one that happens to you by default.

An alert that can answer yes to all three earns the right to send often, because everything it sends has already cleared a bar. One that cannot has a volume problem no amount of tuning will fix, because the volume was never the actual defect.

The two-minute check

1. Search your inbox by sender. If most of what comes back is unread, that is the tool, not the routes.
2. Read the last five subject lines. If they read as interchangeable, the trigger is movement rather than meaning.
3. Count the routes still worth watching. Anything for a trip you have booked or abandoned is dead weight, not signal.

If the answer comes back as dead weight, prune it and see whether the volume that remains still feels like too much. Often it does not.

Flydar is built to sit on the right side of that line: not silent, not constant, correct often enough that you keep reading.

An alert that fires constantly and an alert that fires rarely can both be doing their job. The one that has not done its job is the one you stopped opening, whatever the count says.