Skip to main content

6. Tracker module

Module link: https://my.whalepro.org/tracker/

6.1. Overview

On the crypto market there are helper bots that highlight changes in trading across exchanges. Their job is to continuously monitor market situations that may be interesting for a trader and can lead to profitable trades. Such situational trades often occur after extreme readings of certain volume and/or price indicators.

For example,

  • in a trading pair, over several days, the buy volume accounts for more than 51% of total volume — possibly indicating buyer dominance;
  • or a timeframe shows seller dominance while the 24h close price delta is positive — possibly indicating gradual distribution;
  • and so on.

Thousands of such situations occur every day, and tracking them manually is impossible.

Below we discuss the platform’s Tracker which helps find interesting trading moments and provides an extremely wide set of customization options.

In short, the Tracker can find interesting situations using any combination of 120+ platform indicators.

Rules and scenarios

We will review Tracker mechanics in the next sections. For now, note that all work in the Tracker is done by creating tracking rules. Each rule has required indicators and optional metrics to fill out.

Scenarios are a layer on top of individual rules that allows you to track the sequential execution of rules you created. This is an advanced forecasting feature and an inexhaustible source of strategy testing to discover optimal patterns in volume and price analytics.

How the Tracker works

All interaction with the Tracker happens in the platform’s web UI where the user configures notifications, and via a Telegram bot that delivers the notifications. The bot only sends messages; it does not accept commands.

General view of the configuration UI:

1. Warning.

Clicking this shows a popup reminding you to carefully read the platform documentation.

2. Buttons for creating rules and scenarios

Create rule starts a step-by-step interface at the bottom of the page.

Create scenario opens a modal to create a scenario from several rules.

3. On the right there is a counter displaying how many rules and scenarios the user has created under their plan. All rules count toward the limit, including inactive ones and those used in scenarios.

Below the header with the buttons is the main area showing the user’s configured rules. The process is simple: you configure rules and they immediately appear in the main area. This main area is logically divided into two sections:

  • individual rules
  • scenarios

The second section is used to group rules into scenarios.

Inside the rules and scenarios tables there are several informational labels:

4. The base (universe) the rule or scenario operates on. Specific pairs may also be listed if the user chose to track them.

5. The delay between notifications for a rule’s triggers.

6. Counts of filled metrics in “Main indicators” and “Current TF performance in a row”. (We’ll review these two groups in detail in the rule creation section.)

7. A quick toggle for rule state: Active/Inactive — to stop a rule without deleting it.

8. Three action buttons for rules:

  • The first opens a rule for editing.
  • The second duplicates a rule with a new name (useful to tweak a copy).
  • The third deletes a rule permanently.
6.2. Creating individual rules

This section covers creating a rule that tracks patterns based on a single candle, i.e., at most one timeframe.

To create a rule, click the top button or the link below:

A step-by-step interface opens:

Note that each step has settings on the left and detailed descriptions on the right:

Let’s look at the first two steps on the left. (Only the first two steps are required.)

  • “Create rule from scratch” means creating the rule entirely via the Tracker UI.
  • “Create rule from chart alert” means the new rule is partially based on an existing alert. Indicators used in the alert will automatically appear on the next steps with their configured values. Such rules are marked with “A” in the name.

Second step.

Assume we chose to create a rule from scratch. Then the second step looks like this:

The right side contains detailed field descriptions. A slightly expanded summary is below:

Rule name

Displayed in the rules list and used as the bot message title when the rule triggers.

Base (Universe)

Select the base on which to check the rule. Currently available: BTC, USDT, TUSD, ETH.

Trading pairs

Select specific pairs for the rule. Currently more than 950 pairs are available.

Exclude coins

A list of coins to ignore for this rule. For example, if you specify BUSD, GBP, then pairs like BUSDUSDT and GBPUSDT will be ignored even if they meet all other conditions. This can be useful to exclude tiny-satoshi pairs where a one- or two-satoshi move can cause large percentage changes and many noisy alerts.

Delay

For individual rules

How long to suppress repeated notifications after a trigger for a specific pair.

For scenarios

  1. For the first rule: a pause between full scenario triggers for a specific pair.
  2. For the second and third rules: a delay before the next rule starts checking after the previous one for a specific pair. (E.g., a 15-minute delay for rule 2 means it starts only 15 minutes after rule 1 triggered.)

Attention: if a scenario for a specific pair triggers too often (e.g., on a daily timeframe it triggers every hour), to reduce the number of triggers and messages simply set the first rule’s delay to the desired time. The scenario will not send a new notification earlier than this delay from the last notification.

History

Choose how many historical data points to include in the trigger message for the pair. Historical data are the states of the rule’s indicators at previous triggers. Applies only to individual rules that track a single timeframe.

Price delta 24h

Boundaries for the 24h price change.

Trading volume 24h

Boundaries for daily volume. The script updates per pair every ~10 minutes (possibly faster), so this indicator is checked on the exchange within this period. “24 hours” means the sum of five-minute intervals for the last 24 hours, which is closest to the exchange’s value. Calculations use 5-minute data, not daily candles.

Volume change 24h, %

Boundaries for the change of 24h volume compared to the previous 24h. Note it is calculated over 24 hours, not calendar days, and recomputed every 3–5 minutes.

Timeframe

Choose timeframes on which the selected pairs will be tracked.

Number of timeframes

Specify how many timeframes (candles) must match the indicators’ filled values.

On closed timeframe

Enable to track only closed candles. The current (open) candle will not be checked.

6.3. Working with rules

After a rule is created it appears in the main list. You can:

  • Activate/deactivate the rule using the toggle
  • Edit the rule
  • Copy the rule to create a similar one with small changes
  • Delete the rule

When a rule is active, the system constantly checks the selected pairs for compliance. When all conditions are met, the system sends a notification to the Telegram bot.

Notifications contain:

  • Rule name
  • Pair that triggered
  • Indicator values that led to the trigger
  • History of previous triggers (if enabled)

Recommendations for effective usage:

  1. Start with simple rules and gradually complicate them
  2. Give rules clear, informative names
  3. Configure delay to avoid too-frequent notifications
  4. Periodically analyze performance and adjust parameters
6.4. Scenarios from rules

Scenarios allow you to create sequences of rules that must trigger one after another in a defined order, enabling tracking of more complex market patterns.

To create a scenario:

  1. Click "Create scenario" at the top of the page
  2. Enter a scenario name
  3. Select up to three rules to include
  4. Configure delays between rules
  5. Click "Create"

Once created, the system tracks sequential execution across the rules. If all rules trigger in order and within the configured delays, the system sends a notification for the whole scenario.

Scenarios are especially useful for:

  • Tracking formation of technical patterns on the chart
  • Identifying sequential changes in trading volumes
  • Finding situations when conditions on one timeframe are followed by others on a different timeframe

Example scenario:

  1. Rule 1: Sharp increase in buy volume on the 5m timeframe
  2. Delay: 15 minutes
  3. Rule 2: Bullish candle on the 15m timeframe
  4. Delay: 30 minutes
  5. Rule 3: Breakout of local resistance on the 1h timeframe

This scenario identifies situations where, after a buy spike, an uptrend forms with a resistance breakout.

Back to top