- When a lead arrives. Global and source-level checks compare the new lead with leads you’ve already received. A match marks the lead as a duplicate and rejects it.
- When a lead is about to be delivered. Customer and partner checks compare it with what that particular buyer has already received. A match skips that buyer, and the lead moves on to the next one.
Global duplicate checks
Global duplicate checks apply to all leads coming in from any source.

For example, a check on email with a 30-day window flags any lead whose email matches a lead from the last 30 days. Add phone to the same check and the Field matching setting decides the rest. With All selected fields must match, only leads matching both email and phone are flagged. With Any selected field can match, either one is enough.
Included statuses
By default, every status counts except Duplicate and Unassigned. That means a lead nobody bought doesn’t block a fresh copy of itself, so a second chance at a sale isn’t lost. Club leads are split into Club (unclaimed) and Club (claimed), and a Club lead counts as claimed once it’s been delivered to anyone. Unselected statuses are ignored. If you clear every status, the check won’t reject anything. The table shows each check’s fields (with “All fields must match” or “Any field must match”), Duration, and whether it Applies to pings, is Case sensitive, and Ignores punctuation. Use the row actions to edit or delete a check.Source-level duplicate checks
You can also configure duplicate checks on a source’s Duplicate Checks tab (see Sources). They have the same settings as global checks, but only apply to leads coming through that specific source, giving you more granular control.

Apply to pings
Global and source-level checks can also apply to pings. When enabled, a ping that matches returns a duplicate response, so you can reject a lead before it’s even posted. See ping-post.Matching options
Every kind of duplicate check supports these matching options.Customer duplicate checks
A lead that’s new to you might not be new to a customer, who may have bought the same person from you last month. Customer duplicate checks compare each delivery against that customer’s own delivery history, so you don’t sell a customer someone they already have.

The customer’s history includes returned deliveries and Club claims, but ignores pending reservations. Save with the floating save bar.
Marketplace and Club eligibility
When a lead skips a customer because they already have it, you decide whether it can still be listed on the marketplace or in the Club, where that customer could see it again.- Eligible immediately lists it as usual.
- Never eligible for this routing attempt means the Marketplace or Club stage passes on this lead.
- Eligible after a number of days lists it only if the customer’s earlier delivery was at least that many days before this lead arrived. The number can’t exceed the history window.
Partner duplicate checks
Partners get the same kind of check against their own delivery history. The Partner duplicate-check default tab has the same settings as the customer tab and sets the default every partner can inherit.


