The audience sharing functionality between Audience Manager and Adobe Experience Platform allows you to share your Audience Manager traits and segments to Adobe Experience Platform and Experience Platform segments to Audience Manager.
You need the Audience Manager source connector and the Experience Cloud Audiences destination in Experience Platform to enable audience sharing between Audience Manager and Adobe Experience Platform.
You can use Audience Manager traits and segments in Experience Platform to add Audience Manager data to your customer profiles and to benefit from the Experience Platform segmentation service.
In Audience Manager, you can use Experience Platform segments for Data Management Platform use cases, such as:
Additionally, your Experience Platform segments are shared to other Experience Cloud solutions, via Core Services.
See the table below for an overview of audience sharing use cases:
Use Case | Adobe Experience Platform | Audience Manager | Core Services |
---|---|---|---|
Audience Sharing |
|
|
Use Experience Platform segments in other Experience Cloud solutions, such as Adobe Target, Advertising Cloud, or Marketo. |
The sections below describe how to enable data sharing from Audience Manager to Experience Platform and how to use Audience Manager traits and segments in Experience Platform.
To send segments and traits from Audience Manager to Experience Platform, you must set up the Audience Manager source connector in the Experience Platform sources catalog. This is a self-service workflow that does not require involvement from Adobe Customer Care or engineering teams. To set up the Audience Manager source connector, read:
Adobe encourages customers to configure the connection without selecting the Select all segments and Select all traits options, as shown below. The ingestion of sizeable Audience Manager segment populations has a direct impact on your total profile count when you first send an Audience Manager segment to Platform using the Audience Manager source. This means that selecting all segments can potentially lead to a Profile count in excess of your license usage entitlement.
After setting up the Audience Manager source connector to import traits and segments from Audience Manager, your Audience Manager data appears in Experience Platform as Audiences in the segment workflow. For more information on your Audience Manager segments and traits in Experience Platform, read:
The sections below describe how to enable data sharing from Experience Platform to Audience Manager and how to use Experience Platform segments in Audience Manager.
This section describes the legacy segment sharing integration from Experience Platform to Audience Manager. You can now set up this integration without support from Adobe Customer representatives. For more information, read the Experience Cloud Audiences destination documentation.
Contact your Adobe Customer Success Manager or Customer Care to unlock access to this functionality.
To send segments from Experience Platform to Audience Manager, you must contact either Customer Care or your Customer Success Manager. Customer Care and Customer Support Management teams must file a ticket (see template ticket AAM-52354) to enable the connection from Platform to Audience Manager.
Be sure to share plans for the data going from Platform to Audience Manager, to ensure that the connection is set up correctly. For example, if you need regional data to be shared for segments sent to Adobe Target, this information needs to be communicated in the ticket. The data sharing connection from Experience Platform to Audience Manager is set up within six business days of the request being submitted.
Segments that you create in Experience Platform appear in your Audience Manager interface as signals, traits, and segments, with the following composition rules:
segID = segment ID
.Select Audience Data > Signals > General Online Data and search by SegId
to find signals coming in from Experience Platform. You can use this screen for debugging purposes, to check if the integration between Experience Platform and Audience Manager has been set up correctly.
Audience Manager automatically creates a trait folder called Experience Platform Traits in your trait storage.
You can use automatically created traits in segments alongside other traits. For example, you can mix traits created from Experience Platform segments with third party traits acquired through the Audience Marketplace.
For an example of a trait created automatically from an Experience Platform segment, see the screenshot below:
Item number | Name | Description |
---|---|---|
1 | Trait Type | Traits created from Experience Platform segments are created as onboarded traits in Audience Manager. |
2 | Data Source | Automatically created. All traits and segments that are created automatically from Experience Platform segments are stored in the data source Adobe Experience Platform Audience Sharing. |
3 | Integration Code | The integration code corresponds to the segment ID in Experience Platform. |
4 | Trait Expression | The trait expression is segID = segment ID in Experience Platform . |
5 | Segments with this Trait | An automatically created segment that uses this trait as its composition. |
Audience Manager automatically creates a segment folder called Experience Platform Segments in your segment storage.
For an example of a segment created automatically from an Experience Platform segment, see the screenshot below:
Item number | Name | Description |
---|---|---|
1 | Integration Code | The integration code corresponds to the segment ID in Experience Platform. |
2 | Data Source | Automatically created. All traits and segments that are created automatically from Experience Platform segments are stored in the data source Adobe Experience Platform Audience Sharing. |
3 | Profile Merge Rule | External Merge Policy indicates that automatically created segments follow the merge policy set up in Experience Platform. |
4 | Segment Rule | The segment consists of the trait described in the Traits section. |
In order to enforce data usage compliance in Experience Platform, all applicable datasets and fields must be given appropriate data usage labels. In addition, data usage policies must be enabled for specific marketing actions against those labels, as outlined by the Data Usage Labeling and Enforcement (DULE) framework.
In the audience sharing process between Audience Manager and Experience Platform, any Data Export Controls that have been applied to Audience Manager segments are translated to equivalent labels and marketing actions recognized by Experience Platform Data Governance, and vice versa.
For more general information on Data Export Controls, please refer to the Data Export Controls documentation.
This document provides a reference for how specific Audience Manager Data Export Controls map to data usage labels and marketing actions in Platform.
The following table outlines how specific Data Export Controls map to recognized data usage labels:
Data Export Control | Data usage label |
---|---|
Cannot be used with personally identifiable information | C3: Data cannot be combined or otherwise used with directly identifiable information |
Cannot be used for offsite ad targeting | C5: Data cannot be used for interest-based, cross-site targeting of content or ads |
Cannot be used for onsite ad targeting | C6: Data cannot be used for on-site ad targeting |
Cannot be used for onsite personalization | C7: Data cannot be used for on-site targeting of content |
The following table outlines how specific Data Export Labels map to recognized marketing actions:
Data Export Label | Marketing action |
---|---|
This destination may enable a combination with personally identifiable information (PII) | Combine with PII |
This destination may be used for off-site ad targeting | Cross Site Targeting |
This destination may be used for on-site ad targeting | Onsite Advertising |
This destination may be used for on-site ad personalization | Onsite Personalization |
Segment population numbers can vary between your Audience Manager and Experience Platform segments. While segment numbers for similar or identical audiences should be close, differences in populations can be due to factors listed below.
Audience Manager updates reporting numbers in the interface once per day. The timing of this update rarely aligns with the time of the segment evaluation in Experience Platform.
Profile Merge Rules in Audience Manager and Merge Policies in Experience Platform work differently, and the identity graph used for each varies. Because of this, some differences between segment populations are expected.
When sharing segments from Experience Platform to Audience Manager, your Platform organization default merge policy takes precedence over the merge policy used by the segment shared with Audience Manager. For example, if the shared segment’s merge policy allows for ID stitching, but the organization’s default merge policy does not, this might result in population differences between Platform and Audience Manager.
The integration between Adobe Experience Platform and Audience Manager shares a number of standard identity namespaces for all customers: ECID, IDFA, GAID, hashed email addresses (EMAIL_LC_SHA256), AdCloud ID. If your Experience Platform segments use any of these as primary identity for the qualified profiles, the profiles are counted in Audience Manager traits and segments.
Audiences in Experience Platform with identities keyed off raw emails never appear in Audience Manager.
For example, if you had an Experience Platform segment “All my customers”, and the qualified profiles would be CRM IDs, ECID, IDFA, raw and hashed email addresses, the corresponding segment in Audience Manager would only include profiles keyed off of ECID, IDFA, and hashed email addresses. The segment population in Audience Manager would be smaller than the one in Experience Platform.