- Product documentation
- Latest Updates
- Release Notes
- Getting started
- Profiles and audiences
- Communication channels
- Designing email content
- Testing and Sending
- Reporting
- Integrating with other solutions
- 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
- Working with Adobe Experience Platform audiences
- Developing
- Administrating
- Get started with Campaign Standard administration
- Monitoring guidelines
- 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
- Adobe Launch Synchronization FAQ
- Experience Platform SDK integration FAQ
- Configuring Launch rules to support Adobe Campaign Standard use cases
- Mobile use cases supported in Adobe Campaign Standard
- 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
About Campaign-Audience Manager or People core service integration
Depending on the data exchanged, importing audiences in Adobe Campaign may be subject to legal restrictions.
Adobe Campaign allows you to exchange and share audiences/segments with the different Adobe Experience Cloud applications. Integrating Adobe Campaign with People core service (also known as Profiles & Audiences core service) or Adobe Audience Manager allows you to:
- Import audiences/segments from different Adobe Experience Cloud solutions into Adobe Campaign. Audiences can be imported from the Audiences menu in Adobe Campaign.
- Export audiences as shared audiences/segments. These audiences can be used in the different Adobe Experience Cloud solutions that you use. Audiences can be exported after targeting activities in a workflow, using the Save audience activity.
Integration supports two types of Adobe Experience Cloud IDs:
-
Visitor ID: this type of ID allows you to reconcile Adobe Experience Cloud visitors with Adobe Campaign profiles. As soon as a connection is enabled via Adobe IMS, Marketing Cloud Visitor ID Service is activated, which replaces the permanent cookie used by Adobe Campaign. This allows you to identify a visitor then link it to a profile.
A visitor ID is linked to a profile as soon as the profile clicks in an email sent via Adobe Campaign:- If the profile already has a visitor ID, the profile’s browser data allows Adobe Campaign to recover and automatically link the profile to the visitor ID.
- If no visitor ID is found, a new ID is created. This visitor ID is stored in the profile tracking logs.
The ID will then be recognized by the other Adobe Marketing Cloud applications with the same CNAME.
-
Declared ID: this type of ID allows you to reconcile any type of data with elements from the Adobe Campaign database. It is represented in Adobe Campaign as a predefined reconciliation key. When exchanging data, the Adobe Campaign database identifiers are hashed. These hashed IDs are then compared to the hashed IDs of the Adobe Marketing Cloud audience involved in the import or export.
This integration supports regular declared IDs, hashed declared IDs and encrypted declared IDs.CAUTIONDeclared ID will only work with Adobe Audience Manager. Declared ID will not work without it.
Encryption allows you to share encrypted data in data sources (for example PII) using the declared ID by specifying the encryption algorithm.
For example, with the ability to decrypt encrypted email addresses or SMS numbers, you can also send triggered messages to your users even if their profile does not exist in the Adobe Campaign database.
The following diagram details how this integration works. Here, AAM stands for Adobe Audience Manager et ACS for Adobe Campaign Standard.
