Set up price alerts for symbols on your watchlist — Playbook

A good alert setup = levels that genuinely require action, not levels that are just interesting to watch. Common mistake: too many alerts (notification fatigue → all ignored), or thresholds too wide (alert fires too late). This workflow builds disciplined alerts: per symbol on your watchlist, threshold at decision levels, cooldown to prevent spam.

What you can alert on

The /alerts panel supports:

Kind: 3 tabs — IDX STOCK / MACRO/FX / CRYPTO (FX and macro share one tab).
Symbol: IDX ticker, macro/FX symbol, or crypto pair. Auto-suggested per kind.
Display name (optional): readable label like “Bank Central Asia Tbk.” alongside the symbol code — shown in the alert list for quick scanning.
Field: price or 24H change %.
Operator: ≥, ≤, >, <, ==.
Threshold: numeric value (price or %).
Cooldown (minutes): minimum duration between triggers (default 15). Prevents the alert from firing repeatedly when price flip-flops around the level.
Alert name (optional): if blank, the terminal auto-generates it from symbol + threshold.

Notifications fire via two channels at once:

In-terminal toast — bubble on the right side of the screen when the terminal tab is active.
Browser push — still appears when the terminal tab is inactive (as long as the browser isn’t fully closed). Requires browser notification permission on first enable; a “Push notification active” banner appears at the top of /alerts once granted.

Workflow: set up your first alert

Make sure your browser has granted notification permission. If not, the Alerts tab will request it when you set the first alert.
Open /alerts. The header shows total alerts, active count, ever-triggered count.
Click “New alert” (or ”+ Buat alert pertama” if the list is empty).
“Buat alert baru” form:
- Kind: pick IDX STOCK / MACRO/FX / CRYPTO.
- Symbol: pick from list (auto-suggest based on kind).
- Display name (optional): readable label, e.g. “Bank Central Asia Tbk.” for BBCA.
- Field: price (PRICE) or 24H change %.
- Operator: pick per logic (e.g. ≥ for breakout, ≤ for support break).
- Threshold: number.
- Cooldown (minutes): 15 default is fine. Bump to 60 for volatile pairs that often retest the level.
- Alert name (optional): description, e.g. “BBCA breakout 9800”. Leave blank to auto-generate.
Save. The alert lands in the list with an enabled toggle.
Test: if the threshold is already breached at create time, the alert fires immediately. Otherwise it stays pending until price crosses it.

Alert strategy per use case

Breakout watch (IDX):

Set price ≥ resistance level.
Cooldown 30–60 minutes (breakouts often retest, avoid alert flood).
After trigger: validate volume before entry. Volumeless breakouts are often false.

Support break / SL preview (crypto):

Set price ≤ key support.
Cooldown 60 minutes.
Trigger as early warning before price actually breaks — gives you reaction time.

Macro level (DXY/Gold/US10Y):

Set price ≥ or ≤ at levels that trigger a macro-view repositioning.
E.g. DXY ≥ 105 = strong USD, reduce risk-asset exposure.

Detect unusual moves:

Set 24H change % ≥ 5 (or whatever % is significant for that asset).
Heads-up on events you should investigate before deciding.

Naming convention for maintenance

Once you accumulate 20+ alerts, the list becomes hard to scan. A useful naming convention:

[ASSET] [DIRECTION] [LEVEL] [REASON]
Example: BBCA UP 9800 breakout, BTC DOWN 95K support, DXY UP 105 risk-off.

If an alert fires 2 weeks later, the name should be self-explanatory enough that you remember why it was set at that level — and whether it’s still relevant.

Maintenance: periodic review

Weekly: scroll the alert list, disable ones whose trigger has passed (level already broken, no longer relevant).
Monthly: check the trigger-count column. Alerts with count > 5 in 1 month = threshold likely too tight (price flips at that level often) — adjust to a more meaningful level.
After trigger: if you’ve followed up (entry / decision), disable or delete. If you decided not to act, log the reason in your Journal — so you don’t reset the same alert next week.

Common pitfalls

Setting thresholds at “interesting” but not actionable levels. If you alert on every minor support/resistance, everything becomes noise. Only alert at levels you commit to acting on (entry, exit, or serious evaluation).
Skipping cooldown. Alerts with no cooldown (or 1-minute cooldown) in volatile markets = notification flood. You’ll disable browser notifications, then forget to re-enable — alerts go silently dead.
Forgetting to disable after action. Stale alerts re-fire when price retests. Disable or delete after handling.
Using 24H % change without volatility context. A 5% threshold is reasonable for ETH; 5% on BBCA = extreme (very rare). Calibrate per the asset’s volatility baseline.
Setting alerts at psychological round prices (95000) without checking structure. Round numbers often aren’t real decision levels — check the chart first for confluence (swing high/low, MA, Fibonacci) before committing to an alert.
Forgetting browser permission. In-terminal toast only fires while the terminal tab is open. Browser push still works while the tab is inactive, but the service worker shuts off when the browser is fully closed → alerts don’t fire (no email fallback). Confirm the green “Push notification active” banner is showing on the /alerts header.
Setting alerts on assets you wouldn’t trade. Alerts are meaningful only with an actionable response. If you alert out of “interest” without trade intent, that’s noise consumption.