Behavioral Cohorts is a feature that allows you to create a custom definition of a group of users based on not only the events they have performed but also events which they did not perform. This article will show how you can set this up!
Scenario 1: Identify users who were on product in the last 30 days but did not complete Event A.
Amplitude is an event based analytics platform, and Behavioral Cohorts can only identify users who have fired at least one event to Amplitude during your selected timeframe.
In this example, AmpliTunes is the product and I would like to better understand users who did not fire "Favorite Song or Video" in the last 30 days. To create this cohort, I will need to utilize the "And not who" clause, which can be found as an option if you click on "And also".
The "And not who" clause will exclude users who have fired "Favorite Song or Video" at least once in the last 30 days. This will in turn help me identify users who have not performed this event.
Scenario 2: Identify users who lack a particular user property in the last 30 days.
Let's say that you would like to identify all the active users who did not become a paying user at any point in time during the last 30 days. In order to query for this, you'll have to once again utilize the "And not who" clause which is found as an option if you click on "And also".
Instead of identifying users who have "Paying = false" at any time in the last 30 days, I'll need to identify users who did not have "Paying = true" during that same timeframe. The reason why is that I only want users who did not pay during the entire 30 day timeframe.
If a user was not a paying user at the start of the month but became a paying user by end of this month, querying for users who have "Paying = false" at any time in the last 30 days will identify this user.