Are flight price alerts worth it? What separates a useful alert from noise

A flight price alert sounds like an obvious win: name a route, get told when the price moves, book at the right moment. In practice many people turn them off within a few weeks, and the reason is worth understanding before you set one up — ours included.

The problem with "the price changed"

The most common kind of alert tells you a fare went up or down since you last looked. Fares move all the time, for reasons that have nothing to do with whether they are good — seats in one fare bucket sell, another opens, a cache refreshes. We go through the mechanics in the "searching raises the price" myth.

So an alert that fires on movement fires constantly. A $14 drop is technically news. So is a $9 rise the next day. After a dozen of those, the email that matters arrives looking exactly like the eleven that didn't, and it goes unread. An alert that cries wolf is worse than none, because it teaches you to ignore the one time it's right.

What a useful alert has to answer

The question you actually have is not "did it move?" but "is this fare good, and should I book it now?" That needs three things a movement alert doesn't have:

1. A like-for-like comparison. "Good" only means something against fares for the same route, the same time of year and the same distance from departure. A fare compared against a broad average almost always looks like a deal — more on that in what "26% below typical" means.
2. A sense of timing. A fair price four months out and the same price four days out are different situations. Whether the route's fares have started to climb yet is part of the answer.
3. The willingness to say nothing. Without enough recorded history, the honest answer is "we don't know yet." An alert service that always has an opinion is guessing some of the time, and it won't tell you which times.

What to look for when you pick one

• Does it say what it compares against? If an alert says "great price" without saying great compared to what, assume the comparison flatters the fare.
• Does it send on a threshold or on a schedule? A weekly digest is a newsletter. An alert should arrive when something is worth acting on, and not otherwise.
• Does it ever refuse? A service that will score any route you type, from day one, has to be filling the gap with something.
• Is the price it quotes the price you'll pay? Most fare data is the lowest advertised fare, with bags and seat selection extra. That's fine if the alert says so; it's a problem if you find out at checkout.
• Who benefits from the recommendation? If the service earns more from some bookings than others, ask whether that can reach the advice.

How we built ours around those answers

For transparency, here is how PriceHash answers each of those questions, so you can hold us to them:

• Every fare is compared only against fares we've recorded for the same route, departure month and booking window.
• An email goes out only when a fare scores 90 or more out of 100, and at most once a week per route. Most days there's nothing to send, so we send nothing.
• Below 20 recorded fares for that comparison we produce no score at all, and below 60 we never email — here's why.
• The price in an alert is the lowest fare we've seen for those dates, and it says that bags and seat selection are extra.
• The code that computes the score cannot see any referral or commission data. That's enforced in how the code is structured, not just stated as a policy — how the score works has the details.

So, are price alerts worth it? An alert that tells you when a fare is genuinely good, and stays quiet otherwise, is. One that tells you every time a number moves mostly isn't. If you'd like to try the first kind, watch a route — it's free while we're in beta.