Create a Marketing Cloud Engagement Activation Target

To publish segments and batch data model objects (DMO) to Marketing Cloud Engagement business units, create an activation target in Data 360.

Available in: All Editions supported by Data 360. See Data 360 edition availability.

User Permissions Needed
To create an activation target	One of these permission sets: Data Cloud Architect Data Cloud Activation Manager

User Permissions Needed

To create an activation target

One of these permission sets:

On the Activation Targets tab, click New.
Select Marketing Cloud Engagement, and click Next.
Enter a name and an optional description.
The name can’t be more than 128 characters, start with an underscore, be all numbers, or include these characters: @ %^ = < ' * + # $ / \\ ! ? ( ) { } [ ] , . \ \
1. Select the data space you want to associate your activation target with.
  Data spaces associated with each business unit (BU) based on the Data Streams setup, where each BU mapped to one or more data spaces are displayed. This means data from multiple MCE orgs (EIDs and BUs) can be combined within the same data space. A warning is shown to indicate the risk of records from different EIDs being merged into the same data space.
2. Click Next.
Select a Marketing Cloud Connection and include the required business units from the available list.
To add or remove business units to receive the published segments or DMOs, click the arrows between the two columns.
When an activation target has multiple BUs, the activation filters the contacts by the BUs. The segment activates as a Shared Data Extension (SDE) and not as a Data Extension (DE) to Engagement. If an activation target has multiple business units configured, modify the activation target configuration to include one business unit only.
Click Save.

Ensuring Integrity in Marketing Cloud Engagement Activation
When multiple Marketing Cloud Engagement (MCE) orgs (EIDs) are involved in an Activation, unintended data mixing can occur. This happens when subscriber keys from different EIDs are brought into the same data space and are later activated to a specific EID, which can cause data integrity issues.

Product Area