This destination allows you to share audiences from Experience Platform to various Experience Cloud solutions, like Audience Manager, Analytics, Advertising Cloud, Adobe Campaign, Target, or Marketo.
To help you better understand how and when you should use the Experience Cloud Audiences destination, here are sample use cases that Adobe Experience Platform customers can solve by using this destination.
In Audience Manager, you can use Experience Platform audiences for Data Management Platform use cases, such as:
Use the new self-service audience sharing integration via the Experience Cloud Audiences destination to select which audiences to export to Audience Manager and beyond. This allows you to determine which audiences you want to share with other Experience Cloud solutions and which audiences you want to keep in Experience Platform exclusively.
The legacy audience sharing integration did not allow for a granular control of which audiences should be exported to Audience Manager and beyond.
Apart from sharing audiences with Audience Manager, the Experience Platform Audiences destination card enables you to share audiences with any other Experience Cloud solution that you are provisioned for, including:
If you are already sharing audiences from Experience Platform to Audience Manager and other Experience Cloud solutions via the legacy audience sharing integration, you must contact either Customer Care or your Adobe account team to disable the legacy integration. Customer Care and Adobe account teams must file a Jira ticket (see template ticket PLAT-160986) to disable the integration.
The turnaround time to resolve the deprovisioning ticket for beta customers is six business days or less. After the existing legacy integration has been disabled, you can proceed to creating a connection via the self-service destination card.
The audience export from Experience Platform to your other solutions will be stopped in the time between the Jira ticket resolution and the time a new connection is established through the destination card. You can minimize this downtime by creating the connection via the destination card as soon as the Jira ticket is closed.
Note the following known limitations and important callouts in the beta release of the Experience Cloud Audiences card:
There is a four-hour latency between the time that audiences are first activated in Experience Platform and the time that they are ready to be used in Audience Manager and other Experience Cloud solutions for certain use cases.
It can take up to 24 hours for audiences to be fully available in Audience Manager for all use-cases and up to 48 hours for audiences from the Experience Cloud Audiences to appear in Audience Manager reports.
Metadata, such as audience names, is available in Audience Manager within minutes of setting up the export to the Experience Cloud Audiences destination.
The profiles that are exported to the Experience Cloud Audiences destination are mapped to the identities described in the table below. Learn more about identities.
|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.|
|GAID||Google Advertising ID||Profiles ingested into Experience Platform with a primary identity of Google Advertising ID (GAID) can be exported to this destination.|
|IDFA||Apple ID for Advertisers||Profiles ingested into Experience Platform with a primary identity of Apple ID for Advertisers (IDFA) can be exported to this destination.|
|email_lc_sha256||Email addresses hashed with the SHA256 algorithm||Profiles ingested into Experience Platform with a primary identity of hashed email address can be exported to this destination.|
This section describes which type of audiences you can export to this destination.
|Segmentation Service||✓||Audiences generated through the Experience Platform Segmentation Service.|
|Custom uploads||✓||Audiences imported into Experience Platform from CSV files.|
Refer to the table below for information about the destination export type and frequency.
|Export type||Audience export||You are exporting all members of an audience keyed off the identities listed in the section above.|
|Export frequency||Streaming||Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on audience evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations.|
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.
In the beta release, you can create a single destination connection to the Experience Cloud Audiences destination, across all sandboxes belonging to your Experience Platform organization.
To authenticate to the destination, select Set up in the destination card view in the catalog and select Connect to destination.
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.
When you are finished providing details for your destination connection, select Next.
Read Activate profiles and audiences to streaming audience export destinations for instructions on activating audiences to this destination. Note that no mapping step is required and no scheduling step is available for this destination.
To validate successful data export, you can check that your audiences have successfully made it through to your desired Experience Cloud solution.
Your Experience Platform audiences appear in Audience Manager as signals, traits, and segments. You can verify in Audience Manager if the data has appeared as described in the documentation links above.
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.
Data governance in Experience Platform is enforced by both data usage labels and marketing actions.
Data usage labels will transfer to applications but marketing actions will not. This means that once they land in Audience Manager, audiences from Experience Platform can be exported to any available destinations. In Audience Manager, you can use data export controls to block audiences from being exported to certain destinations.
Audiences and traits in Audience Manager are subject to Role-Based Access Controls (RBAC).
Audiences exported from Experience Platform are assigned to a specific datasource in Audience Manager called Experience Platform Segments.
To allow only certain users access to the audiences, you can apply access controls to the audiences belonging to the datasource. You must set new access control permissions in Audience Manager for these audiences and traits created from Experience Platform segments.