Playbook & Explore filters are identical.
The exact same conditions are available in your playbook’s audience settings and under the explore views.
This article applies to both features.
Playbooks: While in your playbook settings, navigate to the Audience section.
Explore: Open a new Person or Account level view.
Account vs Person: what are you looking at?
All Accounts includes all the accounts (companies) in your CRM, allowing you to manage and track these accounts effectively.
All Persons encompasses all leads, contacts, and people from systems connected to MadKudu that are associated with the accounts from All Accounts
What are the filters available?
Filters are based on:
Event Mapping: specific actions taken by a user that are tracked and recorded in your integrations, and were mapped in the Event Mapping.
Computations: In the context of MadKudu, a computation can be a firmographic, demographic or technographic Enrichment trait used in Fit models or segmentations (e.g. industry, company_size, tag_is_b2b, has_dbms_tech, is_hiring...) to identify if a Person or Company is a good fit for you, and to Segment and prioritize your Leads, Contacts and Accounts.
There are many computations you can use:~200 standard computations available out of the box by MadKudu.
Mapped Fields Computations based on fields from your CRM.
Combined computations, allow you to maximize the coverage of a data point that you have in your own CRM and that is also provided by MadKudu.
Here are some of the most common filters:
Filter | Description |
---|---|
Person activity event | Any person which is correlated with a certain event. Examples: visited the demo page, downloaded specific content, performed an action, etc. Correspond to more granular signals. |
Person activity global event | Any person which is commonly correlated with a group of events, correspond to the granularity you are actually scoring on. Examples: website visits, downloaded content, performed set of actions, etc. |
Account activity event | Any account which is correlated with a certain event. Examples: persons linked to an account that visited the demo page, downloaded specific content, performed an action. Correspond to more granular signals. |
Account activity global event | Any account which is commonly correlated with a group of events, correspond to the granularity you are actually scoring on. Examples: website visits, downloaded content, performed set of actions, etc). |
Person customer fit | Filter by the customer fit segment associated with persons. Examples: Very good, good |
Account customer fit | Filter by the customer fit segment associated with accounts. Examples: Very good, good |
FAQ
What's the difference between person activity event
and person activity global event
in copilot?
person activity global event
→ Correspond to the granularity you are actually scoring on.
That is, each individual event in the column “Mk event name” in your event mapping or the list of events under the Event Weights tab in your Likelihood to buy model.
person activity event
→ Correspond to more granular signals linked to these scored events.
This is the exact same naming that you see under the person’s activities tab in Copilot. It can be configured in colmun “Mk event name (signals) ” in your event mapping.
Troubleshooting
My event filter doesn’t filter out people I’d like to see filtered
If you use a rule like “Activity Event does not contain…”, the result will be every person/account that has at least one event that does not fit contain that activity.
What you should use is “Number of person/company activities = 0 + Person/Account activity event”
My event filter doesn’t yield any result
It might be that the value is not 1 to 1 with the event mapping.
Try to use the exact naming format used in event mapping and copy paste it to avoid errors.
If that doesn’t work, review conflicting rules.