Alert & Risk

Alerts — Detailed Guide

Set up reliable, noise‑filtered alerts for entries, exits, trigger waves, and TP/SL events. Alerts are modular: you choose frequency, categories, and message richness (R:R, ML status, volatility, trend).

1) Enabling Alerts

Turn on: Enable Alerts → true

Choose Frequency:

Once Per Bar Close (recommended)
Once Per Bar (real time, noisier)
All (for debugging only)

2) Alert Categories

Signal Alerts

Bullish/Bearish Signals (core entries)
Enhanced Signals: when trend aligns (EMA50 vs EMA200)

Trigger Wave Alerts

WT3D micro‑divergence triggers for timing

Exit Alerts

Fires when position flips or exit condition is met

TP/SL Alerts

TP1 / TP2 / TP3 hit
SL hit
Risk Levels Set (after new signal sets Entry/TP/SL)

Tip: Use Signal + TP/SL Alerts for most workflows; add Trigger Waves if you scalp.

3) How Signals Are Approved (Filters + ML)

A signal is only alerted when:

Mode condition passes:

Confirmation: os flips up/down with trend
Contrarian: os flips against trend with RSI extremes

Cooldown isn’t violated (prevents clustering)

Not overextended (RSI + EMA200 filter)

Active filters pass:

Smart Trail direction agrees
Trend Catcher agrees
Trend Tracer direction matches
Trend Strength above threshold
Neo Cloud momentum agrees

ML Filter (optional): direction agrees AND confidence ≥ Min ML Confidence

Result: Fewer, higher‑quality alerts.

4) TP/SL System in Alerts

Modes:

ATR Based: uses ATR distances
R:R Fixed: SL ATR multiplier + TP ratios (TP1–TP3)

Alerts include:

Entry, TP1/TP2/TP3, SL prices
R:R context (for entries)
Direction (Long/Short)
Optional ML status and confidence

5) Recommended Setups

Scalping (M1–M5):

Frequency: Once Per Bar Close
Categories: Signals, TP/SL, Trigger Waves
ML Confidence: 55–65%

Intraday (M15–H1):

Frequency: Once Per Bar Close
Categories: Signals, TP/SL
ML Confidence: 60–70%

Swing (H4–D):

Frequency: Once Per Bar Close
Categories: Signals, TP/SL
ML Confidence: 65–75%

6) Creating Alerts in TradingView (Step‑by‑Step)

1. Click the alarm bell (Create Alert).

2. Condition: select “PMALGO® – MultiSignal Trend Navigator 6.5.9”.

3. Pick an Alertcondition:

PMALGO MTN Bullish Signals / Bearish Signals
PMALGO MTN Trigger Waves
PMALGO MTN Exits
PMALGO MTN TP1 Hit / TP2 Hit / TP3 Hit
PMALGO MTN Stop Loss Hit
PMALGO MTN Risk Levels Set

4. Options → Frequency: Once Per Bar Close.

5. Add notification actions (app, email, webhook).

6. Create.

Tip: Set separate alerts per category to keep notifications clean.

7) Message Contents (What You’ll See)

Signals:

Symbol, timeframe, price, time
Signal Quality (0–100 and 1–4 class)
Trend alignment (e.g., “🔥 Strong Uptrend”)
Optional ML: prediction and confidence (✓ ML Approved or ⚠ Low ML Conf)

TP/SL:

Entry price, current price
TP level hit (TP1/2/3) or SL
Direction (Long/Short)

Risk Levels Set:

Entry, TP1–TP3, SL levels posted right after a new signal

8) Best Practices

Reliability: Prefer “Once Per Bar Close” for robust signals.
Cleanliness: Use filters sparingly—too many filters = very few alerts.
R:R Clarity: Use R:R Fixed for consistent targets; ATR Based if you want dynamic distances.
Plot Limit: Alerts work even if some visuals are disabled; keep Plot Management on Smart Auto or Essential Only if needed.

9) Troubleshooting

No alerts:

Ensure Enable Alerts = true, showSignals = true
Lower Min ML Confidence or disable ML temporarily
Reduce active filters or cooldown sensitivity

Duplicates:

Switch to Once Per Bar Close
Avoid overlapping categories targeting the same event

TP/SL not firing:

Turn on TP/SL Visualization (for lines/labels)
Ensure a new signal set Entry/TP/SL before expecting TP/SL hits

Risk Management: Entry, TP1–TP3, SL

Two modes:

ATR Based: classic ATR distances
R:R Fixed: set SL ATR multiplier + TP ratios for consistent risk

Visuals:

Entry, SL, TP1–TP3 lines + left-aligned labels with prices
TP breakout markers (★, ★★, ★★★) at the highest level reached