(Beta) Experience Cloud Audiences connection

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.

Use cases and benefits

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.

Enable Data Management Platform use cases

In Audience Manager, you can use Experience Platform audiences for Data Management Platform use cases, such as:

• Add third party data to your segments;
• Algorithmic modeling;
• Activate your audiences to cookie-based destinations that are not yet supported in the Experience Platform destinations catalog.

Granular control of exported audiences

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.

Share Experience Platform audiences with further Experience Cloud solutions

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:

• Adobe Campaign
• Adobe Target
• Advertising Cloud
• Analytics
• Marketo

Prerequisites

For customers who are using the legacy audience sharing solution

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.

Known limitations and callouts

Note the following known limitations and important callouts in the beta release of the Experience Cloud Audiences card:

• Dataflows monitoring is not supported.
• When connecting to the destination, you can see an option to enable dataflow alerts. Though visible in the UI, the enable alerts option is not supported in the beta release.
• Backfills are not supported. The first export to Audience Manager or other Experience Cloud solutions does not include a historical population of the audiences.
• 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.

Latency when activating audiences

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.

Supported identities

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.

Supported audiences

This section describes which type of audiences you can export to this destination.

Export type and frequency

Refer to the table below for information about the destination export type and frequency.

Connect to the destination

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.

Authenticate to destination

To authenticate to the destination, select Set up in the destination card view in the catalog and select Connect to destination.

Fill in destination details

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.

• Name: A name by which you will recognize this destination in the future.
• Description: A description that will help you identify this destination in the future.

When you are finished providing details for your destination connection, select Next.

Activate audiences to this destination

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.

Validate data export

To validate successful data export, you can check that your audiences have successfully made it through to your desired Experience Cloud solution.

Validate data in Audience Manager

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.

Data usage and governance

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.

Permissions management in Audience Manager

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.

Business.Adobe.com resources