Why you did not receive an alert
Check your sensitivity setting first, since most missing alerts are below the threshold rather than lost.
You expected an alert and none arrived.
Most common cause: the change did not clear your sensitivity threshold
Open Alerts and check your current sensitivity setting. A change that is real but small may simply sit below the level you have set. See Setting alert sensitivity to lower it.
Other causes, by how often they happen
Note
These are ordered by frequency. Work through them in order rather than jumping to the last one.
- Delivery is set somewhere you are not checking, such as Slack only when you expected in-app, or the other way round. See Choosing where alerts are delivered.
- The competitor or source is muted. See Muting a competitor or source.
- The change genuinely did not clear the bar for significance at all, even before sensitivity is considered.
- An integration such as Slack has been disconnected. See Slack alerts stopped arriving.
If none of this fixes it
Send the competitor, the change you expected an alert for, and roughly when you expected it, using the request option below.
Was this useful?
Related articles
- Setting alert sensitivity
Raise or lower how significant a change needs to be before it triggers an alert.
- Muting a competitor or source
Mute a competitor or source to stop alerts from it without removing it from tracking.
- Choose where alerts are delivered
Choose whether alerts appear in-app, in Slack, or both.
- What counts as a significant change
Significance is one shared judgement behind The Read, the Action Plan and alerts, and it is specific to your workspace.
Still stuck?
Send this to the team and we will pick it up.