- Campaign Standard documentation
- Latest Updates
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Get started with communication channels
- About communication channels
- Delivery best practices
- Email messages
- SMS messages
- Push notifications
- In-App messaging
- Direct mail
- Transactional messaging
- Landing pages
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- Get started with Campaign integrations
- Campaign and Experience Manager
- Campaign and Target
- Campaign and Analytics
- Campaign and Audience Manager or People core service
- Campaign and Analytics for Mobile
- Campaign and Triggers
- Campaign and Microsoft Dynamics 365
- Campaign and Adobe Experience Platform
- Managing processes and data
- Get started with data and processes management
- Workflow general operation
- Executing a workflow
- Calling a workflow with external parameters
- Targeting activities
- Execution activities
- Channel activities
- Data management activities
- Filtering data
- Importing and exporting data
- Use cases
- About workflow use cases
- Deliveries
- Creating deliveries with a complement
- Creating deliveries on profiles’ creation date
- Creating a weekly delivery
- Creating a cross-channel delivery
- Identifying duplicates before a delivery
- Birthday delivery
- Coupling email and direct mail deliveries
- Sending an email with enriched fields
- Personalizing an email with additional data
- Sending a recurring push notification
- Segmentation and targeting
- Data management
- Reconcile a File audience with the database
- Deduplicating the data from an imported file
- Enriching profile data with data contained in a file
- External signal activity and data import
- Updating the database with external data
- Updating data based on an automatic file download
- Data reconciliation using relations
- Data update using reconciliation
- Exporting profiles in an external file
- Updating multiple subscription statuses from a file
- Subscribing profiles from a file to a specific service
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- Audit Trail
- Configuration guidelines
- Users and security
- Configuring channels
- Configuring mobile channels
- Implementing Push tracking
- Adding images and videos iOS
- Understanding push notifications payload structure
- Implementing local notification tracking
- Tags in Adobe Experience Platform synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring tag rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- How to migrate your mobile application from SDK v4 to Adobe Experience Platform SDK
- Configuring SMS channel
- Application settings
- Working with APIs
- Get started with Campaign Standard APIs
- About Campaign Standard APIs
- Global concepts
- Interacting with custom resources
- Managing profiles
- Managing services and subscriptions
- Interacting with marketing history
- Privacy management
- Managing transactional messages
- Managing workflows
- Managing organizational units
- Managing geographical units
- Troubleshooting
- Campaign Control Panel
Union
Description
The Union activity allows you to regroup the result of multiple activities into a single target.
The sets do not necessarily need to be homogeneous.
Context of use
The Union activity is used to combine the populations from inbound transitions when performing a segmentation, defining an audience, or when preparing the message target for example.
Related topics:
Configuration
-
Drag and drop a Union 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 to define how duplicates are from the confrontation between inbound populations are handled:
- Keys only: this is the default mode. The activity only keeps one element when elements from the different inbound transitions have the same key. This option can only be used if the inbound populations are homogeneous.
- All shared columns: The data is reconciled on the basis of all the columns in common with the inbound transitions. Therefore, you have to select the primary set that will be kept in case of a duplicate. 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 (that which contains the source data), then the columns 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 you would like to limit the size of the final population, check the Limit size of generated population box. The size can be specified in the Maximum number of records field.
-
If needed, manage the activity’s Transitions to access the advanced options for the calculated population.
-
Confirm the configuration of your activity and save your workflow.
Example
The following example shows the result of two query activities that aim to regroup profiles from the Adobe Campaign database who are between 18 and 27 years old and those who are between 34 and 40 years old. The result contains all the profiles of the two queries or the maximum number of records, if applicable, as specified during the configuration.
Resources
Adobe Account
