Alerts
The Alerts tab surfaces operational issues with the Listening data collection system. When a browser profile has a problem or data collection falls behind, an alert is raised here so your team can take action.
Alert Types
| Type | Meaning |
|---|---|
| Data Issue | A profile has not collected data recently — session cookies may be expiring |
| Login Failed | A browser profile could not authenticate to a platform |
| Challenge | A CAPTCHA or two-factor prompt was encountered and needs admin input |
| Cookie Expired | The session for a profile has expired and needs to be refreshed |
| Rate Limited | A platform is temporarily throttling collection for a profile |
| Zero Yield | A monitoring job ran but collected no new mentions |
| Proxy Error | The proxy assigned to a profile is unreachable |
Responding to Alerts
Acknowledge All — marks all current alerts as seen without dismissing them.
Dismiss — removes an individual alert from the list once the issue is resolved.
For Challenge alerts (CAPTCHA / 2FA), an administrator must:
- Open the alert to see the screenshot of the challenge page
- Submit the required OTP or CAPTCHA response
- The profile resumes collecting automatically on success
Alert Notifications
Critical alerts (Login Failed, Challenge, Proxy Error) are also sent via Slack or email if your administrator has configured notification channels in the Listening → Setup settings.
Updated 5 days ago
