This guide assumes you are familiar with users and company analytics. If not, please review the Introduction to User and Company Analytics
The User/Company Lookup allows you to look up individual customers, like a CRM. You can filter by any user properties like email or company domain. Because Moesif is a User Behavior Analytics platform, you can also filter based on events that a user or company performed (in terms of API calls and user actions).
Note that events may take up to 20 minutes to show up in the user analytics screens. If your data has not shown up, please try again later once the data has had time to filter over.
To see all self-service users who are running into 400 errors, you can add two filters:
- Users that are not on an enterprise plan (a custom user property)
- Users who made at least 1 API calls in last 7 days that resulted in a 400 error
User (or company) filters enable you to filter based on customer properties such as email, name, and created time. Customer properties are stateful and can be updated (such as by yourself to add customer demographic information) or by Moesif itself (such as the Last Seen Time).
User/company filters can be OR’ed and AND’ed together and create complex groupings.
Event filters enable you to filter based on the events a customer performed. A single user or company may have performed multiple events.
Since events represent something performed at a single instance in time, you need to specify the time range to search such as performed within the 24 hrs.
Let’s say we want to look up the users:
Who made at least 10 API Calls in the last 24 hours WHERE the Response.Status was 400 Bad Request AND the route of that API call was either
In this case, the query would look like so:
Events can be one of two types which can be filtered on Event Type filter as shown above:
- API Calls which are the requests hitting your servers such as as
- Actions which are triggered by users within your UI such as
Event filter groups
There are two different ways to think about combining event filters:
- Customers who performed an event matching both X AND Y
- Customers who performed an event matching X AND an event matching Y
Filters within the same group (outlined as a box in Moesif) will match against the same event. Separate groups will match against separate events.
1. Customers who performed an event matching both X AND Y
If you want to match against the same event, ensure your properties are in the same group (outlined as a box in Moesif). Let’s say we want to show all users:
Who made an API call that returned
400 Bad RequestAND the route of that API call was either
In this case, you are matching multiple properties of the same event and the query would look like so:
2. Customers who performed an event matching X AND an event matching Y
If you want to match across different events a user performed, add multiple OR or AND boxes, where each box contains the filters for each single event. Let’s say now we want to match against both an API Call and a Actions so let’s say we want to show all users:
Who made an API call that returned
200 OKto either
/purchases_AND they performed a user action where the Action Name is “Signed-In”
The query should look like so:
Event numeric aggregations
Besides equality, event fields also support aggregations such as average, max, or distinct. For example, we can create a cohort of users who accessed your API with over 10 distinct IP Addresses per hour anytime over the last 7 days. This can be done like so:
With your users/companies table, you can take a variety of actions:
You can modify the columns that are displayed in the table by clicking this button. This is also used to modify the columns selected for export.
For each user or company, you can create an alert such as when a customer’s usage drops or increases. This will open a pop up in the time series view for you to create your alert criteria.
Enterprise customers can bulk export all users or companies based on any filter criteria. Once the export is finished, you will be sent an email where you can download the CSV or JSON file.
Saved cohorts are groups of users defined by their properties and events they performed. An example cohort might be Users who are exceeding rate limits in the last 24 hours. Think of cohorts like a saved list of users that matches some criteria and is continuously updated in the background by Moesif.
You can share the view to a dashboard of your choice. Dashboards make it easier to monitor groups of users over time. Any chart already saved to a dashboard can be modified by clicking the save button. In addition, you can share the chart with others using Share
As seen above, user/company lookup supports two types of filters: