Routing Rules
Routing Rules let you precisely control which endpoints (buyers) receive each lead. By defining IF/THEN logic around lead metadata, you decide when and why a lead should (or should not) be sent to a given endpoint.Rule Components
Name
A human-readable label for your rule. It doesn’t affect logic—it’s how you’ll identify it.Groups
Groups combine multiple sets of conditions. Use the top-levelAND/OR
to specify whether all groups must match (AND
) or any group match suffices (OR
).
Conditions (IF/THEN)
Within each group, define one or more IF/THEN statements:Building a Condition
-
Field Parameter
The lead attribute you’re testing (e.g.,
partner_id
,state
, or any custom field). Only captured fields appear in this dropdown. -
Operator
Specifies the comparison method:
=
(Equal)!=
(Not Equal)>
,<
,>=
,<=
(Numeric comparisons; value must be an integer)IN
,NOT IN
(List membership)
- Value The exact string or number stored in Pingtree. Case-sensitive; must exactly match the stored data.
Logical Combinations
-
Within a Group
Choose if all conditions must be true (
AND
) or if any one suffices (OR
). -
Across Groups
The top-level
AND/OR
determines if every group must match (AND
) or if any single group match suffices (OR
).
Assigning Endpoints
- Select one or more enabled endpoints.
- Only endpoints without existing routing rules will appear.
- If an endpoint is missing, ensure it’s enabled and not already assigned to another routing logic.