Deduplication deletes duplicates from the results of inbound activities. Deduplication can be performed on the email address, telephone number, or another field.
During deduplication, inbound flows are processed separately. If for instance recipient A is found in the result of query 1 as well as in the result of query 2, they will not be deduplicated.
This issue needs to be addressed as follows:
- Create a Union activity to unify each inbound flow.
- Create a Deduplication activity after the Union activity.
To configure a deduplication, enter its label, the method, and the deduplication criteria, and the options concerning the result.
Click the Edit configuration... link to define the deduplication mode.
- Target selectionSelect the type of target for this activity (by default, deduplication concerns recipients) and the criterion to be used, i.e. the field for which identical values enable you to identify duplicates: email address, mobile or telephone number, fax number or direct mail address.In the next step, the Other option lets you select the criterion or criteria to be used:
- Deduplication methodsFrom the drop-down list, select the deduplication method to be used, and enter the number of duplicates to be kept.The following methods are available:
Click Finish to approve the selected deduplication method.The middle section of the window summarizes the defined configuration.In the lower section of the activity editor window, you can modify the label for the outbound transition of the graphical object and enter a segment code that will be associated with the result of the activity. This code can later be used as a targeting criterion.Check the Generate complement option if you wish to exploit the remaining population. The complement consists of all the duplicates. An additional transition will then be added to the activity, as follows:
- Choose for me : randomly selects the record to be kept out of the duplicates.
- Following a list of values : lets you define a value priority for one or more fields. To define the values, select a field or create an expression, then add the value(s) into the appropriate table. To define a new field, click the Add button located above the list of values.
- Non-empty value : this lets you keep records for which the value of the selected expression is not empty as a priority.
- Using an expression : lets you keep records with the lowest (or highest) value of the given expression.
Example: Identify the duplicates before a delivery
In the following example, the deduplication concerns the union of three queries.
The aim of the workflow is to define the target for a delivery by excluding duplicates to avoid sending it to the same recipient several times.
The identified duplicates will also be integrated into a dedicated duplicates list that can be reused if necessary.
- Add and link the various activities required for the workflow to operate as shown above.The union activity is used here to "unify" the three queries into one single transition. Thus, deduplication will not work for each query individually but for the whole of the query. For more on this subject, refer to Best practices .
- Open the deduplication activity then click the Edit configuration... link to define the deduplication mode.
- In the new window, select Database schema .
- Select Recipients as targeting and filtering dimensions.
- Select the ID field for the Email duplicates, to send the delivery only once to every email address, then click Next .If you wish to base the duplicate IDs on a specific field, select Other to access the list of available fields.
- Choose to keep only one entry when the same email address is identified for multiple recipients.
- Select the Choose for me deduplication mode so that the records saved in case of identified duplicates are randomly chosen, then click Finish .
When running the workflow, all recipients identified as duplicates are excluded from the result (and therefore the delivery) and added to the duplicates list. This list may be used again rather than having to re-identify the duplicates.
Each inbound event must specify a target defined by these parameters.
This set of three values identifies the target resulting from the deduplication. tableName is the name of the table which saves target identifiers, schema is the schema of the population (usually nms:recipient) and recCount is the number of elements in the table.
The transition associated with the complement has the same parameters.