Using the New Dashboard Filters
Last updated
Last updated
Previously, the dashboard filters were limited to filtering by company or user properties. With the launch of Filters V2, you can now filter dashboards at the most granular level.
HockeyStack's new dashboard filters enable you to filter entire dashboards by fields of your choice. This is useful when you want to take a look at your marketing efforts from a particular angle, for example by filtering a set of reports by deal type (new vs. existing business) or company size (by number of employees or market segment).
Additionally, you can filter different objects in a dashboard by different fields at the same time. A common scenario is one where you want to filter a table that presents Leads, MQLs, and Closed Won deals by Region, but there are separate fields that define Region on lead and deal objects. The region on the lead object may be Lead_Region__c, while the region on the opportunity object may be Opp_Region__c. You can now create a Defined Property that combines these two fields into a single filter.
First, enable new filters in Settings, under the “Reporting & Tracking” section. It will convert all dashboard filter buttons to Filters V2 buttons.
Then, you need to build Properties, which you will later use for filtering. Go to Definitions → Properties, and create mappings, using the fields of your choice (you'll find them in Action Properties section of a dropdown), and mapping them either to specific values of your choice or simply back to the Property value.
You also need to define actions on which object your mapping covers. So, define: Action Name contains [name of the object]. You’ll find Action Name under Action Properties. Thanks to this, you'll only cover objects of your choice in the definition.
In the Advanced Options of your Property, toggle Include in Filters. If you don’t manually turn this on, it won’t be displayed in the filter options.
For dashboard filters to work properly, you need to understand their nature, otherwise they may trick you.
As they are global, and they filter all actions in entire dashboards, if we only define them as above, they would filter out all of the actions for which the field listed in the definition is empty. Sounds like what we want, right? Well, not entirely! Your dashboards contain lots of actions that are not happening on these defined objects, and you still want them displayed. Example? All the marketing touchpoints: website data, LinkedIn integration, etc. Since we don't want to lose these actions from dashboards, filters don't hide actions for which the selected field is empty. (Example below)
But this comes at a price: for example, if your "Deal_type" field only takes on the value "New Business" for new business and is empty for every other deal - without covering nulls in the definition, the empty values wouldn't get filtered out.
deal property changed
<some date>
hockeystack.com
new business
website visit
<some date>
person@hockeystack.com
(empty)
deal property changed
<some date>
hockeystack.com
(empty)
The solution is simple: include empty values on the object actions coming from your CRM in your definition, mapping all of them to "-". For example:
action_name contains deal AND Opp_Region__c is not empty → map to Opp_Region__c
action_name contains lead AND Lead_Region__c is not empty → map to Lead_Region__c
action name contains deal,lead,contact,company → map to "-”
The last mapping will add a value "-" to the list of regions, enabling filtering it out. This way, anything that is based on a CRM object will either be filtered to its region or will not be shown. But all other data points, such as website data, or ad platform data will be properly displayed in your dashboards.
Properties are executed from top to bottom. So place your detailed definitions on top, and the general ones on the bottom. Always include the definition for "-" value at the bottom of all the mappings.
Action names don't reflect object names 1:1. Action names for the most popular CRM objects will be: deal, lead, contact, campaign subscription, company.
