Adobe Target connection adobe-target-connection
Destination changelog changelog
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.
Supported use cases based on implementation type supported-use-cases
The table below displays the supported use cases for the Adobe Target destination, based on your implementation type, with or without the Web SDK or Edge Network API, and with or without edge segmentation enabled.
- 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, use at.js.
- Adobe Target can be integrated using the Web SDK or the Edge Network API.
- 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.
- Adobe Target can be integrated using the Web SDK or the Edge Network API.
- 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.
Prerequisites prerequisites
Datastream datastream
When configuring the Adobe Target connection to use a datastream, you must have Adobe Experience Platform Data Collection implemented.
Configuring the Adobe Target connection without using a datastream does not require you to implement the Web SDK.
Prerequisites in Adobe Target prerequisites-in-adobe-target
In Adobe Target, make sure that your user has:
- Access to the default workspace;
- The Approver role.
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.
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.
This category includes all audience origins outside of audiences generated through the Segmentation Service. Read about the various audience origins. Some examples include:
- custom upload audiences imported into Experience Platform from CSV files,
- look-alike audiences,
- federated audiences,
- audiences generated in other Experience Platform apps such as Adobe Journey Optimizer,
- and more.
Supported audiences by audience data type:
Export type and frequency export-type-frequency
Refer to the table below for information about the destination export type and frequency.
Implementation considerations implementation-considerations
Keep the following in mind when implementing the Adobe Target connection:
- Same IMS Organization: Adobe Experience Platform and Adobe Target must belong to the same IMS Organization.
- Identity management for first-login personalization: First-login personalization requires the primary identity in the personalization request to match the known customer identity in the Real-Time CDP identity graph. If the primary identity is an ECID or an unstitched identity, identity reconciliation may take several minutes before edge personalization reflects the known customer’s data.
- Custom identity namespace lookups: Lookups on custom identity namespaces require a Web SDK or Edge Network API deployment, with the relevant identities mapped appropriately.
- Edge profile time-to-live (TTL): Edge profiles have a 14-day TTL. After 14 days of inactivity, the edge profile expires and must be retrieved from the hub on the next page visit. This means the first visit after expiry may use a historical profile view rather than real-time data.
Connect to the destination connect
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: 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 Datastream uniqueness across organization: The combination of datastream ID and sandbox name must be unique for Adobe Target destination connections within an IMS Org. This means: - The same combination of datastream ID + sandbox name cannot be used for multiple Adobe Target destination connections across the entire organization
- You can use the same datastream ID for different destination connections as long as the connections are on different sandboxes
- This rule applies to all datastream selections, including when you select None
- None: Select this option if you need to configure Adobe Target personalization but you cannot implement the Adobe 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 in the supported use cases section 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 or Edge Network API Adobe Target implementation with Web SDK or Edge Network API 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, use at.js.
- Adobe Target can be integrated using the Web SDK or the Edge Network API.
- 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.
- Adobe Target can be integrated using the Web SDK or the Edge Network API.
- 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.
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
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.
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.