LevelBeacon exposes four named TradingView alerts
| Alert | Layer | Meaning |
|---|---|---|
| LevelBeacon Bullish Setup | Strict Setup | A fresh bullish setup passed the strict confirmed-close engine. |
| LevelBeacon Bearish Setup | Strict Setup | A fresh bearish setup passed the strict confirmed-close engine. |
| LevelBeacon Bullish Opportunity | Opportunity | Bullish near-level Opportunity changed from false to true. |
| LevelBeacon Bearish Opportunity | Opportunity | Bearish near-level Opportunity changed from false to true. |
Create the alert in TradingView
- Open a chart with LevelBeacon already added.
- Open Create alert.
- In Condition, choose LevelBeacon — Key Levels & Bull/Bear Strength.
- Open the second condition dropdown and choose one of the four named LevelBeacon conditions.
- Use Once Per Bar Close as the alert frequency.
- Choose your notification method (app, popup, email, webhook only if you understand the downstream system).
- Create separate alerts for the conditions you want. One alert does not automatically subscribe you to all four.
Why Once Per Bar Close is still the right user setting
The production alert conditions include confirmed-close guards, but matching the TradingView frequency to the intended behavior keeps your alert configuration clear and reduces confusion when you review alert logs.
Opportunity and Setup alerts should be configured separately
If you want early attention, create the two Opportunity alerts. If you only want stricter events, create the two Setup alerts. Many users will find all four useful because they serve different jobs:
- Opportunity: “Open the chart; conditions near the level are lining up.”
- Setup: “The stricter LevelBeacon setup engine has confirmed a fresh setup.”
Why an Opportunity alert may not repeat
Opportunity alerts trigger only when the complete condition transitions from false to true. If the condition stays true for several confirmed candles, LevelBeacon does not send the same alert every candle. It must become false and later true again to re-arm.
Why there is no Opportunity marker on the chart
The production Opportunity feature is alert-only. Only strict Setups can create the BULL/BEAR setup markers. This avoids mixing the early attention layer with the stricter confirmation layer.
The chart-condition screenshots are real. A separate real Opportunity notification screenshot was not available when this Learning Center was built, so this guide does not fabricate one.
Alerts keep their original configuration
TradingView saves a snapshot of the script, inputs, symbol and timeframe when you create an alert. Changing the chart later does not update that running alert. Recreate it when you need the updated version or configuration, then remove the old one to avoid duplicate notifications.
If a notification is missing
- Check that the alert is running, has not expired, and uses the correct symbol/feed, interval and named LevelBeacon condition.
- Check the TradingView alert log. If an event is logged but not delivered, review the selected notification channel and device permissions.
- If no event is logged, confirm history eligibility and remember that the full condition must pass on a confirmed close. Opportunity also needs a fresh false-to-true transition.
- Historical markers do not create backdated notifications. TradingView script alerts trigger on realtime bars.
See TradingView’s explanation of alert snapshots and realtime behavior and notification setup. Available channels and alert limits depend on your TradingView account.