Features
Slack Notifications
Post to a Slack channel when Argus finishes an analysis, rage clicks or errors spike, the first session arrives, or usage nears the monthly limit.
A project can post short messages to one Slack channel, so your team hears about the things worth a look without keeping the dashboard open. Each message says what happened, gives the numbers, and has one button that opens the right page in AnyReplay.
Connecting a channel
Create an incoming webhook in Slack
In Slack, add the Incoming Webhooks app to your workspace (from the App Directory), choose the channel and copy the URL it gives you. It starts with
https://hooks.slack.com/services/. Your workspace may need an admin to approve the app.Paste it in AnyReplay
Open the project's Settings → Slack notifications, paste the URL, choose the events and press Connect Slack. Owners and admins can do this; everyone else on the project sees whether it is connected.
Send a test message
Press Send test message. If it arrives, you are done. If Slack refuses it, the card shows Slack's reason.
Each project has its own channel setting, so a storefront and a marketing site can post to different channels, or both to the same one.
What is sent
| Event | When it is sent |
|---|---|
| Argus finishes an analysis | When a project analysis is ready: how many sessions were read, how many findings there are and how many are new since the last analysis, tracked issues that were resolved or got worse, and the three most serious problems. Only on plans that include Argus. |
| Rage clicks spike | When the last hour clearly had more sessions with rage clicks than usual (the rule is below). Lists the pages those sessions started on. |
| Errors spike | The same rule for sessions in which the recorder saw an uncaught error. |
| The first session arrives | Once, within a minute or so of the project recording its first session. |
| Usage reaches 90% or 100% | When the organisation reaches 90% or 100% of its monthly sessions or recording hours. Sent once per channel, even when several projects post to it. |
Every event is on when you connect. Untick the ones you do not want and press Save changes.
When a spike counts
Every ten minutes AnyReplay compares the last hour with the seven days before it. A spike alert is sent when all of these are true:
- At least 5 sessions in the last hour had rage clicks (or errors).
- That is at least 3 times the project's usual number for an hour, averaged over the previous seven days.
- Those sessions are at least twice the usual share of all sessions, so a busy afternoon with more visitors is not mistaken for more people getting stuck.
- The project has been recording for at least a day, so there is a "usual" to compare with.
After an alert, the same kind of alert for the same project waits six hours, so a long spike is one message rather than one every ten minutes. The button opens the session list filtered to that hour and that kind of session.
What a message never contains
A Slack channel is often read by people who are not members of your AnyReplay organisation, and Slack keeps its messages under its own terms. So messages carry counts, project names, Argus's finding titles and page addresses without their query strings or fragments — the part of a URL where sites tend to put tokens, search terms and email addresses. They never contain a visitor's name, email address, user id or anything typed into the page.
How the webhook URL is kept
Anyone with the webhook URL can post to the channel, so AnyReplay treats it as a secret. It is stored encrypted, and after you save it the dashboard and the API only ever show a hint such as hooks.slack.com/services/T…/…abcd. It is not included in data exports or the audit log. To change the channel, press Replace webhook and paste a new URL.
Only Slack incoming-webhook URLs are accepted: exactly https://hooks.slack.com/services/…. Workflow Builder webhooks (/workflows/…) are not supported, because they expect the variables a workflow defines rather than a message.
When Slack stops accepting messages
If Slack answers that the webhook is gone — the channel was archived or deleted, the webhook was removed, or the app was uninstalled — AnyReplay marks the connection as broken and sends nothing more. The settings card shows a warning with Slack's reason. Paste a new webhook URL to reconnect; if you have brought the channel back, Send test message reconnects the existing one when it gets through.
Other failures are not treated as permanent. A message that gets no answer within five seconds is dropped, and one that Slack rate-limits or fails on its side is tried once more after the delay Slack asks for. Notifications are best effort: a message that could not be delivered is not queued for later.
Plans and the audit log
Slack notifications are on every plan. The Argus event only happens on plans that include Argus, since that is where analyses run. Connecting and disconnecting a channel are written to the organisation's audit log, with the hint and never the URL.