Blog

You can now test auto-start conditions for your flows/checklists directly in the builder, without having to publish them first.

If you use one of our CRM integrations (e.g. Salesforce or HubSpot), you might have noticed that we prefix fields created in the CRM with userflow_user_ or userflow_company_.

For testing purposes, you can now mark announcements as unread. Go to the announcements' Analytics tab, then find the user in the list under Users that saw this announcement, and finally click Mark as unread in the three-dot menu.

Until now, launchers were always hidden while a flow was active. We've added a new setting in the launcher builder: Show launcher while flows are active If you enable this setting, the launcher will keep showing even while a flow is active.

To make it easy to tell when you're in a Staging environment in Userflow, we now mark the UI with a yellow top border and the name of the environment. This is shown in places where data/analytics is related to just that environment.

We've now made it possible to change the alignment of buttons directly in the builder. Simply select a button, then use the new Button alignment tool in the toolbar.

Announcements offers a straightforward and effective method for sharing updates directly within your app's resource center. Picture it as a modern, digital bulletin board where you can effortlessly display information about new features, improvements, or any other news that matters to your users.

We've got something new for you: Banners! Straightforward and effective, these are designed to help you communicate better within your app.

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.

The Step funnel (found on the Analytics tab for flows) now displays how often a tooltip step's target element could not be found in your app.