Follow

Filtering leads that get sent to a delivery destination

 

Filtering lets you control which leads will be sent to a delivery destination server. To set up filtering for a destination, click the gray funnel icon on the delivery destinations list for your campaign.

Filtering uses a list of rules to determine whether a lead should be sent to that destination. One or more of the rules must pass in order for the lead to be sent to the associated delivery destination. This is customizable; you can set the filter to send a lead through if only one of the rules passes, or if all of the rules pass.

In the event that none of the rules pass, then the lead is blocked — delivery to that destination will be considered failed, and the lead will not be sent to the destination. When a lead is blocked, you can see why in the delivery summary section of the lead details.

If you'd rather treat a blocked lead as a delivery success (or a delivery error) in order to control multi-destination lead delivery behavior, you can do that too.

Filtering can significantly alter lead status. It is important to test and watch newly setup filters to make sure the delivery behavior is correct and the leads are flowing as expected through the filter.

Note that filtering is not available on "Custom HTTP POST" destinations, which are usually used for SOAP and XML deliveries.

Rules

Rules consist of a number of conditions. A condition tests the value of a field. You might, for example, have a condition that says email_address must end with "hotmail.com".

A rule with multiple conditions can be set to require "all" of the conditions to pass. This setting is logically equivalent to putting the word "and" between each condition — email ends with "hotmail.com" and phone begins with "512" .

Alternatively, a rule can be setup to pass in the event that "any" of the conditions pass. This setting is logically equivalent to putting the word "or" between each condition — email ends with "hotmail.com" or phone begins with "512".

Operators

Each condition has three parts: the field being examined, the comparison operator, and the value being compared to the field. There are a number of different operators available, and each does a different kind of comparison:

  • is equal to — the field value must be the same as the specified value
  • blank — the field value must not be present or must be empty
  • begins with — the first characters of the field value must be equal to the specified value
  • ends with — the last characters of the field value must be equal to the specified value
  • contains — the field value must contain the specified value (i.e. "hot dog" contains "dog")
  • is included in — the field value must be found within the specified comma delimited list of values (up to 200 values)
  • is greater than — a numeric field value is expected; the field value must be more than the specified numeric value
  • is greater than or equal to — a numeric field value is expected; the field value must be equal to or more than the specified numeric value
  • is less than — a numeric field value is expected; the field value must be less than the specified numeric value
  • is less than or equal to — a numeric field value is expected; the field value must be less than or the equal to the specified numeric value
  • matches pattern — the field value matches the specified regular expression value

All operators are available in the negative: is not equal to, is not blank, etc.

Fields

Your filter rules operate on the parameters that are set up for the associated delivery destination — one field per parameter. For that reason, you may notice different fields in the filter editor than you have set up in your campaign.

Keep in mind that your rules operate on the values that are being passed to the associated delivery destination, not necessarily the exact values that were collected in the lead data. So, if you're combining multiple fields into the same parameter, your condition should be written with that in mind. For example, if you have your destination parameters set to phone=#{area}#{exchange}#{line}, then your condition should say phone begins with "512789"area, exchange, and line won't be available as filter fields even though they are campaign fields. If you are doing variable translations on the associated delivery, those will also be applied to field values for the purposes of filtering.

If you add a new parameter to your delivery destination, it will be available as a new filter field. Removing a parameter from your delivery destination will mean that it is no longer available during filter evaluation. Consequently, you should remove filter rules that refer to the parameter prior to removing it from the delivery destination. Failure to do so will mean that rules may pass or fail in a way that's inconsistent with your intentions.

Effect on multi-destination deliveries

Each destination in a campaign's delivery can be configured to either continue or halt further delivery processing, depending on that destination's success, failure or error (see Lead Delivery Overview). The filter can be configured to treat delivery as a success, failure, or error, when the filter blocks a lead. The results of filter evaluation can be similarly used to control delivery processing.

For example, assume you have the destination set to stop further processing ("do not continue to next destination") when a failure occurs, and the filter set to treat a blocked lead as a failure. In the event that the filter blocks the lead or the destination server responds with a failure, the delivery process will be stopped. This configuration is set on each destination.

Filtering Mode

The behavior of your filter can be modified by changing its mode of operation using the drop-down in the bottom left corner of the filter editor.

  • Block unless at least one rule passes — this is the default mode; evaluate the filter rules, and if one of the rules passes, then allow the lead through the filter to the destination server
  • Block unless all rules pass — evaluate the filter rules, and if every rule passes, then allow the lead through the filter to the destination server.
  • Never block, no matter what — short circuit all your configured rules so that leads always pass through the filter; leads will always be sent to the destination; use the "Stop Filtering" button if you intend to leave the filter in this mode for an extended period
  • Always block, no matter what — short circuit all your configured rules so that leads never pass through the filter; leads will never be sent to the destination

Disabling or Removing

You can disable your filter at any time by clicking the "Stop Filtering" button. This is the logical equivalent to the "Never block, no matter what" filter mode. Leads will not be sent through the filter, but rather will be immediately sent to the destination.

To permanently remove your filter and all its rules, click the "Remove Filter" button. If you decide you want to use filtering for this destination again, you will need to set your rules up from scratch. Once you remove the filter, leads will always pass to the destination.

Example Use Case: How do I prevent leads from a particular source from going to a particular delivery destination?

First you need to make sure that you are passing a source value to the delivery destination. You can only create a filter rule by using a field that is actually passed to the delivery destination. It doesn't matter if the recipient server actually captures this value. It just needs to be in the delivery destination for creating the rule. For example, you could add source=#{xxLeadSourceId} to the delivery destination.

The next step is to lookup the ID that represents the source you want to block. Go to your Sources tab to find a list of Seller Accounts. The ID representing each account is listed in the first column. For the sake of this example, lets assume the ID is 123XYZ.

Now create a filter rule for the appropriate destination. The rule will contain a condition that says "source is not equal to 123XYZ". Now this destination will no longer receive leads from that particular source.

We have a brief screencast walkthrough of a filter setup at: LeadConduit Classic Destination Filters Screencast

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

Comments

You must be logged in to comment.