Blog

We’ve changed the standard behavior of when a tooltip target can’t be found. Previously, if you used our standard themes, the following message would be shown:

Going forward, the flow will auto-dismiss if the tooltip target is not found within 3 seconds.

We’re making this change in an effort to get more out of the user’s way. Only in cases where it’s absolutely necessary for the user to complete a guide, do we recommend presenting the user with the above message. In most regular onboarding flows or feature announcements, if the user does navigate away, it’s most likely that they just don’t want to continue the tour. Therefore we feel it’s better to err on the side of just dismissing the flow and let the user continue unhindered.

This change only applies if you’re using one of our standard themes. If you’re using a custom theme, the setting you had under Tooltip → Missing tooltip target behavior still applies. You can, of course, change that if you wish. Read more in our Missing tooltip target behavior guide.

We’ve renamed our Groups feature to now be called Companies instead.

The word “group” was originally chosen because it was a broader term than “company”, meaning it could cover both companies, accounts, teams, organizations etc. - whatever term our customers may use to group multiple users belonging to the same entity together. Another reason was that popular tools used the term, too, such as Segment’s analytics.group() JavaScript API.

We’ve come to the conclusion that “groups” is a confusing term, and is often misunderstood as “segments” (which we also have).

To make the distinction crystal clear, Groups is now Companies 🤓

For now, this is solely a terminology rewording, and no actions are required of you. We’ve updated our UI and documentation use the word “company” everywhere possible. Userflow.js has not changed and still uses userflow.group(), just like the REST API has not changed and still uses endpoint URLs such as /groups and group_id for object properties.

What tools do you actually need in a product-led stack?

Read full post

We’ve made it easier to conditionally show content depending on the current time. The 2 most common use cases for this are:

• Publishing content that shouldn’t go live until a specific time in the future. For example, a feature launch coming up in a few days, or a message related to the time of year, such as remembering a reporting deadline.
• Automatically stop showing content after a period time, after which it’s no longer relevant. For example, a new feature that won’t be new in 3 months.

Simply use the new Current time condition. It works under any Add condition button in the builder. You can either fill in one of the 2 time fields, or both of them.

It’s now much easier to set up recurring flows that start up to a specific number of times, spaced out over time.

The drop-down now contains a new option, Start a specific number of times per user, which, when selected, lets you pick how many times the flow may start.

This option, as well as for Start unlimited times per user, now also allows you to specify a minimum number of minutes/hours/days that has to pass since the flow was last dismissed before it may start again.

Bonus tip: If you only want to show the flow again if the user has not already completed it, you simply add that to the auto-start condition:

You can now use any icon of your choosing in resource center blocks and launchers.

The icon selector still supports a small selection of built-in icons. But now you can also choose to upload your own icon, or enter the URL to an icon hosted elsewhere.

Conditions, such as in triggers and Auto-start flow rules, now support waiting a specified number of seconds before performing actions or starting a flow.

This allows you to, for example, wait a few seconds after a user arrives on a page before starting a flow, or automatically continuing to the next step after a short delay.

Use the new Wait option in the Add condition popover.

Then choose the desired number of seconds to wait.

That’s it!

You can now manually add/remove specific users/groups to our new manual segments. This allows you to easily target specific users in your Userflow content. Example use cases:

• Manually maintain a list of beta users.
• Import (via CSV upload) a segment of users from another tool, such as your CRM.

To add a new manual segment, simply click the + New button on the Users or Groups pages.

Read full post

The Users and Groups pages now support exporting the whole list as CSV.

This is useful if you want to do your own analysis in a spreadsheet, or want to import some or all users into another system by hand.

Simply click the export icon in the top right. The exported file will use the same ordering and filters as the list. You can either export only the displayed columns or all available columns.

You can now continuously sync Amplitude cohorts to Userflow.

This way you can use Amplitude’s more advanced conditions for targeting users that should see specific content from Userflow.

It’s super easy to set up. Check the Amplitude integration docs.