Alerts Management
Get notified when market activity matches your criteria
What Alerts Management does
Alerts Management watches for market events that match rules you define. Each alert has one source, optional filters, a cooldown, and one or more delivery channels.
Use alerts when you want to monitor a focused condition without keeping a feed open. Keep the criteria narrow enough that every notification deserves a review.
Availability: Options-activity and flow-acceleration alerts require Gamma or higher. Trade Idea and Market Commentary alerts require Theta or Vega because their source features use those plans.
Open it: Choose Alerts Management in the sidebar, use Manage Alerts from the notification menu, or open optionomics.ai/alerts.
Choose an alert source
Every alert monitors one source. The form changes after you choose the source so you only see relevant criteria.
| Source | What can trigger it |
|---|---|
| Option Alerts | A new options-activity event matches the selected contract, premium, timing, execution, or unusual-activity filters |
| Trade Ideas | A new AI Trade Idea matches the selected symbol, direction, strategy, confidence, conviction, or model track-record filters |
| Market Commentary | A new Market Commentary item matches the selected symbol, category, and severity |
| Flow Acceleration | Call- or put-side flow for a symbol reaches the selected direction and acceleration level |
Leave Stock Symbol blank to monitor all supported symbols for that alert. Enter one ticker when the rule should only apply to a specific name.
Create an alert
- Open Alerts Management.
- Choose Create Alert.
- Select the source before setting filters.
- Add a descriptive name and an optional note.
- Set a cooldown between 1 minute and 7 days.
- Enter a symbol or leave it blank for all symbols.
- Add only the criteria needed for your question.
- Choose at least one delivery channel.
- Save the alert.
All configured criteria for an alert must match. Adding more fields makes the rule narrower; it does not create separate alternatives.
Options-activity criteria
The Option Alerts source can filter visible activity by:
- Call or put
- Minimum and maximum premium
- Minimum and maximum days to expiration
- Minimum and maximum unusual score
- Minimum volume/open-interest ratio
- Minimum and maximum strike
- Execution location, such as above ask, at ask, mid-market, at bid, or below bid
- One or more user-facing unusual-activity patterns
An unusual score or execution label helps prioritize activity, but neither proves trader intent. A matching print can still be part of a spread, hedge, closing trade, or larger portfolio transaction.
Trade Idea criteria
Trade Idea alerts can filter by:
- Direction
- Strategy
- Minimum confidence
- Standard or High Conviction tier
- Minimum displayed model win rate
Historical model results are context, not a guarantee that the next idea will resolve the same way. Review the public Track Record and the idea detail before acting.
Commentary and flow-acceleration criteria
Market Commentary alerts can use the commentary category and minimum severity. If you set a symbol, the commentary must reference that symbol.
Flow Acceleration alerts can use direction and a minimum acceleration score. These alerts identify a change in the pace of displayed flow; they do not predict the direction of the underlying stock.
Templates and starter recipes
Choose Browse Templates to start from a preconfigured alert. When your account has no alerts, the page also offers starter recipes that can add a small group of related rules.
Review every generated rule before enabling it. Adjust symbols, thresholds, cooldowns, and channels to fit your own workflow rather than treating a template as a recommendation.
Delivery channels
| Channel | Setup |
|---|---|
| Uses the email on your account | |
| SMS | Requires a valid phone number and acceptance of the SMS terms |
| Slack | Requires a Slack incoming-webhook URL |
| Discord | Requires a Discord webhook URL |
| Push (Mobile) | Requires the iOS app and notification permission |
| Developer webhook | Sends a versioned JSON event to your HTTPS endpoint |
The Notifications page provides your in-app notification history. Browser notifications can be enabled from the notification menu when your browser supports them.
Developer webhooks
Enable Developer webhook, enter an HTTPS endpoint, and return a successful 2xx response when your application accepts an event. The form displays the current public payload contract. Do not infer fields that are not shown there.
Use Webhook logs on the Alerts page to review delivery attempts. If you edit an existing alert, you can also open its delivery history from the alert row.
Keep credentials out of webhook URLs. If your endpoint is compromised, replace its secret and update the alert.
Manage and review alerts
The Alerts table shows each rule’s status, criteria summary, trigger count, average tracked performance when available, and last-triggered time.
Available actions include:
- Edit the criteria, cooldown, or channels
- Pause or reactivate the alert
- Send a sample test notification
- Log a trade in the Trade Journal
- Review webhook deliveries
- Delete the rule
Use Test after changing a delivery channel. A successful test confirms delivery setup; it does not test whether the market criteria will match.
Reduce noise
- Start with one symbol or a focused condition.
- Use a cooldown long enough to prevent repeated notifications from the same event.
- Review trigger frequency and tracked performance on the Alerts page.
- Pause rules that no longer answer a useful question.
- Add another delivery channel only when you need it; duplicating every event across every channel can hide the important alerts.
Alerts surface matching information. They are not orders or personalized trading recommendations, and delivery can be delayed by networks or third-party services.
