Signals are alerts that Userflow creates for you when a flow's performance changes in a way worth looking at, such as a drop in completions or a jump in element errors. They appear on each flow's analytics page and point to the step causing the change. You don't need to set them up.
What do Signals look for?
Signals compare a flow's performance week over week, month over month, and quarter over quarter, and flag significant changes.
Signal | What it flags |
|---|---|
View changes | Flow views went up or down significantly. |
Completion volume changes | A sudden change in how many users complete the flow. |
Step views analysis (steps with a significant increase in drop-offs) | The step with the highest drop-off rate in each flow, and steps where drop-off has risen significantly. |
Element errors (high element missing errors) | Steps where more than 10% of views end in an "Element not found" error. See Element not found to fix them. |
Where do I see Signals?
Signals appear above a flow's analytics. Each card shows the alert, the metrics behind it, and a link to the step to look at.
.png)
What can I do from a Signal?
Get email alerts: click Subscribe.
.png)
Open the step: click View step in builder to go straight to the step in the Flow builder.
.png)
Add a custom alert: set up an alert policy so you keep getting alerts for that metric. See Setting up custom alerts.
.png)
Dismiss a Signal: click the three dots on the card and select Dismiss alert. If the same trend comes back later, a new Signal may appear.
.png)
Set your business region so weekends and holidays don't trigger Signals
Signals use your business region to allow for normal dips such as weekends and holidays.
Select Settings > Alerting from the sidebar.
Select your business region from the dropdown.
.png)
How many Signals will I see, and for how long?
Userflow shows at most three negative Signals (problems to look at) and one positive Signal (a success) at a time. Each Signal stays for 7 days from when it was created, even if no new data comes in. It's only replaced sooner by a new Signal of the same type for the same flow.
When there are more Signals than fit, Userflow shows them in this order:
Completion rate dropped more than 50%, or to zero
Views dropped more than 50%, or to zero
Other completion rate changes
Other view changes
Element errors
Step-level changes
Why isn't my flow getting Signals?
A flow needs enough activity before Signals can spot a real change:
Signal type | Minimum daily average | Minimum change | Minimum history |
|---|---|---|---|
Views change | 10 daily views | 5 views up or down | 14 days |
Completion rate | 5 daily completions | 5 completions up or down | 14 days |
Step view change | 10 daily views | 5 views up or down | 14 days |
Element errors | None | More than 5 missing element errors | 14 days |
A flow also doesn't get Signals of a type you already cover with a custom alert. For example, if you set a custom alert on a flow's completion rate, you still get Signals for its views, steps, and element errors, but not for its completion rate.
Should I use Signals or custom alerts?
Use both. Custom alerts watch the exact metrics you choose. Signals watch everything else and surface the biggest changes without any setup.
.png)
Add a custom alert to a flow
Create an alert policy in Settings > Alerting. See Setting up custom alerts.
Open the flow's Analytics tab and select Add custom alert.
.png)
Select the alert policy and click Assign alert policy.
.png)