Skip to content

Commit 873aee3

Browse files
vladfalonGitHub Enterprise
authored andcommitted
Merge pull request #6558 from AdobeDocs/PLAT-255820-Update-Destination-Mapping-API-Documentation-Clarify-Batch-Method-Requirement-for-Streaming-Destinations
PLAT-255820-Update Destination Mapping API Documentation: Clarify Batch Method Requirement for Streaming Destinations
2 parents 26002d8 + 7f8fbbe commit 873aee3

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

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

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -752,6 +752,14 @@ The exported files contain the destination name, Experience Platform audience ID
752752

753753
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.
754754

755+
>[!IMPORTANT]
756+
>
757+
>**Destination-specific mapping requirements**
758+
>
759+
>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.
760+
>
761+
>**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).
762+
755763
**API format**
756764

757765
```http

0 commit comments

Comments
 (0)