...
This is a processor job that will check to find if the email address submitted is unique to the campaign.
This is a predominately used in the B2C environment as it is more of a low value-based consumer goods.
Action | Description | Acceptance Criteria | |
|---|---|---|---|
| 1 | Set the Duplicate Status | Set the status of when the duplication will run the user has the option to select Valid, Billable or All. | Depending on the status of when the duplcation job is set this can produce 3 different results. If set to valid this check will only flag if the lead is valid or billable If set to Billable this check will flag only flag on billable leads If set to All this will flag on Valid, Caution, Invalid and Billable |
Who would use it?
Publisher, Agency & Clients users
...
An example of how it would be implemented?
User Users will be able to add this Processor job to a Campaign via Processor.
...
In order to configure configure this job Users can select Duplicate_status of either Billable, Valid or All. This will then filter any Duplicate emial email with the corresponding Duplicate status.
Users can edit the label associated associated with the Duplicate Duplicate email job for their own reference.
...
Users can 'Enable' or 'Disable' the job using the toggle. Users can also toggle on/off the 'Hardfail' functionality for the job.
Example config:
...
The core functionallity functionality of this job can be described described as follows: If a lead with an email eg adam.carter@convertermediacarter@converter.net comes io comes into a campaign the second instance of a lead with this email will be flagged as a duplicate.
Once flagged the platform then passes this information back on to the publisher.
...
Duplicate email Import settings:
Users can import settings into a campaign if the duplicate email check has been added via the processr section
...
Upon successful import of confirmation confirmation, the user should see a snack bar notification confirming the change.
...
Import via JSON:
Alternatively users can import settings via JSON. It is important to note that importing with JSON will remove previously configured settings for the job.
