Guide
Event notifications
In Watchlist.top there are two different groups of notifications. Price notifications are monitored on the server and delivered to Telegram or email. Parameter-based notifications work inside the application for the current list: they react to price change, volume, trades, combined conditions, and impulse. This section explains where each type is configured, what the tabs in the notifications window mean, and what changes for demo, trial, and subscribed users.
What this section covers
- What is the difference between server-delivered price notifications and notifications that work only inside the application.
- What the "Price" and "By parameters" tabs show and why price notifications are split into active, newly triggered, and inactive.
- How parameter notifications are split into "By changes" and "Impulse" and why they depend on the current saved list.
- How the delivery channel is chosen in account settings and why email confirmation or Telegram binding is required.
- Why users without an active subscription are limited to one active server-side price notification.
- How sound notifications work: you choose one of the available alert sounds and set the volume in settings, and the sound plays locally in the browser when a notification fires.
- What a combined condition notification is: it fires only when all the thresholds you set are met at the same time, unlike a single-parameter notification that reacts to any one condition alone.
- What specific thresholds you define in a "By changes" notification: the percentage price change, the volume multiplier relative to the average, or the number of trades in the selected window.
Key screens and controls
- Chart controls where price notification lines are created from the chart.
- Notifications window with the "Price" tab and its three states: Active, Newly triggered, and Inactive.
- Notifications window with the "By parameters" tab, including the "By changes" and "Impulse" sections.
- Impulse settings block with the enable switch, period, and minimum percentage change.
- Account settings with email, Telegram, and the delivery channel selector.
- Combined conditions form in the "By changes" subtab with multiple parameter thresholds added together.
- Sound settings in the settings dialog with the sound selector and volume control.
Step-by-step flow
- To get a price alert delivered to Telegram or email, create a price notification line directly on the chart. This registers a server-side notification that keeps monitoring even when the app is closed.
- Open account settings and make sure the delivery channel is ready. Email delivery requires a confirmed email, and Telegram delivery requires a linked Telegram account.
- Open the "Event notifications" window and use the "Price" tab to see your server-side notifications. Active notifications are still being monitored, newly triggered notifications have just fired, and inactive notifications stay in history until you remove or edit them.
- If you need local notifications inside the application, go to the "By parameters" tab. The "By changes" subtab shows saved notifications for price change, volume, trades, and combined conditions for coins in the current list.
- Use the "Impulse" subtab when you want to catch a fast move over a short period. Turn it on, choose the period in minutes, and set the minimum percentage change.
- When a browser notification fires, a toast appears in the lower-right corner. Clicking the toast opens the coin from that notification.
- If you no longer need a notification, remove it from the corresponding row or clear the entire current list of notifications with "Delete all".
- To set up a combined condition notification, go to the "By changes" subtab and add conditions for two or more parameters. The notification fires only when all conditions are met at the same time.
- To enable sound when a browser notification fires, go to settings, pick an alert sound, and set the volume. The sound plays locally in the browser and does not affect Telegram or email delivery.
Screenshots
Screenshot placeholder
Price notification line on the chart
Show where a server-side price notification is created and how it looks on the chart.
Screenshot placeholder
Price tab in the notifications window
Show the tabs for active, newly triggered, and inactive price notifications.
Screenshot placeholder
By changes notifications for the current list
Show saved parameter notifications in the "By parameters" section for the current list.
Screenshot placeholder
Impulse settings and triggered impulse events
Show the enable switch, period, percent threshold, and the list of triggered impulse events.
Screenshot placeholder
Alert delivery channel in account settings
Show where the user confirms email, links Telegram, and chooses the delivery channel.
Screenshot placeholder
Demo warning about the active notification limit
Show the warning that appears when a demo user tries to create more than one active server-side notification.
Operational notes
- Price notifications with delivery are monitored on the server. They do not depend on whether the coin is currently visible in your open list or chart.
- Notifications in the "By parameters" section belong to the current saved list. When you switch to another list, you see another set of local notifications.
- Impulse settings are saved with the current list, but the list of already triggered impulse events is temporary and is shown only inside the running application session.
- A triggered server-side price notification can later be edited and returned to active monitoring if your account and delivery channel still allow it.
- If email is not confirmed and Telegram is not linked, the application cannot use the corresponding delivery channel even if the notification itself is configured.
- Sound notifications play in the browser tab only. If the tab is muted or the device volume is off, the sound will not play even when the notification fires.
- A combined condition notification requires all thresholds to be met simultaneously. A coin matching only some of the conditions does not trigger it.
- When trial access expires, active server-side price notifications are paused and move to the inactive list. They remain in your history and can be reactivated when the subscription is restored.
When to use it
- Use this section when the user wants to set up notifications and understand where each type is monitored and where it appears later.
- It is the right place to explain the difference between delivered price notifications and local notifications that only work inside the application.
- It also fits questions that combine thresholds, channel delivery, trigger history, and demo or subscription limits.
When not to rely on it
- Do not use this section as the main answer if the user is only trying to confirm email, link Telegram, or restore account access before notifications are even configured.
- It is also not the main section for formulas of one metric when the question is about how that value is calculated rather than how notifications use it.
Typical interpretation mistakes
- Do not assume that every notification visible in the window is an actively monitored server-side price notification. The window also shows local notifications for the current list.
- Do not ignore account status and channel readiness when you expect delivery. A configured notification still needs a valid email or Telegram channel and the right subscription state.
- Do not treat impulse history as a permanent saved archive. It is only a temporary list of events from the current application session.
Algorithms and formulas to understand
- Why a price notification can move from active monitoring to the newly triggered or inactive list instead of disappearing immediately
- Why notifications in the "By parameters" tab change when you switch to another saved list
- Why impulse settings stay with the list, while already triggered impulse events are only a temporary session history
- Why a demo user can create only one active server-side price notification at a time