Routing Logic and Filters
Apply filters campaign wide or to specific buyers with just a few easy steps. This document will walk you through the simple set up to route leads to buyer's based on their specific criteria
To watch a tutorial on this topic click here
In this example we have 4 backend buyers, 2 buying off of ping post, an email delivery buyer, and one direct post buyer
Once your buyers are built out, scroll down to the Filters section of your campaign homepage
Global filters are campaign wide. Common global filters are filters for profanity, the word test, or things that you want to reject from all of your suppliers. For example, you might want to block any lead that does not pass jornaya or trustedform or anyone who is not a homeowner
To add a new filter, click the blue add button, then select a field to filter
Next you'll set your filter, for example blocking any emails with the word "test"
For our buyer specific filter example, let’s say Solar Company only wants leads in Florida, Texas, and California. Here you’ll add a filter with an Allow action and a Condition of matches exactly, then enter in the states the buyer has specified
For Solar Company 2, they only want to buy leads with a monthly electric bill over $150. Here add a filter for the monthly electric bill field and select allow as the action and one of as the condition. You’ll then add the values that fit the buyer's criteria
If you have more than just a few records, instead of entering them one by one you should upload a zip file. The editor on the left should only be used for a few records, no more than 1000. If the direct post buyer has a list of allowed zip codes greater than 1000 records, upload that file here to add them as a filter. If you upload a text file, each line is added as an entry - so make sure each value is on its own line. If they are in a spreadsheet all values need to be in one column with NO header to be properly imported
On top of simple filtering, LP can also execute regular expression filtering. When creating a filter on a text field, you can use the "contains" condition to create complex filters. For example, we can block all phones that start with area code 210 and 505 by using BLOCK, and putting ^210 and ^505 in the contains condition. Please be sure to read our docs for additional examples on how to use this feature. Reach out to support if you need help setting these advanced rules
Remember that every buyer can have their own set of filters, ensuring they only get leads that match exactly what they are looking for
Filters are Case-Insensitive
- The filtering system is case-insensitive. When parsing and executing filters for incoming requests, they will be evaluated as case insensitive.
- EX: if your input receives M, and your filter is defined as "m", the request will be valid.
Configuration:
- when adding a filters value, you may notice them in the saved filters list with a different character case - this is OK and working as intended.
- EX: you might add "M" and "F" as a gender filter, but in the list they will display as "m" or "f".
Filters on optional fields do not execute unless a value is received for that field. It's best to set those fields as required if filtering is needed on the field.
That’s all for routing logic and filters, if you have any questions please email us at support@leadprosper.io or make use of the support button