۶Ƶ Target connection adobe-target-connection
Destination changelog changelog
Overview overview
۶Ƶ 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.
۶Ƶ Target is a personalization connection in the ۶Ƶ Experience Platform destinations catalog.
Video overview video-overview
For a brief overview on how to configure the ۶Ƶ 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 ۶Ƶ Target destination, based on your implementation type, with or without Web SDK and with or without edge segmentation enabled.
- A datastream is not required. ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ 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 ID datastream-id
When configuring the ۶Ƶ Target connection to use a datastream ID, you must have the ۶Ƶ Experience Platform Web SDK implemented.
Configuring the ۶Ƶ Target connection without using a datastream ID does not require you to implement the Web SDK.
Prerequisites in ۶Ƶ Target prerequisites-in-adobe-target
In ۶Ƶ 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 ۶Ƶ 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.
Export type and frequency export-type-frequency
Refer to the table below for information about the destination export type and frequency.
Connect to the destination connect
To connect to this destination, follow the steps described in the destination configuration tutorial.
۶Ƶ Experience Platform automatically connects to your company’s ۶Ƶ 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 ۶Ƶ Experience Platform services enabled. See configuring a datastream for detailed information on how to configure a datastream for ۶Ƶ Experience Platform and ۶Ƶ Target.
note important IMPORTANT The datastream ID is unique for each ۶Ƶ Target destination connection. You cannot use the same datastream ID for multiple ۶Ƶ 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.- None: Select this option if you need to configure ۶Ƶ 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 in the supported use cases section for a comparison of available use cases per implementation type.
table 0-row-3 1-row-3 ۶Ƶ Target implementation without Web SDK ۶Ƶ Target implementation with Web SDK ۶Ƶ Target implementation with Web SDK and edge segmentation off - A datastream is not required. ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ 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 ۶Ƶ Target workspace to which audiences will be shared. You can select a single workspace for each ۶Ƶ 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 ۶Ƶ Target connection when that audience is already being used in an ۶Ƶ Target activity. Trying to remove an audience from an ۶Ƶ Target connection results in an error if the audience is used by an ۶Ƶ 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
۶Ƶ Target reads profile data from the ۶Ƶ Experience Platform Edge Network, so no data gets exported.
Data usage and governance data-usage-governance
All ۶Ƶ Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how ۶Ƶ Experience Platform enforces data governance, read the Data Governance overview.