This integration works with Adobe Campaign version 8.4 or higher.
Adobe Campaign Managed Cloud Services provides a platform for designing cross-channel customer experiences and an environment for visual campaign orchestration, real-time interaction management and cross channel execution. Get Started with Campaign
Use Campaign to:
Keep in mind the following guardrails when using the Adobe Campaign Managed Cloud Services connection:
To help you better understand how and when you should use the Adobe Campaign Manage Service destination, here is a sample use case that Adobe Experience Platform customers can solve by using this destination.
Adobe Experience Platform creates a customer profile that incorporates information like the identity graph, behavioral data from analytics, merges offline and online data etc. With this integration, you can augment the segmentation capabilities that are already existing within Adobe Campaign with those Adobe Experience Platform powered audiences, and you can hence activate that data in Campaign.
For example, a sports attire company wants to leverage the Adobe Experience Platform powered smart segments and activate them using Adobe Campaign to reach out to their customer base across the different channels supported by Adobe Campaign.
Once the messages are sent, they want to enhance the customer profile in Adobe Experience platform with experience data from Adobe Campaign such as sends, open and clicks.
The result is cross channel campaigns that are more consistent across the Adobe Experience cloud ecosystem and a rich customer profile that is quickly adapting and learning.
Learn more on Adobe Campaign integration with Adobe Experience Platform
Adobe Campaign Managed Cloud Services supports the activation of identities described in the table below. Learn more about identities.
|external_id||Custom user IDs||Select this target identity when your source identity is a custom namespace. We recommend using this identity and mapping it to the ID in your Campaign instance that represents customer (loyalty_ID, account_ID, customer_ID…)|
|ECID||Experience Cloud ID||A namespace that represents ECID. This namespace can also be referred to by the following aliases: “Adobe Marketing Cloud ID”, “Adobe Experience Cloud ID”, “Adobe Experience Platform ID”. See the following document on ECID for more information.|
|email_lc_sha256||Email addresses hashed with the SHA256 algorithm||Both plain text and SHA256 hashed email addresses are supported by Adobe Experience Platform. When your source field contains unhashed attributes, check the Apply transformation option, to have Platform automatically hash the data on activation.|
|phone_sha256||Phone numbers hashed with the SHA256 algorithm||Both plain text and SHA256 hashed phone numbers are supported by Adobe Experience Platform. When your source field contains unhashed attributes, check the Apply transformation option, to have Platform automatically hash the data on activation.|
|GAID||Google Advertising ID||Select the GAID target identity when your source identity is a GAID namespace.|
|IDFA||Apple ID for Advertisers||Select the IDFA target identity when your source identity is an IDFA namespace.|
Refer to the table below for information about the destination export type and frequency.
|Export type||Profile-based||You are exporting all members of a segment, together with the desired schema fields (for example: email address, phone number, last name), as chosen in the select profile attributes screen of the destination activation workflow.|
|Export frequency||Batch||Batch destinations export files to downstream platforms in increments of three, six, eight, twelve, or twenty-four hours. Read more about batch file-based destinations.|
To connect to the destination, you need the Manage Destinations access control permission. Read the access control overview or contact your product administrator to obtain the required permissions.
To connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, refer to the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
Select the marketing actions applicable to the data that you want to export to the destination. For Adobe Campaign, we recommend you select the Email Targeting marketing action.
For more information about marketing actions, see the data usage policies overview page.
To activate data, you need the Manage Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
Read Activate audience data to batch profile export destinations for instructions on activating audience data to this destination.
Select XDM fields to export with the profiles and map them to the corresponding Adobe Campaign fields.Learn more on identity and attributes selection for email marketing destinations
Select source fields:
Select an identifier (For example: the email field) as source identity that uniquely identifies a profile in Adobe Experience Platform and Adobe Campaign.
Select all other XDM source profile attributes that need to be exported to Adobe Campaign.
The “segmentMembershipStatus” field is a required mapping to reflect segmentMembership status. This field is added by default and cannot be modified or removed.
Map each field with its target field in Adobe Campaign. Available target fields are determined by the target mapping selected when creating the destination.
Identify mandatory attributes and deduplication keys. Note that values in attributes marked as “Mandatory” or “Deduplication key” cannot be null.
Mandatory attributes ensure that all profile records contain the selected attribute(s). For example: all exported profiles contain an email address. Recommendation is to set to mandatory both the identity field and the field used as deduplication key.
A deduplication key is a primary key which determines the identity by which users want their profiles to be deduplicated.
Make sure that the deduplication key attribute’s name matches a column name of the selected target mapping.
Once mapping has been performed, you can review and complete the destination configuration to start sending data to Campaign.
Learn how to review and complete destination configuration.
Once a destination has been activated, you can access the corresponding job and exported data in Campaign.
Navigate to the Administration > Audit > Audience load jobs menu to monitor all export jobs activated from Adobe Experience Platform.
Navigate to the Profile and target > List > AEP audiences menu to access audiences created after activating a destination.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, read the Data Governance overview.