What are Routing Rules?
Routing rules are are sets of rule conditions that you can apply to an endpoint in order to customize your lead distribution.
Routing rules take data that's stored with the lead in Pingtree, and allows users to create restrictions or rules with them through the use of IF/THEN statements.
Example: Assume you had an offer built inside of Pingtree and in the form you were collecting the age of the lead.
Now assume that you have 2 different buyers set up as custom endpoints in your routing distribution logic, one buyer accepts leads up to the age of 35 and another buyer only accepts leads over the age of 35.
In order to segment each lead into the proper distribution flow and ensure that it's sent to the correct buyer, you would utilize routing rules.
Routing Rules can be found in your Distribution section.
Configuring a Routing Rule
Routing rules uses groups of IF/THEN statements in order to facilitate the conditional logic you want to apply.
Name:
The name doesn't impact any logic, it's only how you want the rule to show up in your routing logic.
Groups:
You may have multiple "Groups" within a single Routing Rule condition. The first "AND/OR" tab will determine if the conditions need to be met in all groups or if they just need to be met in one of the various groups that have been set.
IF/THEN Statement
"IF" (condition/parameter) --> "Operator" --> {VALUE} -> "THEN" {action to take if condition is true}
Field Parameter:
The parameter, which is the left hand selection, will populate data that's stored with a lead. This can be any system fields that are captured on the backend, such as the "pid" (partner ID - where the lead originated from), or it could be a custom field that's captured on your form or from an external source.
It serves as the foundation for the rule you create. Only the fields that are being stored will populate as an option in this dropdown.
Operator:
The operator is in middle part of the IF/THEN Statement in the application but in reality it sits on the end of the logic. It tells the system what would be considered a "true" value.
For the exception of the "Equal" and "Not Equal" (or = and !=), the value needs to be an integer for it to work appropriately.
Value:
The third box is extremely important as it represents the value(s) being used in the rule.
This will reference the value that you are storing in that particular field.
NOTE* Syntax matters. The structure of the value has to be EXACTLY the same as how you are storing it in Pingtree.
AND/OR in the Same Group
If you create multiple rules in a single group, you will need to determine if the logic states that All the values within that rule group need be true or if only one of them would need to be true.
This logic applies to rules in a single group where the previous AND/OR logic applies to each group as a whole.
Assigning an Endpoint
The last step to setting up a routing rule is to assign it to an appropriate endpoint (or endpoints as you can assign these conditions to more than one).
Any endpoint which is active and enabled and does NOT already have an existing routing rule assigned should populate in this dropdown.
If, for whatever reason you do not see them in there, you will want to ensure the endpoint is enabled and that they are not set in a separate routing logic such as Base Routing.