Set up duplicate checking
Stop the same person being sold twice, by choosing which fields to match on, how far back to look, and whether the rule applies per campaign or per buyer.
This article shows how to configure the Dupe Checker so the same consumer is not sold twice inside your lookback window. Duplicates are the fastest way to lose a buyer relationship, and the fastest way to block good traffic if you set the rule too wide.
What it does
When a lead arrives, Datahubb looks back a number of days you choose and compares the fields you nominate against leads already in the campaign. If it finds a match, the incoming lead is rejected and labelled a duplicate.
The check runs during ingest, after filters and before the lead is offered to any buyer.
Prerequisites
- A campaign with its fields already defined
- A view on how long a lead stays "the same person" in your vertical, usually 30 days
Configure the Dupe Checker
- Go to Campaigns and open the campaign.
- Open the Filters tab and find the Dupechecker Settings section.
- Enable the feature.
- Set Number of Days. This is how far back the check looks.
- Set Dupe Check Fields. These are the campaign fields to compare, most commonly phone and email.
- Set Dupe Check Scope.
- Set Matching Field.
- Click Save.
- Send the same test lead twice and confirm the second one is rejected as a duplicate.
Scope
| Scope | What it means |
|---|---|
| Campaign Level | Match against every lead in the campaign, whoever bought it. Prevents selling the same person to anyone twice. |
| Buyer Level | Match only against leads sold to the same buyer. The same person can still go to a different buyer. |
Campaign Level is the stricter, more common choice. Buyer Level suits a program where several buyers legitimately want the same consumer.
Matching
| Matching Field | What it means |
|---|---|
| ONE FIELD | Any single nominated field matching is enough to call it a duplicate |
| ALL FIELDS | Every nominated field must match the same earlier lead |
One Field is the aggressive setting. With phone and email nominated, a person who reuses either one is caught. All Fields is the conservative setting, and it lets a consumer through if they changed any one of the values.
Choosing fields and a window
Phone and email together is the standard combination for person-level deduplication. Add an IP address only when you actually want to block a household or an office, not a person.
Thirty days is the usual lookback. A longer window catches more repeats and blocks more legitimate re-inquiries. Match it to how long your buyers consider a lead worked.
Expected result
Sending the same lead twice inside the window produces one accepted lead and one rejected as a duplicate. The rejected lead's timeline names the duplicate check as the cause, and the same cause appears grouped on Rejection Reasons.
Troubleshooting
- Too many duplicates. The window is too long or the matching is too loose. Shorten the window, or switch from One Field to All Fields.
- Duplicates getting through. The wrong fields are nominated, or the window is too short. Add phone and email, and lengthen the window.
- A phone duplicate is not matching. The two leads carry the number in different formats. Check what your suppliers actually send.
- The same person reaches two buyers and you did not want that. The scope is Buyer Level. Switch it to Campaign Level.
- A buyer says it received a duplicate anyway. The duplicate check compares leads inside this campaign. A consumer who filled in two different campaigns produces two separate leads.
Frequently asked questions
Comments
No comments yet — be the first to share your thoughts.