Lessons

  • How Alerts Work

    An introduction to Alerts

  • Destinations

    Where Alerts can send notifications

  • Creating a Rule

    How to create and manage alert rules

  • Rule Filters

    How to filter Alerts for useful matches

  • Reading Deliveries

    How to inspect delivered alerts

  • Maintenance and Troubleshooting

    How to keep Alerts useful

  • Examples
  • Positive EV Alert

    Create a focused value-bet alert

  • Middles Alert

    Create an alert for useful middle candidates

  • Radar Bonus Alert

    Create a Radar alert for bonus conversion

  • Webhook Alert

    Send alerts to an external workflow

  • Falling Odds Alert

    Create an alert for confirmed moves and slow-book offers

Falling Odds Alert

Create an alert for confirmed moves and slow-book offers

Scenario

Say you want a notification when trusted reference bookmakers shorten and one of your usable bookmakers still offers a longer price.

You want enough confirmation to avoid every small flicker, and enough time to verify the opportunity before the event starts.

Create the rule

Create a new alert and choose Falling Odds.

Choose the in-app stream first. Add browser push if the rule is selective enough that you want immediate device notifications.

Set the filters

Offer Bookmakers

Select the bookmakers where you can actually place the slow offer.

Sharp Bookmakers

Select the independent reference books you want to follow, or leave this empty for broad-market confirmation.

Movement Window

Use a window appropriate for the market. Three hours is a practical starting point; shorter windows react faster and create more noise.

Drop and Gap

Set both high enough that the alert is worth opening. The defaults of 4pp Drop and 10% Gap are a conservative starting point, not universal truth.

Matched and Moved Sources

Require confirmation appropriate to the size of the selected reference pool. Do not require more sources than the chosen sharp list can provide.

Time Window

Exclude events starting too soon to verify and place cleanly.

Add a frequency limit when the rule covers many leagues or markets. A broad move can otherwise produce several deliveries at once.

Read the delivery

Start with the sent and current Drop, the change between them, and the current bookmaker option. Confirm whether the alerted offer is still available.

The delivery is a qualifying snapshot, not the full Falling Odds row. Re-open Falling Odds with the same filters to inspect Gap, the Was and Now reference prices, source confirmation, and fair EV before acting.

Act and track

If the live offer still matches the delivery:

  1. Check the event, market, line, and selection.
  2. Review fair odds and EV when available.
  3. Place at a stake that fits the bankroll and account.
  4. Record the actual bookmaker, odds, and stake in Tracker.

Common mistakes

  • Making the rule broad enough to alert on normal price noise.
  • Selecting bookmaker aliases that share one datasource and treating them as independent sharps.
  • Forgetting a small sharp list needs achievable source thresholds.
  • Treating Drop as EV.
  • Chasing the delivered price after the bookmaker has moved.