Skip to main content
Alerts are how Replayfy tells you when something you care about happens again — without you having to keep the dashboard open. Replayfy already detects issues, signals, and conversion trends across your web and mobile sessions; an alert is a standing subscription that says where to notify you when one of them fires. Alerts are email-first. Every alert can email a list of recipients, and funnel-conversion alerts are delivered by email only. Recurrence and threshold alerts also drop into the in-app notification bell and can fan out to a connected channel like PagerDuty, Slack, or a webhook.
You manage alerts on the Alerts page at app.replayfy.app/alerts. Alerts are born from the feature you’re watching — a funnel, an issue, or a signal — and then live on the Alerts page for you to retune, re-route, pause, or remove.

Alert types

Replayfy has four kinds of alert. Which one you get depends on what you were looking at when you created it.
Metric-threshold alerts watch the same daily counters the dashboard shows — crashes, backend failures, slow API calls, frustrated sessions, form abandonment, navigation loops, conversion failures, conversion successes, and health score. An alert never watches an invented metric.

How alerts get created

The Alerts page is a management surface, not a builder — you create each alert from the thing it watches.
Open a saved funnel and choose Alert on this funnel from the builder header. Pick a condition, add recipients, and Replayfy checks the funnel’s conversion once a day. See the Funnels guide for building the funnel first.
Open an issue and ask Replayfy to watch it, or tell Replayfy AI “alert me if this issue comes back.” The alert fires the moment the issue regresses (resolved → back again).
On a dashboard signal, choose Create alert. It’s baselined to the signal’s current activity, so it only notifies you about future recurrence — never the activity you’re looking at right now.
Ask Replayfy AI something like “email me if crashes go above 50 today.” The AI can create threshold and recurrence alerts on your behalf; editing, pausing, and deleting them stay with you on the Alerts page.

Create a funnel-conversion alert

1

Open a saved funnel

Go to Funnels, open the funnel you want to watch, and click Alert on this funnel in the builder header. The funnel must be saved first.
2

Choose a condition

Pick Drops by (a relative drop versus the previous window) or Falls below (a fixed conversion percentage), then set the threshold. The comparison window comes from the funnel’s own window in days.
3

Add recipients

Your account email is pre-filled. Type any additional addresses and press Enter or comma to add each one. Remove anyone you don’t want.
4

Create the alert

Click Create alert. Replayfy checks conversion once daily off the conversion history and emails everyone on the list when the condition is met.

The condition model

Every alert that isn’t a plain “watch this again” subscription is defined by a small, consistent condition: a comparator, a threshold, and — for funnel alerts — a window in days. Here’s how the same funnel alert reads as a stored condition for each comparator:
Funnel-conversion alerts need enough traffic to be trustworthy. A window with very few entrants won’t fire, and a DROP_PCT alert also needs a healthy prior window to compare against — so a quiet day never triggers a false alarm.

Email delivery and recipients

Email is the primary channel for alerts, and the only channel for funnel-conversion alerts.
  • Multiple recipients. Funnel-conversion alerts carry a recipient list. Add as many teammates as you need (up to 20); duplicates and malformed addresses are dropped automatically.
  • Sensible default. Leave the recipient list empty and the alert emails the person who created it, using their Replayfy account email. The funnel builder pre-fills your own address so there’s always at least one recipient.
  • What lands in the inbox. Each email names the alert, describes exactly what happened (for example, “Checkout conversion is 31.4% — down 22% from 40.1% over the last 7 days”), and — for funnel alerts — includes a View funnel button that deep-links straight back to the dashboard.
Email recipients are addresses you or your teammates enter explicitly. Replayfy never emails an address it inferred — an alert only reaches its recipient list or, as a fallback, the creator’s account email.

Delivery channels

For recurrence and threshold alerts you can route to an external channel in addition to the bell and email. A provider only appears as a choice once you’ve connected it — an alert can’t route somewhere that would silently never deliver.
Connect PagerDuty, Slack, or a webhook per-workspace under Settings → Integrations. See Integrations to set one up, then pick it from the alert’s channel picker.

Managing alerts on the Alerts page

The Alerts page lists every alert in the workspace, newest first, with a stat row at the top (total alerts, how many are watching an issue, and how many are paused). Each row shows what the alert is watching, its channel, and when it last fired.
1

Open the Alerts page

2

Open a row's menu

Click the menu at the end of any alert row.
3

Manage or re-route it

For a funnel-conversion alert, choose Manage alert to edit the comparator, threshold, window in days, and the email recipient list. For an issue, signal, or metric alert, choose Change channel to pick which connected channels it routes to (the in-app bell is always on, and the email leg is shown).
4

Remove it when you're done

Choose Unsubscribe from issue (for an issue-recurrence alert — the issue itself stays, only the subscription is removed) or Delete alert. Both stop the notifications immediately and can’t be undone.
An alert that has been paused stops firing without being deleted and shows a Paused badge in its Last fired column — useful for muting a noisy alert during a known incident or a planned change.
A row labels itself by exactly what it watches. If a watched issue is later deleted, the alert honestly reads “Issue unavailable” rather than inventing a title — so the list never lies about what it’s tracking.

When alerts fire

Different alerts are evaluated on different cadences, matched to how quickly their underlying data changes.
Every alert has a cooldown: once it fires, it won’t notify you again for the same ongoing condition for about six hours. A still-breaching alert folds into a single ongoing notification instead of paging you every tick.

Funnels

Build a conversion funnel, then attach a funnel-conversion alert to it.

Integrations

Connect PagerDuty, Slack, or a webhook to route alerts beyond email.

Crashlytics

See how Replayfy detects the issues that recurrence alerts watch.