Merge remote-tracking branch 'upstream/main' into snowflake-batch-updates

Author: Carlo Javier

help/datastreams/bot-detection.md

@@ -29,7 +29,13 @@ This bot scoring helps the solutions receiving the request correctly identify bo
 >
 >Adobe solutions may handle bot scoring in different ways. For example, Adobe Analytics uses its own [bot filtering service](https://experienceleague.adobe.com/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/bot-removal/bot-rules.html) and does not use the score set by the Edge Network. The two services use the same [IAB bot list](https://www.iab.com/guidelines/iab-abc-international-spiders-bots-list/), so the bot scoring is identical.
 
-Bot detection rules can take up to 15 minutes to propagate across the Edge Network after being created.
+## Technical considerations {#technical-considerations}
+
+Before enabling bot detection on your datastreams, here are a few key points to keep in mind to ensure accurate results and a smooth implementation:
+
+* Bot detection applies only to unauthenticated requests sent to `edge.adobedc.net`.
+* Authenticated requests sent to `server.adobedc.net` are not evaluated for bot traffic, as authenticated traffic is considered trustworthy.
+* Bot detection rules can take up to 15 minutes to propagate across the Edge Network after being created.
 
 ## Prerequisites {#prerequisites}
 

help/destinations/api/activate-segments-file-based-destinations.md

@@ -1090,7 +1090,7 @@ curl --location --request POST 'https://platform.adobe.io/data/foundation/flowse
 
 ### Add encryption to exported files
 
-Optionally, you can add encryption to your exported files. To do this, you need to add items from the `encryptionSpecs`. See the request example below with the mandatory parameters highlighted:
+Optionally, you can add encryption to your exported files. To do this, you need to add items from the `encryption` object. See the request example below with the mandatory parameters highlighted:
 
 
 >[!BEGINSHADEBOX]
@@ -1099,7 +1099,7 @@ Optionally, you can add encryption to your exported files. To do this, you need
 
 ```json {line-numbers="true" start-line="1" highlight="26-27"}
 
-           "encryptionSpecs": [
+           "encryption": [
                 {
                     "name": "File PGP/GPG Encryption",
                     "type": "FileAsymmetric",
@@ -1159,12 +1159,12 @@ curl --location --request POST 'https://platform.adobe.io/data/foundation/flowse
       "sshKey": "<Add SSH key>"
       }
     },
-  "encryptionSpecs":{
-     "specName": "Encryption spec",
-     "params": {
-         "encryptionAlgo":"PGPGPG",
-         "publicKey":"<Add public key>"
-      }            
+  "encryption": {
+    "specName": "File Encryption",
+        "params": {
+            "encryptionAlgo": "PGP/GPG",
+            "publicKey": "<Add public key>"
+        }
     },
   "connectionSpec": {
     "id": "36965a81-b1c6-401b-99f8-22508f1e6a26", // SFTP connection spec
@@ -1217,7 +1217,7 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
             "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
             "version": "1.0",
             "authSpec": [...],
-            "encryptionSpecs": [...],
+            "encryption": [...],
             "targetSpec": { //describes the target connection parameters
                 "name": "User based target",
                 "type": "UserNamespace",
@@ -1428,7 +1428,7 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
             "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
             "version": "1.0",
             "authSpec": [...],
-            "encryptionSpecs": [...],
+            "encryption": [...],
             "targetSpec": { // describes the target connection parameters
                 "name": "User based target",
                 "type": "UserNamespace",
@@ -1628,7 +1628,7 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
             "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
             "version": "1.0",
             "authSpec": [...],
-            "encryptionSpecs": [...],
+            "encryption": [...],
             "targetSpec": { // describes the target connection parameters
                 "name": "User based target",
                 "type": "UserNamespace",
@@ -1818,11 +1818,11 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
         "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
         "version": "1.0",
         "authSpec": [],
-        "encryptionSpecs": [],
-            "targetSpec": { // describes the target connection parameters
-                "name": "User based target",
-                "type": "UserNamespace",
-                "spec": {
+        "encryption": [],
+        "targetSpec": { // describes the target connection parameters
+            "name": "User based target",
+            "type": "UserNamespace",
+            "spec": {
                     "$schema": "http://json-schema.org/draft-07/schema#",
                     "type": "object",
                     "properties": {
@@ -2009,7 +2009,7 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
             "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
             "version": "1.0",
             "authSpec": [...],
-            "encryptionSpecs": [...],
+            "encryption": [...],
             "targetSpec": { // describes the target connection parameters
                 "name": "User based target",
                 "type": "UserNamespace",
@@ -2208,7 +2208,7 @@ Note the highlighted lines with inline comments in the [!DNL connection spec] ex
             "providerId": "14e34fac-d307-11e9-bb65-2a2ae2dbcce4",
             "version": "1.0",
             "authSpec": [...],
-            "encryptionSpecs": [...],
+            "encryption": [...],
             "targetSpec": { // describes the target connection parameters
                 "name": "User based target",
                 "type": "UserNamespace",

help/destinations/api/update-destination-dataflows.md

@@ -752,6 +752,14 @@ The exported files contain the destination name, Experience Platform audience ID
 
 To add a profile attribute to the destination dataflow, perform a PATCH request to the [!DNL Flow Service] API while providing your flow ID, version, and the profile attribute you want to add.
 
+>[!IMPORTANT]
+>
+>**Destination-specific mapping requirements**
+>
+>The `profileSelectors` method described in this section works for most streaming destinations. However, some streaming destinations, including **Adobe Target**, require the Data Prep mapping set workflow instead. 
+>
+>**If your profile attributes do not appear in the Experience Platform UI after a successful API response (202)**, you must use the mapping set method documented in [Activate audiences to batch destinations](../api/activate-segments-file-based-destinations.md#attribute-and-identity-mapping).
+
 **API format**
 
 ```http

help/destinations/catalog/advertising/acxiom-real-id-audience-connection.md

@@ -1,16 +1,16 @@
 ---
-title: Acxiom Real ID™ Audience Connection
-description: Use the [!DNL Acxiom Real ID™ Audience Connection] destination to enhance audiences with [!DNL Acxiom's Real ID] technology and activate audiences to multiple platforms, such as [!DNL Altice], [!DNL Ampersand], [!DNL Comcast], and more.
+title: Acxiom Real ID Audience Connection
+description: Use the [!DNL Acxiom Real ID Audience Connection] destination to enhance audiences with [!DNL Acxiom's Real ID] technology and activate audiences to multiple platforms, such as [!DNL Altice], [!DNL Ampersand], [!DNL Comcast], and more.
 badge: label="Beta" type="Informative"
 exl-id: 5f1f0f7f-ac46-42bd-8002-be50fab5a76b
 ---
-# [!DNL Acxiom Real ID™ Audience Connection] destination 
+# [!DNL Acxiom Real ID Audience Connection] destination 
 
 >[!NOTE]
 >
->The [!DNL Acxiom Real ID™ Audience Connection] destination is in beta. This destination connector and documentation page are created and maintained by the [!DNL Acxiom] team. For any inquiries or update requests, contact Acxiom directly [here](mailto:[email protected]).
+>The [!DNL Acxiom Real ID Audience Connection] destination is in beta. This destination connector and documentation page are created and maintained by the [!DNL Acxiom] team. For any inquiries or update requests, contact Acxiom directly [here](mailto:[email protected]).
 
-Use the [!DNL Acxiom Real ID Audience Connection] destination to enhance audiences with [!DNL Acxiom's] [Real ID™](https://www.acxiom.com/real-id/real-id/) technology and activate audiences to multiple platforms, such as [!DNL Altice], [!DNL Ampersand], [!DNL Comcast], and more.
+Use the [!DNL Acxiom Real ID Audience Connection] destination to enhance audiences with [!DNL Acxiom's] [Real ID](https://www.acxiom.com/real-id/real-id/) technology and activate audiences to multiple platforms, such as [!DNL Altice], [!DNL Ampersand], [!DNL Comcast], and more.
 
 This tutorial provides instructions to create an [!DNL Acxiom Real ID Audience Connection] destination connector using the [!DNL Adobe Experience Platform] user interface. This connector is used to build and distribute audiences to selected destinations.
 

help/destinations/catalog/advertising/demandbase-people.md

@@ -96,14 +96,29 @@ Read [Activate profiles and audiences to streaming audience export destinations]
 
 ### Mandatory mappings {#mandatory-mappings}
 
-When activating audiences to the [!DNL Demandbase People] destination, you must configure the following mandatory field mappings in the mapping step:
+When activating audiences to the [!DNL Demandbase People] destination, you must configure the following mandatory field mapping in the mapping step:
+
+| Source field | Target field | Description |
+|--------------|--------------|-------------|
+| `xdm: workEmail.address` | `Identity: email` | The work email address of the person |
+
+### Recommended mappings {#recommended-mappings}
+
+For optimal matching accuracy, include the following optional mappings in your activation flow, in addition to the [mandatory mapping](#mandatory-mappings) above.
 
 | Source field | Target field | Description |
 |--------------|--------------|-------------|
 | `xdm: b2b.personKey.sourceKey` | `xdm: externalPersonId` | The unique identifier for the person |
 | `xdm: person.name.lastName` | `xdm: lastName` | The last name of the person |
 | `xdm: person.name.firstName` | `xdm: firstName` | The first name of the person |
-| `xdm: workEmail.address` | `Identity: email` | The work email address of the person |
+
+### Mapping best practices {#mapping-best-practices}
+
+When mapping fields to [!DNL Demandbase People], consider the following matching behavior:
+
+* **Primary matching**: If `externalPersonId` is present, Demandbase uses it as the primary identifier for person matching.
+* **Fallback matching**: If `externalPersonId` is not available, Demandbase uses the `email` field for identification.
+* **Required vs. recommended**: While only `email` is required by Demandbase, Adobe recommends mapping all available fields from the recommended mappings table above, to improve matching accuracy and campaign performance.
 
 ![Demandbase People mappings](/help/destinations/assets/catalog/advertising/demandbase-people/demandbase-people-mapping.png)
 
@@ -114,4 +129,4 @@ These mappings are required for the destination to function properly and must be
 * **Demandbase API guardrails**: If you have exported audiences to Demandbase and the exports are successful in Experience Platform, yet not all of the data reaches Demandbase, you might have encountered API throttling on the Demandbase side. Reach out to them for clarification.
 * **List deletion**: People lists are unique, so you cannot re-create a new list with a name already in use. When you remove people from a list, they will no longer be available, but they will not be deleted.
 * **Activation time**: Data loading in Demandbase is subject to overnight processing.
-* **Audience naming**: If an account audience with the same name was activated earlier to Demandbase, you cannot activate it again through a different dataflow to the Demandbase destination.
+* **Audience naming**: If a people audience with the same name was activated earlier to Demandbase, you cannot activate it again through a different dataflow to the Demandbase destination.

help/destinations/catalog/advertising/demandbase.md

@@ -104,5 +104,7 @@ These mappings are required for the destination to function properly and must be
 
 ## Additional notes and important callouts {#additional-notes}
 
-* If an account audience with the same name was activated earlier to Demandbase, you cannot activate it again through a different dataflow to the Demandbase destination.
-* If you have exported audiences to Demandbase and the exports are successful in Experience Platform, yet not all of the data reaches Demandbase, you might have encountered API throttling on the Demandbase side. Reach out to them for clarification.
+* **Audience naming**: If an account audience with the same name was activated earlier to Demandbase, you cannot activate it again through a different dataflow to the Demandbase destination.
+* **Demandbase API guardrails**: If you have exported audiences to Demandbase and the exports are successful in Experience Platform, yet not all of the data reaches Demandbase, you might have encountered API throttling on the Demandbase side. Reach out to them for clarification.
+* **List deletion**: Account lists are unique, so you cannot re-create a new list with a name already in use. When you remove accounts from a list, they will no longer be available, but they will not be deleted.
+* **Activation time**: Data loading in Demandbase is subject to overnight processing.

help/destinations/catalog/advertising/tradedesk.md

@@ -44,10 +44,10 @@ All identities in the table below are mandatory mappings.
 
 |Target identity|Description|Considerations|
 |---|---|---|
-|GAID|Google Advertising ID|Select the GAID target identity when your source identity is a GAID namespace.|
-|IDFA|Apple ID for Advertisers|Select the IDFA target identity when your source identity is an IDFA namespace.|
-|ECID|Experience Cloud ID|This identity is mandatory for the integration to work correctly but is not used for audience activation.|
-|The Trade Desk ID|Advertiser ID in the [!DNL The Trade Desk] platform|Use this identity when activating audiences based on The Trade Desk's proprietary ID.|
+|[!DNL GAID]|Google Advertising ID|Select the GAID target identity when your source identity is a GAID namespace.|
+|[!DNL IDFA]|Apple ID for Advertisers|Select the IDFA target identity when your source identity is an IDFA namespace.|
+|[!DNL ECID]|Experience Cloud ID|This identity is mandatory for the integration to work correctly but is not used for audience activation.|
+| [!DNL Tradedesk] |[!DNL TDID] in the [!DNL The Trade Desk] platform|Use this identity when activating audiences based on The Trade Desk's proprietary ID.|
 
 {style="table-layout:auto"}
 

help/destinations/catalog/personalization/custom-personalization.md

@@ -35,6 +35,12 @@ This destination requires the use of one of the following data collection method
 * Use the [Adobe Experience Platform Mobile SDK](https://developer.adobe.com/client-sdks/documentation/) if you want to collect data from your mobile application.
 * Use the [Edge Network API](https://developer.adobe.com/data-collection-apis/docs/) if you are not using [Web SDK](/help/web-sdk/home.md) or [Mobile SDK](https://developer.adobe.com/client-sdks/documentation/), or if you want to personalize the user experience based on profile attributes.
 
+>[!IMPORTANT]
+>
+>**Attribute-based personalization requirements:** If you want to personalize based on profile attributes (not just audience membership), you **must** use the [Edge Network API](https://developer.adobe.com/data-collection-apis/docs/) with authenticated server-side integration, regardless of whether you are also using Web SDK or Mobile SDK for data collection.
+>
+>Web SDK and Mobile SDK alone only support personalization based on audience membership. The Edge Network API is **required** to securely retrieve profile attributes for personalization.
+
 >[!IMPORTANT]
 >
 >Before creating a custom personalization connection, read the guide on how to [activate audience data to edge personalization destinations](../../ui/activate-edge-personalization-destinations.md). This guide takes you through the required configuration steps for same-page and next-page personalization use cases, across multiple Experience Platform components.