Notifications

The Notifications module lets you define precise market conditions and get alerted the moment they're met — whether that's an ADP extreme, a Trend Dominance shift, or a specific ticker breaking away from its EMA. You set the rules once; the terminal does the monitoring.

There are two modes depending on what you're tracking: Average mode for market-wide conditions, and Ticker mode for individual asset conditions.

Average Mode

Average mode works with the same market-wide metrics you see on your main dashboard — Average Deviation Powerand Trend Dominance — averaged across your entire watchlist.

Use this when you want to know that the broad market has reached a meaningful state: overextended, crossing a key level, or entering a specific range.

Setting Up a Notification

Timeframe — Select which timeframe the condition should be evaluated on. You can add multiple timeframe blocks to a single notification using the + Add button, but each timeframe can only appear once.

Average Deviation Power — Set the condition for the ADP value on that timeframe.

Trend Dominance — Set the condition for the Trend Dominance value on the same timeframe.

Notification name (required) — Give it a clear, descriptive name. You'll thank yourself later when you have 10 active alerts running.

Comment (optional) — Add context about why you created it or what setup it's tied to.

How Conditions Work

open > — Fires when the live value is strictly above your threshold. Stays active as long as the condition holds.

open < — Fires when the live value is strictly below your threshold.

open cross (=) — Fires once the moment the value crosses your level in either direction. One trigger per crossing.

open cross up — Same as above, but only triggers on an upward cross.

open cross down — Only triggers on a downward cross.

close in range [min..max] — Evaluated on the closed candle value. Fires when the value lands within your defined range (inclusive on both ends).

close > / close < — Evaluated on the closed candle value, above or below a single level.

Evaluation Logic

When you add a single timeframe block, both conditions on that timeframe must be satisfied simultaneously — ADP AND Trend Dominance.

When you add multiple timeframe blocks, all conditions across all timeframes must be true at the same time. It's a logical AND across the board — the alert won't fire unless every condition is met.

A few rules to keep in mind:

• Each timeframe can only be selected once per notification.

• Cross-based conditions (=) cannot be combined with close-based conditions on other timeframes in the same notification.

• When using a range, make sure min ≤ max.

Ticker Mode

Ticker mode evaluates conditions per individual asset rather than across the whole watchlist. Use this when you want to track something specific — a single coin or a defined group of tickers — against its own EMA deviation and duration.

Setting Up a Template

In Ticker mode, you first create a template — a reusable set of conditions. Once the template is saved, you can apply it to any tickers or tag-based groups you want to monitor.

Timeframe — Which timeframe to evaluate the condition on. Multiple blocks can be added via + Add.

EMA (o_diff) — The condition applied to the asset's deviation from its EMA (expressed as a percentage difference). This is the per-ticker equivalent of ADP.

Duration — The condition applied to how many consecutive candles the asset has been holding above or below its MA.

Template name (required) — Name it clearly. Include the timeframe and direction if possible — e.g. BTC – 65% LONG – SL3 TP5 or 5min SCALP SINGLE LONG (-2).

Comment (optional) — Notes on the setup or strategy context.

Once a template is created, it appears in your Templates list. From there, you can:

• Assign it to specific tickers directly

• Assign it to a tag to apply it across a group

• Hit Apply to activate it

• Edit or delete it at any time

How Conditions Work

EMA (o_diff): open > / open < — Fires when the live deviation value is above or below your threshold.

EMA (o_diff): open cross (=) — Fires once on any crossing of your level (either direction).

EMA (o_diff): open cross up / open cross down — Directional crossing triggers only.

EMA (o_diff): close in range [min..max] — Evaluated on the closed candle. Fires when the deviation lands within your range (inclusive).

EMA (o_diff): close > / close < — Closed candle value above or below a single level.

Duration: open > / open < — Compares the live duration (number of consecutive candles above/below MA) against your threshold. Useful for catching assets that have been trending persistently, not just spiking.

Evaluation Logic

The same logic applies as in Average mode:

• Each timeframe can only appear once per template.

• On a single timeframe, both blocks must be satisfied — EMA deviation AND Duration.

• With multiple timeframes, all conditions across all timeframes must be true simultaneously.

• Cross-conditions (=) cannot be combined with close-based conditions on other timeframes.

• For ranges, min ≤ max.

Notifications List and Archive

All active notifications are visible in the Notifications List, where you can see their current status at a glance:

• Active — toggle on/off without deleting

• Repeats — set whether the alert fires once or continues repeating each time the condition is met

• Delete — whether the notification is automatically removed after it fires

• Type — delivery method: in-browser (Web) or Telegram

• Created — timestamp for reference

Triggered notifications are stored in the Archive tab, so you can review what fired, when, and under what conditions — useful for backchecking your alert logic or reviewing missed setups.

Practical Tips

Name your alerts like setups, not just conditions. "Alert 1" tells you nothing at 3am. Something like BTC 4H ADP Cross Up +2 or Market Oversold 15m is immediately useful.

Use cross conditions for entries, range conditions for context. Cross-based alerts are precise and time-sensitive — great for catching the moment something changes. Range conditions are better for monitoring whether the market is in a particular state.

Combine DP + DUR in Ticker mode for quality over quantity. An asset that just crossed a threshold is different from one that's been holding above it for 40 candles. Combining both filters in a single template cuts the noise significantly.

Use the Archive to audit your logic. If an alert fired but you didn't like the setup, go back and look at what the conditions actually were at that moment. Over time, that feedback loop will sharpen your alert configurations considerably.