Marketplace Alerts
What fires, what deliberately does not, and how the thresholds work.
Alerts watch a campaign run to run and tell you when something moved enough to be worth reading. They are evaluated per target, so a campaign watching four shelves can report four independent stories.
What fires
Section titled “What fires”| Alert | When | Severity |
|---|---|---|
| Entered the top 10 | Your best position on a target crossed into the top 10 | Success |
| Left the top 10 | It crossed back out | Error |
| Rank changed | Your position moved by 3 places or more | Success or warning |
| Price changed | A listing on the shelf repriced by 10% or more — yours or a competitor’s | Info or warning |
Price alerts are the ones a rank tracker usually cannot give you. A competitor undercutting you by 15% is at least as actionable as a rank slip, and it is often the cause of one.
What deliberately does not fire
Section titled “What deliberately does not fire”Most of the design here is about not sending things.
A single bad page. Each run is one page load, and pages disagree. A product sitting at 8, 9 and 25 across three runs is an 8–9 product that hit one bad page — so the window uses the median of each run’s measurement, not the average and not the best. The median says 9 and stays quiet; the average would say 14 and the best would say 8, and both would alert on the anomaly instead of the trend.
A new campaign. Comparing a first run against nothing would fire “entered the top 10” for every product you track, on the day you created the campaign. Both sides of the comparison need at least two runs.
A stale baseline. The comparison reaches back at most 45 days. A campaign that ran three times last week and three times two months ago would otherwise compare this week against two months ago and report all the drift in between as one sudden move.
A target seen once. If a target only appeared in one run of a window, it is skipped. That is a single page load, not a trend.
Small wobbles. Under 3 positions, or under a 10% price move, nothing is sent.
Where alerts arrive
Section titled “Where alerts arrive”| Channel | What arrives |
|---|---|
| In-app | Every alert, in the notification feed |
| Every alert, batched: at most one email per hour per organization | |
| Webhook | Every alert, if a webhook URL is set on the campaign |
Alert emails are batched per organization, the same way they are for every tracker. Owners receive at most one email per hour, carrying every alert raised across all campaigns since the last one, grouped by campaign, so a run that moves five keywords is one email, not five. A lone alert can therefore take up to an hour to reach the inbox; the in-app feed and the webhook get it at once. Each owner can turn alert emails off in their notification preferences.
Turning them on
Section titled “Turning them on”Alerts are configured per campaign, in the wizard’s schedule step. You can switch the top-10 transitions, rank changes and price moves on or off individually, keep the campaign out of the alert email with its “Email alerts” switch (the feed and the webhook are unaffected), and set a webhook URL for outbound delivery.
Alerts only evaluate after a run that produced data — a run that failed entirely never triggers them.
Related
Section titled “Related”- Metrics and results — what the numbers behind an alert mean
- Schedules and alerts — how scheduling works across all trackers
- Webhooks — payload format and delivery