Skip to content

Alerts ​

Alerts watch every new visit for you and tell you when something you care about happens: a JavaScript error on the checkout, a failed payment request, a visitor rage-clicking, a VIP customer arriving. You choose what to watch for, where to be told (email, Slack, a webhook) and how often at most. Each message links to the visit, so you can watch it right away.

6 minutesSupport, product managers, developers

Where to find it: in the sidebar, under your website, click Alerts (for example Demo Plant Shop › Alerts).

your-replora.com/sites/1/alerts
Three alerts of the Demo Plant Shop, one with a failed Slack delivery, and the latest matching sessions.Three alerts of the Demo Plant Shop, one with a failed Slack delivery, and the latest matching sessions.
Three alerts of the Demo Plant Shop, one with a failed Slack delivery, and the latest matching sessions.

How alerts work ​

  • Each new batch of recording data is checked against the website’s alerts that are on, as it arrives. You’re told within moments of the visit, not the next day.
  • Each session counts once per alert, however many times it hits the trigger.
  • How often sets a quiet time after each notification. Sessions that match during the quiet time are not lost: they are listed as In the next one and sent together in the next notification, when the quiet time ends.

Create an alert ​

  1. Click New alert (top right).
  2. Enter a Name (up to 120 characters), for example Checkout errors.
  3. In Tell me about, choose the trigger, and fill in its text if it has one (see the table below).
  4. Choose where to be told: Email to, Slack incoming webhook, Webhook, or several. At least one is needed.
  5. Choose How often you may be told at most.
  6. Leave On switched on, and click Create alert.
  7. Click Test on the new alert to check the messages arrive.
your-replora.com/sites/1/alerts
The New alert dialog.The New alert dialog.
The New alert dialog.

Triggers ​

Tell me aboutMatches a session when…Extra field
A JavaScript errora JavaScript error happens.Message contains (optional): only errors whose message contains this text, such as TypeError. Empty: any error.
A failed requesta call from the page to a server fails (no answer, or an error status of 400 or higher).Address contains (optional): only calls to addresses containing this, such as /api/. Empty: any failed request.
A rage clicka visitor rage-clicks (the third click within a second in the same spot).None.
A dead clicka visitor clicks something that looks clickable and nothing happens.None.
A session tagthe session gets this tag (set by your site with tagSession).Tag (required, up to 64 characters), such as plan; Value (optional): only when the tag has exactly this value, such as pro.
A visit to a pagea visitor opens a page whose address contains the text.Address contains (required), such as /checkout.

“Contains” ignores upper and lower case. Texts can be up to 500 characters. The alert’s card says in words what it watches for, for example A JavaScript error containing “TypeError” or The tag “plan” set to “pro”.

Channels ​

FieldWhat to enterNotes
Email toUp to 10 addresses, separated by commas (spaces, semicolons and new lines work too).Duplicates are removed.
Slack incoming webhookThe address of a Slack incoming webhook, starting with https://hooks.slack.com/services/…. Create one in Slack (Apps › Incoming Webhooks) for the channel you want.Only Slack incoming-webhook addresses are accepted.
WebhookAny https:// address of your own system (or Zapier, Make…). Replora sends a JSON POST there for each notification.Signed with the header X-Replora-Signature (HMAC-SHA256). Once the alert is saved, the field shows the secret to check the signature with. Details for developers are in the Replora Docs.

Addresses on private networks are refused for security unless the installation allows them.

How often ​

ChoiceMeaning
at most once every 5 minutes
at most once every 15 minutes
at most once an hourThe default.
at most once every 6 hours
at most once a day

After a notification, the alert waits that long before sending the next one; matches in between are bundled into it.

The alerts list ​

Each alert is a card:

PartWhat it shows / does
NameThe alert’s name.
TriggerWhat it watches for, in words.
Small printIts channels (Email, Email (2), Slack, Webhook), how often, and when it was last sent (or never sent).
On / Off switchTurns the alert on or off at once. Turned off, the alert records and sends nothing. Off alerts are greyed out.
TestSends a test message to every channel now (“This is a test of the alert …”). It points at no real session and doesn’t change the alert’s state. You then see “Test sent to Email, Slack” or “Test failed: slack: …” with the reason. Up to 10 tests a minute.
EditOpens the dialog to change anything, then Save.
Delete“Delete this alert?”: the alert and its list of matches are deleted; recordings stay.
Red noticeThe last notification failed: … with the reason, for example a Slack address that no longer exists (The server answered HTTP 404). Fix the address with Edit, then use Test.

Latest matches ​

Under the alerts, the 50 latest sessions that matched any of them:

ColumnMeaning
WhenThe moment it matched. Click to open the replay right there.
AlertWhich alert matched.
What happenedThe detail: the error message, the failed request (POST /api/pay → 500), the clicked element, the tag (plan=pro) or the page.
NotificationSent, or In the next one while the alert is in its quiet time.

Limits and who can do what ​

  • In the SaaS edition your plan sets how many alerts your account may have (all websites together): “Your plan allows n alerts. Upgrade the plan or delete an alert first.”
  • Managers and members create, edit, delete, switch and test alerts. Viewers see the alerts and their matches but can’t change them.

Ideas for alerts ​

NameTriggerChannel
New script errorsA JavaScript error, message left emptySlack #dev, at most once every 15 minutes
Checkout requests failingA failed request, address contains /checkoutSlack #dev
Payment API failingA failed request, address contains /api/paymentWebhook to your on-call tool
Frustrated shoppersA rage clickEmail to the product team, at most once a day
VIP visitA session tag plan = enterpriseEmail to the account manager
Someone reached pricingA visit to a page, address contains /pricingSlack #sales, at most once an hour

Replora: see what your visitors see.