Introduction

LeadByte provides you with the ability to Dedupe against phone fields AND/OR email within a Campaign and other Campaigns (including Suppression Campaigns).

On the whole, this is the most common in the lead generation industry. However, in some instances you may need to run additional Dedupe checks. 

For example, you may be running a broadband (internet) Campaign that has an exclusive offer to each household, in which case phone and email dupe would not be enough but Phone + Last Name + Postcode + House Number may just do the trick. Luckily our Advanced Deduplication allows you to do just that!

Standard Deduplication

Standard Deduplication allows you to check for duplicate leads using the Phone fields or the Email field.

You can specify to only check against certain Suppliers or additional Campaigns using the options available. You can also set a timeframe which you reject leads as duplicates here. Note, when Deduping against a Suppression Campaign the timeframe is ignored, instead the check is indefinite.

Advanced Deduplication

Advanced Deduplication allows you to select additional fields within the Campaign you are editing to check against. You can choose from any fields set up in your Campaign, but you can also specify a timeframe to treat matching values as duplicates. Advanced deduplication will only reject as a duplicate if all the fields you have selected match an existing lead in the system at the same time. If Email/Phone1/Postcode are all selected, the all three fields on the lead must all be identical to another lead to reject as an advanced deduplication.

The cross-campaign deduplication allows you to perform the same advanced deduplication checks but against other campaigns.

We encourage you to run some tests when the process is complete by submitting API leads into your list.

Raise a support ticket if you have any questions.

FAQs

Q - Can I choose not to Dedupe against a Campaign?

A - Yes, we've added the option to allow you to Dedupe against other Campaigns BUT NOT the Campaign the lead is entering. Simply check the box and the rest is self-explanatory. 

Q - Is there a difference between using the REST API vs Standard API?

A - Our REST API is more robust and reduces the risks of duplicates slipping through the net. This is only really applicable when sending in leads in very quick succession, as leads using the REST API are queued to be thoroughly checked, whereas the standard API leads are checked against for duplicates and then written to the database. If a duplicate lead comes in BEFORE the original lead is written to the database, then this is when duplicates are allowed into your Campaign.

Q - I want to use Deduplication on a Delivery, can I do this?

A - You can! This article explains how - Deduplication on Delivery

Q - How about Deduplication across a Buyer?

A - You can! This article explains how - Deduplication on a Buyer