The Intersection activity allows you to keep only the elements common to the different inbound populations in the activity.
Context of use
The Intersection activity is generally used to carry out additional filtering on populations from inbound transitions.
- Drag and drop an Intersection activity into your workflow.
- Connect it to the other activities that come before it, such as queries.
- Select the activity, then open it using the button from the quick actions that appear.
- Select the Reconciliation type :
- Keys only : Default mode. The activity only keeps one element when elements from the different inbound transitions have the same key.
- All shared columns : The data is reconciled on the basis of columns in common with the inbound transitions. Therefore, you have to select the primary set that will serve as a basis for comparison. This option can be used if the inbound population targeting dimensions are different.
- A selection of columns : Select this option to define the list of columns on which the data reconciliation will be applied. You must first select the primary set (the one which contains the source data), then specify the fields to use for the join.
- Check the Use common additional data only box if you would like to keep only the additional data that is in all inbound transitions.
- If needed, manage the activity's Transitions to access the advanced options for the outbound population.
- Confirm the configuration of your activity and save your workflow.
The following example shows the intersection between two query activities. It is being used here to look into the Adobe Campaign database and retrieve profiles who are between 18 to 27 years old and profiles whose email address has been provided respectively.