# Alert rules

URL: https://storelift.net/features/alert-rules/
Language: en
Updated: 2026-09-18

An alert is worth having only if it is rare. Ours are built from the difference between two measurement runs, and the thresholds are deliberately high: a move of fewer than ten places is not an event, it is a Tuesday.

## In measured numbers

Every figure on this page is read from a code path, not written by hand — the same discipline the product applies to your own data.

## The six things we detect

| Alert | What triggers it | Why it is separate |
| --- | --- | --- |
| Dropped out | Was ranked, now returns no position at all | Always an alert, whatever your threshold — you left the measured depth |
| Rank drop | Fell by at least your threshold (10 by default) | The threshold is yours; below it is daily noise |
| Entered | Was unranked, now has a position | A new term arriving is news you would otherwise find weeks later |
| Rank rise | Climbed by at least your threshold | Separated from drops in Aug 2026: one switch sent both, and people who asked for drops got "#123 → #14" |
| Rival passed you | An app that was behind you is now ahead | Only for apps that were previously behind — otherwise every competitor is an alert |
| You passed a rival | You moved ahead of a tracked rival | Only when your own rank improved and the rival's new rank was measured |

NOTE: Both rival alerts require that both measurements ranked. Comparing a measured day to an unmeasured one would report a pass that never happened — the three measurement states apply here too.

## How it works

1. Two runs are compared. Each nightly run at 02:10 UTC is diffed against the last delivered one, so a night that failed does not silently erase the change.
2. Your rules filter it. One threshold for both drops and rises, separate switches per alert type, and a scope: all keywords, or only the ones you tagged.
3. It lands in the dashboard first. The alert list is always there; channels are additional, not a replacement.
4. Connected channels get pushed. Telegram, Slack and webhook — whichever you have connected.

NOTE: If you narrow the scope to tagged keywords but have not tagged anything, the scope is ignored rather than silencing everything. A rule that quietly stops producing alerts gets read as a broken product.

## What you do with it



## What this does not do

Email is not a channel here, and that is a decision rather than a gap: alerts are about your app, and mixing them into the same inbox as our own product mail made both harder to read. It was removed in September 2026. Alerts also do not predict — nothing here tells you a drop is coming, only that one happened between two measurements.

## What each plan includes

|  | Free | Pro | Studio |
| --- | --- | --- | --- |
| Alert list in the dashboard | Yes | Yes | Yes |
| Custom threshold | Yes | Yes | Yes |
| Telegram · Slack · webhook | Yes | Yes | Yes |
| Keywords the rules can watch | 25 | 250 | 500 |
| Storefronts watched | 2 | All 128 | All 128 |

Pro is $20/month ($18 billed yearly), Studio $60/month ($54 billed yearly). Alerts themselves are on every plan; what scales is how many keyword × storefront pairs they can watch.

## FAQ

Q: How big a drop triggers an alert?
A: Ten places by default, and you can change it. Anything smaller is ordinary daily movement in store search — sending it would train you to ignore the channel.

Q: Can I get alerts by email?
A: No. The email channel was removed in September 2026 because app alerts and our own product mail were landing in the same inbox. Telegram, Slack and webhook are the delivery channels; the dashboard list is always there.

Q: Will I be told when a competitor overtakes me?
A: Yes, but only for an app that was previously behind you, and only when both days were actually measured. Otherwise every app above you would generate an alert every night.

Q: What happens if a measurement run fails?
A: The comparison waits. The next successful run is diffed against the last delivered one, so the change is reported late rather than lost.