Adobe Target connection adobe-target-connection

Destination changelog changelog

Release month
Update type
Description
April 2024
Functionality and documentation update
When connecting to the Target destination with using a datastream ID, you now do not need to necessarily enable the datastream for edge segmentation. This means that the Target destination will work with batch and streaming audiences, though the use cases that you can accomplish differ. View the table in the connection parameters section for more information.
January 2024
Functionality and documentation update
You can now share audiences and profile attributes to the Adobe Target connection for the default production sandbox and other non-default sandboxes.
June 2023
Functionality and documentation update
As of June 2023, you can select the Adobe Target workspace that you want to share audiences to, when configuring a new Adobe Target destination connection. See the connection parameters section for more information. Additionally, see the tutorial on configuring workspaces in Adobe Target for more information about workspaces.
May 2023
Functionality and documentation update
As of May 2023, the Adobe Target connection supports attribute-based personalization and is generally available to all customers.

Overview overview

Adobe Target is an application that provides real-time, AI-powered personalization and experimentation capabilities in all inbound customer interactions across websites, mobile apps, and more.

Adobe Target is a personalization connection in the Adobe Experience Platform destinations catalog.

Video overview video-overview

For a brief overview on how to configure the Adobe Target connection in Experience Platform, watch the video below.

Prerequisites prerequisites

Datastream ID datastream-id

When configuring the Adobe Target connection to use a datastream ID, you must have the Adobe Experience Platform Web SDK implemented.

Configuring the Adobe Target connection without using a datastream ID does not require you to implement the Web SDK.

IMPORTANT
Before creating an Adobe Target connection, read the guide on how to configure personalization destinations for same-page and next-page personalization. This guide takes you through the required configuration steps for same-page and next-page personalization use cases, across multiple Experience Platform components. To achieve same-page and next-page personalization use cases, you must use a datastream ID when configuring the Adobe Target connection.

Prerequisites in Adobe Target prerequisites-in-adobe-target

In Adobe Target, make sure that your user has:

Read more about granting permissions for Target Premium and for Target Standard.

Supported audiences supported-audiences

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

IMPORTANT
Audiences that you activate to this destination must use the Active-on-Edge Merge Policy. The Active-On-Edge merge policy ensures that audiences are constantly evaluated on the edge and are available for real-time and next-page personalization use case.
If you map audiences which use a different merge policy to edge destinations, those audiences will not be evaluated.
Follow the instructions on creating a merge policy, and make sure to enable the Active-On-Edge Merge Policy toggle.
Audience origin
Supported
Description
Segmentation Service
Audiences generated through the Experience Platform Segmentation Service.
Custom uploads
X
Audiences imported into Experience Platform from CSV files.

Export type and frequency export-type-frequency

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

Item
Type
Notes
Export type
Profile request
You are requesting all the audiences that are mapped in the Adobe Target destination for a single profile.
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.

Connect to the destination connect

IMPORTANT
To connect to the destination, you need the View Destinations and Manage Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

To connect to this destination, follow the steps described in the destination configuration tutorial.

Adobe Experience Platform automatically connects to your company’s Adobe Target instance. There is no authentication required.

Connection parameters parameters

While setting up this destination, you must provide the following information:

  • Name: Fill in the preferred name for this destination.

  • Description: Enter a description for your destination. For example, you can mention which campaign you are using this destination for. This field is optional.

  • Datastream ID: This determines in which Data Collection datastream the audiences will be included. The drop-down menu shows only datastreams that have the Target and Adobe Experience Platform services enabled. See configuring a datastream for detailed information on how to configure a datastream for Adobe Experience Platform and Adobe Target.

    note important
    IMPORTANT
    The datastream ID is unique for each Adobe Target destination connection. If you need to map the same audiences to multiple datastreams, you must create a new destination connection for each datastream ID, and go through the audience activation flow.
    • None: Select this option if you need to configure Adobe Target personalization but you cannot implement the Experience Platform Web SDK. When using this option, audiences exported from Experience Platform to Target only support next-session personalization, and edge segmentation is disabled. Reference the table below for a comparison of available use cases per implementation type.
    table 0-row-3 1-row-3
    Adobe Target implementation without Web SDK Adobe Target implementation with Web SDK Adobe Target implementation with Web SDK and edge segmentation off
    • A datastream is not required. Adobe Target can be deployed through at.js, server-side, or hybrid implementation methods.
    • Edge segmentation is not supported.
    • Same-page and next-page personalization are not supported.
    • You can share audiences and profile attributes to the Adobe Target connection for the default production sandbox and non-default sandboxes.
    • To configure next-session personalization without using a datastream ID, use at.js.
    • A datastream with Adobe Target and Experience Platform configured as services is required.
    • Edge segmentation works as expected.
    • Same-page and next-page personalization are supported.
    • Sharing audiences and profile attributes from other sandboxes is supported.
    • A datastream with Adobe Target and Experience Platform configured as services is required.
    • When configuring the datastream, do not select the Edge segmentation checkbox.
    • Next-session personalization is supported.
    • Sharing audiences and profile attributes from other sandboxes is supported.
  • Workspace: Select the Adobe Target workspace to which audiences will be shared. You can select a single workspace for each Adobe Target connection. Upon activation, audiences are routed to the selected workspace while following the applicable Experience Platform data usage labels.

NOTE
When using a custom Target workspace for same-page and next-page personalization with attributes, only the selected audiences are sent to the selected Target workspace. The mapped attributes are sent to the default Target workspace.


This behavior will change in a future update.

Enable alerts enable-alerts

You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.

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

Activate audiences to this destination activate

IMPORTANT
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

Read Activate audiences to edge personalization destinations for instructions on activating audiences to this destination.

Remove audiences from a Target destination remove

There are extra steps required to remove an audience from an existing Adobe Target connection when that audience is already being used in an Adobe Target activity. Trying to remove an audience from an Adobe Target connection results in an error if the audience is used by an Adobe Target activity.

Platform UI image showing an error caused by attempting to remove an audience that is used by a Target activity.

To remove an audience from a Target destination when the audience is being used in an activity, you must first either remove the audience from the Target activity which is using it, or delete the activity altogether. Then, you can remove the audience from your Target connection.

If the audience is not being used in an activity, go to Destinations > Browse > Select destination dataflow > Activation data, select the audiences that you want to remove, then select Remove audiences.

Exported data exported-data

Adobe Target reads profile data from the Adobe Experience Platform Edge Network, so no data gets exported.

Data usage and governance data-usage-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.

recommendation-more-help
7f4d1967-bf93-4dba-9789-bb6b505339d6