The HTTP destination in Platform is currently in alpha. The documentation and the functionality are subject to change.
The HTTP destination is an Adobe Experience Platform streaming destination that helps you send profile data to third-party HTTP endpoints.
To send profile data to HTTP endpoints, you must first connect to the destination in Adobe Experience Platform.
The HTTP destination is targeted towards customers who need to export XDM profile data and audience segments to generic HTTP endpoints.
HTTP endpoints can be either customers’ own systems or third-party solutions.
In Connections > Destinations, select HTTP API, and select Configure.
If a connection with this destination already exists, you can see an Activate button on the destination card. For more information about the difference between Activate and Configure, refer to the Catalog section of the destination workspace documentation.
In the Account step, you need to define the HTTP endpoint connection details. Select New account and enter the connection details for the HTTP endpoint that you want to connect to.
Only OAuth2 client credentials are currently supported.
Click Connect to destination. After the connection succeeds, click Next.
In the Authentication step, enter the account authentication credentials:
header1:value1,header2:value2,...headerN:valueN
.The current implementation requires at least one custom header. This limitation will be resolved in a future update.
Marketing action: Marketing actions indicate the intent for which data will be exported to the destination. You can select from Adobe-defined marketing actions or you can create your own marketing action. For more information about marketing actions, see the Data usage policies overview.
Click Create destination.
See Activate profiles and segments to a destination for information about the segment activation workflow.
During the Select attributes step, when activating segments to an HTTP destination, we recommend that you select a unique identifier from your union schema. Select the unique identifier and any other XDM fields that you want to export to the destination.
Your exported Experience Platform data lands in your HTTP destination in JSON format. For example, the event below contains the email address profile attribute of an audience that has qualified for a certain segment and exited another segment. The identities for this prospect are ECID and email.
{
"person": {
"email": "yourstruly@adobe.con"
},
"segmentMembership": {
"ups": {
"7841ba61-23c1-4bb3-a495-00d3g5fe1e93": {
"lastQualificationTime": "2020-05-25T21:24:39Z",
"status": "exited"
},
"59bd2fkd-3c48-4b18-bf56-4f5c5e6967ae": {
"lastQualificationTime": "2020-05-25T23:37:33Z",
"status": "existing"
}
}
},
"identityMap": {
"ecid": [
{
"id": "14575006536349286404619648085736425115"
},
{
"id": "66478888669296734530114754794777368480"
}
],
"email_lc_sha256": [
{
"id": "655332b5fa2aea4498bf7a290cff017cb4"
},
{
"id": "66baf76ef9de8b42df8903f00e0e3dc0b7"
}
]
}
}