My Alerts — your own rules (beta)

Every other alerting surface on the dashboard shows the same feed to everyone, and you narrow it with filters while you are looking at it. My Alerts is the opposite: you write the rule once, and it is evaluated continuously whether or not you have the site open. When something matches, you get an email or a browser notification. A filter decides what a page shows while you watch it; an alert tells you when you are not watching.

The evaluation loop is new. Alerts can fire late, and they can fail to fire at all, so do not make this your only signal yet — keep watching the pages you already watch. This matters more here than on a chart or a table: when an alerting tool breaks, it goes quiet, and silence looks exactly like a calm market. If a rule should have fired and did not, tell us — that is the single most useful thing you can report while this settles.

Click the bell in the top corner of the dashboard, next to the sign-out button. It loads at /account/alerts. It needs an active subscription — with an expired one your rules are kept but stop being evaluated, so nothing is lost if you come back.

Click New alert. Give it a name you will recognise in an email subject line, then add one or more conditions. Each condition is a field, an operator and a value — for example premium > 500000. Add a condition stacks another one underneath.

Conditions are combined with AND, never OR. A rule with premium > 500000 and dte <= 1 fires only on contracts that satisfy both. If you want two independent triggers, create two alerts — that is deliberate, because a rule you can read in one line is a rule you can trust.

For options flow: premium in dollars, volume in contracts, V/OI (volume over open interest), days to expiration, % out of the money, call or put, fill direction (ask, bid or mid) and direction (bull or bear). The list only offers what the scanner actually measures — a field that could never match is not shown at all. Price action, technical levels and dark pool appear greyed out as coming soon: they are declared but not yet evaluated.

Leave the Tickers box empty and the rule watches everything the scanner covers. Type SPY, NVDA to restrict it to those names. Empty is not a mistake — it is the setting for hunting anomalies wherever they happen, and the frequency limit below is what keeps that usable.

Tick Email, Browser, or both — at least one is required. Email arrives at your account address. Browser asks for notification permission the moment you tick the box, never before, and works on desktop Chrome, Firefox and Edge. On iPhone, notifications only work if you have added the site to your home screen first; the form says so rather than failing silently.

At most every N minutes caps how often one rule can fire for the same contract. The default is 30 minutes and the minimum is 5. Without it, a rule watching the whole universe during an active session would mail you continuously. The limit is per contract, so two different contracts matching the same rule both come through.

Each rule in the list carries Pause and Delete. Pausing stops evaluation and keeps the rule; the list shows it as paused. Deleting removes the rule and its history. There is no confirmation step, so read the name before you click.

Underneath your rules, the last 50 firings are listed with their timestamp and the contract that caused them. Use it to sanity-check a new rule: if it has fired 40 times in an hour, the thresholds are too loose; if it has never fired, they are too tight or the market has simply been quiet.

Rules are re-read and evaluated about once a minute, so a change you save is live within a minute and a match reaches you within roughly two. You can keep up to 20 rules. An alert older than five minutes is dropped rather than delivered late — a stale flow signal presented as fresh is worse than no signal at all.