Beta Feature: Filtered metrics for event parameters

Thanks for being a beta tester for one of our new features!

All Leanplum users can see analytics and metrics for their app's events, but not for all the parameters associated with those events. With the standard platform, metrics are possible for parameters with numeric values only. 

Filtered Metrics allow you to create metric tiles filtered by any event Parameters, even those that aren't numeric values. This is especially useful for customers who use event parameters frequently. Filtered Metrics can also be used to create new Custom Metrics or A/B test goals, just like any other metric.

Create a Filtered Metric

For example, let's say you send Leanplum an Event called "Sign Up" which has an Event Parameter called eventAction with values such as Facebook, Google, email, etc.

We can create a Filtered Metric for one specific parameter value for this event. Let's define a Metric Tile called "Facebook Signups" which is the occurrences of "Sign Up" only where parameter "eventAction" = "Facebook".

  1. In the Analytics space, under Favorites, click the + tile to create a new metric.
  2. Select Filtered metrics from the menu sidebar.
  3. Click + Create new filtered metric.
  4. Enter a metric name ("Facebook Signups").
  5. Select the Event ("Sign up") from the Event chooser.
  6. Under Filtered by, choose Selected event > Parameter.
  7. Click Name and enter the parameter name (e.g. "eventAction").
  8. Click value and enter the value you want to filter by ("Facebook"). 

Here is the resulting metric tile:

You can also add additional segment criteria to your Filtered Metric. For example, you could create a metric to track an event parameter and also add a filter for Los Angeles users. This would create a metric that only tracks your parameter value for users in Los Angeles. Just click the + sign under Filtered by to add additional filter criteria to your metric.


Note: Once you create a Filtered Metric, you can use it to create a new Custom metric.


Filtered metrics allows you to create more refined metrics based on the parameters you append to events. Here are a few examples of filtered metrics:

  • An on demand ride service could filter their "Ride Completed" event by the parameter "Car Type," allowing them to create filtered metrics such as SUV Rides Completed, Compact Rides Completed and custom metrics such as SUV Rides per Total Rides, Compact Rides per Total Rides.
  • A game could filter their "Level Completed" event by the "Level Number" parameter, allowing them to create filtered metrics such as Level 3 Complete, Level 10 Complete and custom metrics such as Level 3 Completions per Total Level Completions, Level 10 Completions per Total Level Completions.
  • A furniture retail app could filter their "Search" event by the parameter "Item Category," allowing them to create filtered metrics such as Bed Search, Desk Search and custom metrics such as Bed Searches per Total Searches, Desk Searches per Total Searches.

Was this article helpful?
Have more questions? Submit a request