Alerting

Alerting in Userflow helps you keep a close watch on the performance of your content. It notifies you, for instance, if a flow’s views fall below a set limit within a certain timeframe or if its completion rate drops. This is especially valuable if an unintended change occurs in your Userflow.js configuration or there’s a significant alteration in your app’s elements.

Alerting is exclusively available on our Pro and Enterprise plans.

Alert policies

Set up alert policies in Userflow to monitor flows, checklists, and launchers. Configure notifications to trigger when:

• Unique views drop below a specified threshold within a defined timeframe.

• Activation or completion rates decline from expected levels.

• Missing tooltip target rate exceeds an acceptable threshold.

These alerts help identify potential issues with auto-start conditions, targeting rules, or flow performance, enabling quick intervention before user experience is impacted.

Create alert policies

1. Select Settings > Alerting from the sidebar.
   

2. Click the New button corresponding to the alert type you want to create – a Flow, Checklist, or Launcher policy.

3. Enter a policy name.
   

4. Use the toggle switch to activate one or more metrics to monitor, then enter the number or percentage threshold and duration for each. For example, 25 unique views over 4 days or a 50% drop over 5 days.

   • Unique views (All policy types)

   • Completion rate (Flows & Checklists)

   • Missing tooltip target rate (Flows)

   • Activation rate (Launchers)

5. By default, the Notify by email toggle switch will be activated with the checkbox selected for the user creating the alert. Add email addresses for (up to eight) additional recipients in the spaces provided.

   Regardless of whether email alerts are active for a policy, alerts will appear at the top of the flow.
   

6. Use the toggle switch to activate monitoring for the desired environments.

7. To designate the new policy as a default for all future Flows, Checklists, or Launchers, select the checkbox to make it the default policy.

8. Click Create alert policy.

9. If Flows, Checklists, or Launchers already exist, you will be prompted to select which flows this policy should be assigned to.
   
   Here you can:
   - Select all
   - Select all with no policy
   - Deselect all
   - Select individual items

10. Click Save assignments.

Manage alert assignments or edit/delete a policy

After creating an alert policy, you can manage the Flows, Checklists, or Launchers it is assigned to, or edit or delete a policy. From the Alerting settings, click the options menu next to a policy and select the desired option. Complete the prompts that follow.

Alert checking, triggering, and resolving

Every 6 hours, we evaluate all content items against their respective alert policies.

An alert is triggered if all of the following is true:

• The content item is assigned to an alert policy.  

• The policy is monitoring the environment.  

• The content item is published in the environment.  

• Alerts are not muted for the content item.  

• Any monitored metric falls below the defined threshold.  

• The content item has been published for a duration equal to or longer than the chosen metric’s timeframe. Example: If a policy monitors “over 3 days”, it does not make sense to trigger an alert until the content item has been published for at least 3 days.  

Triggered alerts result in immediate email notifications:

An alert remains active until the concerning metric meets or surpasses the threshold. Once resolved, another email notification is sent.

The Userflow UI displays active alerts in 3 places:

1. The Content list highlights items with ongoing alerts via a red bell icon.  

2. The Builder page displays a red bar at the top.  

3. Similarly, the Analytics page showcases a red alert bar.  

Muting alerts

After addressing the underlying issue of an alert, you can choose to mute it for a specific period, like a day.

Just select Mute alerts from the three-dot menu on the Analytics page.

Muted alerts are auto-resolved silently, meaning no email notifications are sent. Alert checks remain paused during the mute period and resume afterwards. A fresh alert only triggers after the mute period if the metric is still below the defined threshold.

When you mute alerts, the active alert will be silently be resolved (i.e. no notification email is sent), and the alert check won’t run for the mute period you select. Once the mute period ends, the content item will be checked again. Only if the monitored metric’s threshold is failed to be met, another alert will be triggered.