Overview
The Enterprise Duplicate Email Check job runs to find if the email address submitted has been received on any other campaigns across the entire enterprise.
This job is quite versatile, as there are a number of ways in which it can be configured based on the end results that you would like to achieve.
Configuration
Please see below the options available to ensure the job runs according to your specifications:
- same_advertiser: Enter yes/no depending on whether the job will run across the same Advertiser.
- same_publisher: Enter yes/no depending on whether the job will run across the same Publisher.
- advertiser_billable:Enter yes/no depending on whether the job will check only for leads that are already billable for the Advertiser.
- publisher_billable: Enter yes/no depending on whether the job will check only for leads that are already billable for the Publisher.
- date_from:Enter the date from when the job will check for duplicate leads.
- date_to:Enter the end boundary from when the job will check for duplicate leads.
- past_x_days:Enter the amount of days the lead can be present in the platform before it is excluded from being a duplicate.
- campaigns: Enter and map the campaigns the job will check.
Note: None of the above options are mandatory - it is completely up to you on which filters you would like to utilise.
Use Case
This job is often used to flag duplicate leads that re-appear in Q2 for campaigns under the same advertiser. This information is vital for the client, as it shows re-engagement from a lead which makes that lead more valuable to them.
The set up for this use case would be as follows (assuming that Q2 runs from April 1st - June 30th):
The above setup means that between that date range, leads will be flagged if they have appeared on that enterprise previously in campaigns under the same advertiser.
If you would like to immediately invalidate these leads, ensure that you have enabled the hardfail option when you add this job. Otherwise this lead will be flagged as a caution lead.