What does it do?
This job’s function is to identify if a lead has a duplicate value across selected fields, from a list of set values. Eg If the same value from the defined list is found within the configured fields this will be flagged as a duplicate.
Actions | Description | Acceptance Criteria | |
|---|---|---|---|
| 1 | fields | From the drop-down menu, you can select the fields you would like this check to run against. The user can add as many fields as they choose. | The user can add multiple field for the processr job to reference |
| 2 | values | From the drop-down menu, you can select yes or no | The user can add multiple values for the processr job to reference |
| 3 | case_sensitive | From the drop-down menu, you can select yes or no | The user can select yes or no, |
Who would use it?
Why would clients find this useful?
This helps prevents sending duplicate leads over a particular timeframe, for instance, if a lead was sent in Q1 the client may not want to receive the same lead in Q2
Key Talking points:
If the client wants to avoid duplicate leads over a set time period
It gives the customer the option to filter leads based on all customers or just one customer
Can determine if the lead is re-engaging after a set time period eg flag as a duplicate in Q1 but accept in Q2
An example of how it would be implemented?
If the user is running a campaign for the first 3 months (Jan-Mar) of the year, the advertiser will then say they do not want to receive the same lead within the next 3 months (Apr-Jun).