🎉  Userflow joins forces with Beamer to create all-in-one growth toolkit

Read more
blog single image
blog single image
Userflow Updates

Filter event conditions by attributes

blog author
Sebastian Seilund

December 4, 2020

Here's a new 😋 feature, which gives you an even more powerful way to target users or adapt to their behavior.

Event conditions can already be used in Auto-start conditions for flows, Completed conditions for tasks etc. Example: Start a flow when a user changes their subscription plan.

When your app tracks an event, it may add additional information about the event in the form of event attributes. Here's an example of when a user changes their subscription plan, and we want to know which plan they change to:

userflow.track('subscription_plan_changed', {plan_id: 'pro'})

The new thing: Event conditions now support filtering based on these event attributes. Example: Start a flow when a user changes to the Pro subscription plan specifically.

Event condition where

Notice the new "Where Plan Id is pro" part.

Just like with regular user attribute conditions, you can add multiple event attribute conditions. The attributes can be strings, which you can compare with equality (is/is not) or whether they contain a substring. They can also be integers, which you can use to compare using equality, less than, greater than, etc. Date and boolean event attributes work, too!

You can even use this with Userflow-generated events, such as Flow Started, to e.g. start one flow 7 days after a user completes another flow:

Event condition where

2 min 33 sec. read

blog single image
Userflow Updates

Filter event conditions by attributes

blog author
Sebastian Seilund

December 4, 2020

Here's a new 😋 feature, which gives you an even more powerful way to target users or adapt to their behavior.

Event conditions can already be used in Auto-start conditions for flows, Completed conditions for tasks etc. Example: Start a flow when a user changes their subscription plan.

When your app tracks an event, it may add additional information about the event in the form of event attributes. Here's an example of when a user changes their subscription plan, and we want to know which plan they change to:

userflow.track('subscription_plan_changed', {plan_id: 'pro'})

The new thing: Event conditions now support filtering based on these event attributes. Example: Start a flow when a user changes to the Pro subscription plan specifically.

Event condition where

Notice the new "Where Plan Id is pro" part.

Just like with regular user attribute conditions, you can add multiple event attribute conditions. The attributes can be strings, which you can compare with equality (is/is not) or whether they contain a substring. They can also be integers, which you can use to compare using equality, less than, greater than, etc. Date and boolean event attributes work, too!

You can even use this with Userflow-generated events, such as Flow Started, to e.g. start one flow 7 days after a user completes another flow:

Event condition where

2 min 33 sec. read

Here's a new 😋 feature, which gives you an even more powerful way to target users or adapt to their behavior.

Event conditions can already be used in Auto-start conditions for flows, Completed conditions for tasks etc. Example: Start a flow when a user changes their subscription plan.

When your app tracks an event, it may add additional information about the event in the form of event attributes. Here's an example of when a user changes their subscription plan, and we want to know which plan they change to:

userflow.track('subscription_plan_changed', {plan_id: 'pro'})

The new thing: Event conditions now support filtering based on these event attributes. Example: Start a flow when a user changes to the Pro subscription plan specifically.

Event condition where

Notice the new "Where Plan Id is pro" part.

Just like with regular user attribute conditions, you can add multiple event attribute conditions. The attributes can be strings, which you can compare with equality (is/is not) or whether they contain a substring. They can also be integers, which you can use to compare using equality, less than, greater than, etc. Date and boolean event attributes work, too!

You can even use this with Userflow-generated events, such as Flow Started, to e.g. start one flow 7 days after a user completes another flow:

Event condition where

About the author

Co-Founder of Userflow

Sebastian Seilund is the co-founder and former CEO of Userflow, where he built one of the leading user onboarding platforms for SaaS companies. With experience as a software engineer at Google and having founded multiple successful software companies, including Denmark's first user-friendly accounting software, Sebastian brings deep technical expertise to discussions about product-led growth and user experience.

Effortless Onboarding,
Powerful Results

Try the most-loved user onboarding product on the market.

CASE STUDIES

All case studies
iconicon

Evocalize

a case study

How Evocalize Boosted Product Adoption and Engagement With Userflow 

Learn how
iconicon

Visma Dinero

a case study

How Visma Dinero provides 24/7 onboarding and support with in-app content and AI Assistant.

Learn how
iconicon

Iteratively

a case study

How Iteratively gives users an awesome first-time experience

Learn how
iconicon