How to get alerts for flight deals

Why alerts for flight deals need a system, not just an app

Setting up alerts for flight deals is easy in theory: pick an app, enter a route, wait for a notification. In practice, the value of an alert depends on what it's actually measuring and how quickly you act once it arrives. A notification that lands three days before a fare disappears is more useful than one that arrives after the seats are gone, and an alert built on a stable reference price is more useful than one that simply flags 'lower than yesterday.'

The most reliable approach treats alerts as one part of a small workflow: choose your departure flexibility first, then pick one or two alert channels that match how you actually search, then decide in advance what you'll do when an alert fires. Without that last step, alerts just add noise, because fares can move again before you've confirmed anything with the airline or booking provider.

• Define your flexible date range and acceptable airports before turning on alerts
• Pick channels that match your habits (email, app push, or a dedicated deal page)
• Decide your response window in advance, since fares and availability can change quickly

Choosing your alert channels

Google Travel lets travellers track specific flights and routes and receive price change notifications, which is a straightforward way to monitor one or two trips you're already planning. It works well when you know your dates and just want to watch a known itinerary for movement, and it sits inside a tool many travellers already use for search, so there's little setup overhead.

Flare takes a different starting point: rather than tracking a route you've already chosen, it publishes flight-deal discovery pages built from a traveller's departure city, surfacing routes and fares that may not have been on your radar. According to its published methodology, the deals shown are ones detected at least 30% below the route reference price that its monitoring uses. That's useful for flexible travellers who want to see what's worth considering from their home airport, rather than travellers who already have one specific flight in mind.

A practical setup often combines both approaches: use a discovery page or similar source to surface candidate routes and price drops you weren't watching for, then use route-specific tracking once you've narrowed down to a trip you're seriously considering, so you can follow that particular itinerary as it moves.

Understanding what a threshold actually means

Any alert built around a percentage discount is only as meaningful as the reference price behind it. A '30% below' claim tells you the fare is unusually low relative to what that monitoring system normally sees on that route, not that it's the lowest fare that will ever exist, and not that it accounts for your specific dates, cabin, or baggage needs. Reference prices vary by methodology, so a discount on one platform isn't directly comparable to a discount calculated differently on another.

This distinction matters most when you're deciding whether to act on an alert immediately or wait for a better one. A deal that clears a discovery threshold is a signal worth investigating, not a guarantee of value for your particular trip. Total-trip context still applies: a deeply discounted fare into an airport with expensive onward transport, or with dates that force an extra hotel night, may cost more overall than a moderately discounted fare that fits your itinerary better.

Because thresholds are set against historical monitoring data, they can flag fares that later change or sell out before you check them. That's normal behaviour for any price-tracking system and not a flaw specific to one tool; it's simply a reason to treat every alert as a starting point for checking, not as a final price.

A worked example: setting up alerts for a flexible trip

Example only, not a real itinerary or observed result: suppose a traveller in Chicago wants to take a one-week trip somewhere in Europe sometime in the next four months but has no fixed destination. They could start by browsing a departure-city discovery page to see which European routes from Chicago are currently flagged as notably below their usual reference price, giving them a shortlist of destinations rather than a single locked-in plan.

From that shortlist, they narrow to two or three destinations they'd genuinely enjoy, then set up route-specific tracking in Google Travel for each of those city pairs across their flexible date window. This way, discovery alerts continue surfacing new ideas in the background, while tracked-route alerts tell them when their shortlisted options move.

When an alert fires, they check the fare directly with the booking provider before doing anything else, since displayed fares and availability can change between when an alert is generated and when they look. If the price and dates work, they check current entry, passport, and any visa or health requirements for that destination before booking, since those requirements depend on the traveller and destination and can change.

This example illustrates a workflow, not a guaranteed outcome; actual fares, availability, and requirements will vary by traveller and by the time you search.

A short checklist before you act on an alert

Before booking anything triggered by a flight deal alert, it helps to run through a short, repeatable check rather than relying on the alert text alone. This is especially true for alerts sourced from a discovery page, where the fare was flagged as low relative to a reference price but hasn't necessarily been checked at the moment you're reading it.

• Confirm the current fare and seat availability directly with the airline or booking provider
• Check that the dates and airports still match your plans, including any connections
• Verify current official entry, passport, visa and health requirements for your destination
• Add total-trip costs (bags, transport, accommodation) before comparing two deals
• Re-check the fare once more immediately before payment, since prices can move quickly

Keeping alerts useful over time

Alerts lose their usefulness quickly if you let too many accumulate without reviewing them. It's worth periodically pruning tracked routes you're no longer seriously considering, since a long list of stale alerts makes it harder to notice the ones that actually matter, and it can lead to acting on outdated information out of habit.

It's also worth remembering that any alert, whether it comes from route tracking or a discovery page, is describing a snapshot in time. Flare's public pages describe the deals shown as detected below a route reference price at the point of detection, according to its methodology, not as a live, continuously updated quote. Treating every alert as a prompt to verify, rather than as the final word on price, keeps the whole process useful rather than misleading.