LeadConduit: Filters

« Previously: Rules

LeadConduit filters are powerful, flexible, and critical to getting the most value out of the platform. To successfully configure a filter, keep a few simple principles in mind.

Filters have only one function: If a filter's rule conditions are met, it stops the flow. In the process, it also sets the status of the lead and sends a reply message to the Source.

Filters are case-insensitive: To a filter, "TEST" == "test" == "Test".

There's more than one way to skin a cat. You can filter out red leads by setting a filter to look for is red, or you can accomplish the same thing by setting the filter to look for is not green, blue, white or black. The shortest is often, but not always, the most efficient, so think flexibly.

Layers and rule sets are your friend. LeadConduit filters allow you to create one layer of child sub-rules that also must evaluate as true for the parent rule to evaluate as true. You also can create rule sets composed of multiple parent-level or child-level rules. Initiate a rule set by clicking a rule's Convert this rule into a rule set button, then adding additional rules to the set. Each rule set is evaluated separately as a group, and the outcome of the set is treated as if it were the outcome of a single rule.

These options create a lot of flexibility. Let's look at an example. Say you want to accept leads only from females aged 40 to 65. That means that, from the filter's point of view, you want to reject leads from all males, and reject leads from females who are not between 40 and 65. You could set up one filter to reject leads from males, a second filter to reject females over 65, and a third filter to reject females under 40, like so:

Effective, but very clunky. Using a second-level rule set we can do the entire gender/age evaluation in a single filter. Note the use of any and all in the configuration:


Note that the top level rules evaluate only gender (one rule for male and one for female) and reject the lead if either the lead is of either gender, but the female rule contains a second-level rule set that tests age, so the female gender rule is only true if the age is less than 40 or greater than 65.

Finally, let's allow for the possibility of a DOB date that's in the future, and the possibility that the gender is submitted as other (both are legitimate options for those fields in LeadConduit). In the process we can refactor the entire filter configuration for maximum efficiency using a top-level rule set for the age component:


Next: Advanced Field Mapping »



Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


You must be logged in to comment.