How to create dynamic user properties from your users' actions

[enague]

What are Behavioral Breakdowns?

Imagine you are looking at your users and you’ve already implemented the user properties that are static like name, email, etc. However, you want to take it a step further and create dynamic user properties from actions your users have taken in your app.

For example, let’s say you wanted to create a cohort of users that created more than 5 channels in the last 30 days. You may not be tracking the number of channels created as a user property, but as long as you have the event you can create a cohort using “Behavioral Properties.”

Where can I find it?

There are two ways to see these behavioral metrics. You can see this in our Insights report and our Users page, so I’ll explain where to find these below and what the difference is between the two.

1. Go to the Insights report and click on “Frequency Per User.” Let’s say you are in our Media Demo Project and want to find an answer to this question: Out of all my users who do the event “Comment,” how many times do they also do the event “Watch Video”? You can see an example report in our demo project here.

Check out this log entry for a Loom walkthrough on how to use Behavioral Properties in our Insights report.

2. You can do this on our Users page as well to address the use case defined above, but the key difference is that you are able to see this in a column on the Users page versus seeing this in an Insights report. Please note: the behavioral properties created on the Users page are not accessible in other core reports.

To get to it, first, navigate to the Users Page, click on “Edit Columns”, scroll down, and click on “Create Custom”. Then, click on “Behavioral Property” (as shown in the screenshot below).

How do I use it?

From there, you can create a custom property that tallies the total number of times a user performs a specified event or aggregate a specified property on the specified event similar to what you would do in an Insights report. The difference here is that this is making a user property instead of a filter or breakdown on our core reports as explained above.

Common Gotchas

• You would not be able to see this behavioral property in custom properties.
• The created behavioral property is not visible on the user profile view — only on the Users Page.

Hope that helps! If you are not part of our Slack Community yet, feel free to join us at this link here.