About Campaign-Audience Manager or People core service integration about-campaign-audience-manager-or-people-core-service-integration
ÃÛ¶¹ÊÓƵ Campaign allows you to exchange and share audiences/segments with the different ÃÛ¶¹ÊÓƵ Experience Cloud applications. Integrating ÃÛ¶¹ÊÓƵ Campaign with People core service (also known as Profiles & Audiences core service) or ÃÛ¶¹ÊÓƵ Audience Manager allows you to:
- Import audiences/segments from different ÃÛ¶¹ÊÓƵ Experience Cloud solutions into ÃÛ¶¹ÊÓƵ Campaign. Audiences can be imported from the Audiences menu in ÃÛ¶¹ÊÓƵ Campaign.
- Export audiences as shared audiences/segments. These audiences can be used in the different ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Experience Cloud IDs:
-
Visitor ID: this type of ID allows you to reconcile ÃÛ¶¹ÊÓƵ Experience Cloud visitors with ÃÛ¶¹ÊÓƵ Campaign profiles. As soon as a connection is enabled via ÃÛ¶¹ÊÓƵ IMS, Marketing Cloud Visitor ID Service is activated, which replaces the permanent cookie used by ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Campaign:- If the profile already has a visitor ID, the profile’s browser data allows ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ 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 ÃÛ¶¹ÊÓƵ Campaign database. It is represented in ÃÛ¶¹ÊÓƵ Campaign as a predefined reconciliation key. When exchanging data, the ÃÛ¶¹ÊÓƵ Campaign database identifiers are hashed. These hashed IDs are then compared to the hashed IDs of the ÃÛ¶¹ÊÓƵ Marketing Cloud audience involved in the import or export.
This integration supports regular declared IDs, hashed declared IDs and encrypted declared IDs.note note NOTE Declared ID data source can now also be used with People core service integration. If you are using the People core service integration and want to add the Audience Manager integration, you will need the help of an ÃÛ¶¹ÊÓƵ Audience Manager consultant’s to avoid losing all of the ID syncs collected when transitioning to using this Declared ID data source in an ÃÛ¶¹ÊÓƵ Audience Manager context. 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 ÃÛ¶¹ÊÓƵ Campaign database.
The following diagram details how this integration works. Here, AAM stands for ÃÛ¶¹ÊÓƵ Audience Manager and ACS for ÃÛ¶¹ÊÓƵ Campaign Standard.
