Merge pull request #5105 from AdobeDocs/KB-2156-Update-Adobe-Target--…

…-AEP-connection-Documentation Update Adobe Target - AEP connection Documentation
chelleis · Apr 18, 2024 · 4cedb4c · 4cedb4c
2 parents 0c3f4a8 + 92238ee
commit 4cedb4c
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/help/destinations/catalog/personalization/adobe-target-connection.md b/help/destinations/catalog/personalization/adobe-target-connection.md
@@ -100,6 +100,11 @@ While [setting up](../../ui/connect-destination.md) this destination, you must p
 * **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](../../../datastreams/configure.md#aep) for detailed information on how to configure a datastream for Adobe Experience Platform and Adobe Target.
+
+    >[!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](../../ui/connect-destination.md) for each datastream ID, and go through the [audience activation flow](#activate).
+
     * **[!UICONTROL None]**: Select this option if you need to configure Adobe Target personalization but you cannot implement the [Experience Platform Web SDK](/help/web-sdk/home.md). When using this option, audiences exported from Experience Platform to Target only support next-session personalization, and edge segmentation is disabled. See the table below for more information.
 
     |Adobe Target implementation (without Web SDK)| Web SDK implementation |