Use Duplicate Rules (a.k.a. "dup rules") to prevent posting a duplicate lead to a Lead Point to shorten overall ping tree response times and to not bother your buyers unnecessarily.
Use Exclusivity Rules to honor exclusivity agreements.
Duplicate and Exclusivity Rules are attached to Lead Points. When a posted lead matches an attached rule and its history then the lead will not be posted. Otherwise if it is posted then afterwards a new duplicate entry may be created depending on the outcome of the post combined with the Set Event that has been configured for the rule.
Important: Like most other configuration items in the system the mere act of defining a Duplicate/Exclusivity Rule doesn't put it into effect anywhere. You have to attach it to the Lead Points where you wish for it to be enforced. Being explicit about when to apply a Duplicate/Exclusivity Rule provides the flexibility to allow a Lead Point to be excluded from a given Duplicate/Exclusivity Rule.
Also Important: There is no overlap when multiple Duplicate/Exclusivity Rules have the same Pattern definition. For example, say you have one Exclusivity Rule called "Payday Exclusive - Email (15d)" based solely on an email address that you attach to lead points in a payday ping tree. Say you also have an Exclusivity Rule called "Debt Exclusive - Email (15d)" also based solely on an email address. If you sell "email@example.com" through a lead point that uses the "Payday Exclusive - Email (15d)" rule then it has no affect on any other lead point unless that lead point also has "Payday Exclusive - Email (15d)" attached to it. Lead points with "Debt Exclusive - Email (15d)" attached to it have their own set of email addresses and are therefore free to receive posts of "firstname.lastname@example.org".
||A unique duplicate rule name up to 255 characters.
||You may keep a duplicate entry for up to 60 days.
Never - Use this to only check for existing entries but not contribute new entries. Only makes sense for an Exclusivity Rule since all Duplicate Rules involve a Lead Point Internal ID in the Pattern definition.
On Accept - Set a new entry if you get an Accept from any Lead Point that uses this rule.
On Any Response - Set a new entry if you get an Any Valid Response from any Lead Point that uses this rule. This does not include time outs, network connectivity errors, e.g. It only includes application level responses from the other end.
On Decline - Set a new entry if you get an overall Decline disposition from any Lead Point that uses this rule.
On Post - Set a new entry if you do a Post to any Lead Point that uses this rule even if a time out occurs waiting for a response.
||You can't delete a rule once you create it but you can change its definition and you can also hide it so that it does not appear in drop down lists, e.g.
||Anything goes here.
||Build up a list of one or more Fields, System Parameters, etc. to indicate what defines a duplicate lead.
A Duplicate Rule
In this example we wish to prevent unnecessarily posting a duplicate lead to a given Lead Point to speed up response time and reduce buyer quality complaints.
We set the duration to 3 hours and the Set Event to "On Post". For the "pattern" we use Ping Tree ID, Lead Point Internal ID (critical!), Social Security Number, and Last Name. We did not have to include Ping Tree ID; this was a choice. Typically it is sufficient to just pick Lead Point Internal ID plus one or more Fields.
Now if the same Ping Tree and Lead Point combination encounters the same SSN and Last Name combination within 3 hours and the lead point has this rule attached to it then it will be prevented from receiving a post.
This rule could be simplified to not include Ping Tree ID. Whether to do so depends on what you want to achieve. Do you want this Lead Point to not see "Smith/123-45-6789" again for a 3-hour period for all of your Ping Trees or just this very same one?
An Exclusivity Rule - Maximum Number of Times a Lead Can Be Sold = 1
In this example we wish to honor a business rule to not sell a lead a second time out of the same Ping Tree for a period of 5 days.
We set the duration to 5 days and the Set Event to "On Accept". For the "pattern" we use Ping Tree ID, Social Security Number, and Last Name. Again, including Ping Tree ID is a choice and is not necessary. It is perfectly valid to only involve Social Security Number and Last Name for this example if you wish for the rule to apply no matter in which ping trees the lead point is included. What makes this an Exclusivity Rule versus a Duplicate Rule is the lack of Lead Point ID in the Pattern definition and the Set Event of On Accept.
Now if the same Ping Tree encounters the same SSN and Last Name combination within 5 days then any Lead Point that has this rule attached to it will be prevented from receiving a post. Any Lead Point that does not have this rule attached to it however will receive the post; for example you may wish for a list management Lead Point or a Lead Point for an insert/update into your own back office Customer Relationship Management (CRM) or other such database to receive the post regardless.
An Exclusivity Rule - Maximum Number of Times a Lead Can Be Sold > 1
Honoring this business rule in the system today requires a bit of a hack. What you have to do is define an Interface that doesn't do anything -- it doesn't post and therefore it doesn't get a response. In technical terminology this is called a "No Operation" or "no-op".
Next create a Lead Point that uses this "no-op" Interface. It can hang under any Lead Buyer that you like. Most customers create a Lead Buyer with their own company name for this kind of Lead Point.
Next create an exclusivity rule like the one from the previous example and attach it to this new Lead Point as well as to every other Lead Point involved in the exclusivity agreement.
Next create a Filter for a Lead Point that requires the total number of accepts to be greater than one. Attach this Filter to the new Lead Point.
Finally create a final tier in your Ping Tree to hold this new Lead Point. Now if one or more leads is sold when this Ping Tree completes then an entry will be made in the duplicate/exclusivity history to prevent additional matching leads from being sold during the configured time period.
We understand that this is cumbersome. We have a pending work ticket to make it easier to configure exclusivity rules so that you can define an exclusivity rule with a count and so that this "no-op" Lead Point hack is not required. Once we deploy this work then the condition for a duplicate/exclusivity history match becomes a check against the count of matching entries within the configured time period instead of a mere exists-or-not type of check.