Release month | Update type | Description |
---|---|---|
April 2024 | Functionality and documentation update | When connecting to the Target destination and 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. |
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.
For a brief overview on how to configure the Adobe Target connection in Experience Platform, watch the video below.
The table below displays the supported use cases for the Adobe Target destination, based on your implementation type, with or without Web SDK and with or without edge segmentation enabled.
Adobe Target implementation without Web SDK | Adobe Target implementation with Web SDK | Adobe Target implementation with Web SDK and edge segmentation off |
---|---|---|
|
|
|
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.
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.
In Adobe Target, make sure that your user has:
Read more about granting permissions for Target Premium and for Target Standard.
This section describes which types of audiences you can export to this destination.
When activating edge audiences for same-page and next-page personalization use cases, the audiences must use an 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 cases. Read about all available use cases,based on implementation type.
If you map edge audiences which use a different merge policy to Adobe Target destinations, those audiences will not be evaluated for real-time and next-page use cases.
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. |
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. |
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.
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.
The datastream ID is unique for each Adobe Target destination connection. You cannot use the same datastream ID for multiple Adobe Target destination connections.
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.
Adobe Target implementation without Web SDK | Adobe Target implementation with Web SDK | Adobe Target implementation with Web SDK and edge segmentation off |
---|---|---|
|
|
|
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.
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.
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.
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.
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.
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.
Adobe Target reads profile data from the Adobe Experience Platform Edge Network, so no data gets exported.
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.