Setting up an alert that will not spam you

A walk through the New alert form: conditions, repeat mode, hold, dedup and routes, in order.

Short answer

An alert is a rule: a set of conditions that must all hold at the same time, and the routes a message is sent to. What usually spams is not the rule but conditions that are too wide — one coin across ten venues is dozens of spreads, and each one fires for itself.

Three fields on the form are the defence: When to send, Must hold for and Count repeats by. They are explained below where you meet them.

Creating a rule

1. Open Alerts in the top navigation. The Rules tab is the list; Journal is what has

already fired.

1. Press New alert.
2. In Name, say what the rule is for — the field suggests "e.g. Fat entries". The name shows in

the list and in every message, so it has to explain itself a month from now.

1. The block Fires when (all conditions at once) holds the same filters as the scanner: venues,

coins, class, status, spread and funding thresholds. Each condition reads exactly the number the table's column shows.

1. Under the conditions the form says how many spreads match right now. That is your noise meter.

Above thirty a minute the rule stops itself — narrow the venues or the coins.

The three fields that stop the noise

When to send — how the rule fires again while the condition stays true:

| when to send | how many messages | when it fits | |---|---|---| | Only once | one, ever | a one-off event you are waiting for | | Per streak | one each time the condition becomes true | the spread comes and goes and every visit matters | | Throttled | no more than once per window (the No more than once every field) | the condition holds for a long time and you want the odd reminder | | Every cycle | on every recomputation | almost never: this is the loudest setting there is |

Must hold for — how long the condition has to survive before the first message. Flicker around the threshold resets the clock. Zero means send on the first match.

Count repeats by — what counts as "already sent": a spread or a coin. Ten venues of one coin under "coin" is one message instead of ten. If the rule is about a coin rather than a specific pair of venues, pick the coin.

Where it goes

The Send to block: App (toasts and the bell inside the product), Sound (a tone with the toast), Telegram (the bot's direct messages), Browser (a system notification while the tab is open).

The journal is always written, whatever routes you pick. A rule with no routes at all is not lost — its fires show up under the Journal tab.

A route that is not connected yet is disabled and labelled "This route is unavailable until it is connected". Telegram and browser notifications are connected on this same page.

Then press Create.

An alert on one spread

A rule made from the Alerts page watches every spread that passes its conditions. When you want one specific spread, open its card and create the alert there: the form copies the conditions from the table and the rule watches that spread only.

If something is off

• The rule will not let you edit it. Edit is disabled while the rule is enabled — the tooltip

says so: "Disable the rule to edit it". Disable, change, enable again.

• The rule switched itself off. It passed thirty fires in a minute. Restart puts it back, but

narrow the conditions first or it will happen again.

• It will not save. The form names what is missing: "Name the rule", "Add at least one condition

with a value", "Set the pause window".

• More than fifty rules. That is the cap; delete one to add another.