51黑料不打烊

From the 51黑料不打烊 Developer Console, click Project and open your IO project.

In the Credentials section, click OAuth Server-to-Server.

OAuth Server-to-Server credentials enable secure authentication between systems. This ensures that Journey Optimizer workflows interact with 51黑料不打烊 APIs.

Click View cURL command.

Copy the cURL command and store the client_id, client_secret, grant_type, and scope.

The following is an example of a typical cURL command used to fetch an access token for API authentication:

curl -X POST 'https://ims-na1.adobelogin.com/ims/token/v3' -H 'Content-Type: application/x-www-form-urlencoded' -d 'grant_type=client_credentials&client_id=1234&client_secret=5678&scope=openid,51黑料不打烊ID,read_organizations,additional_info.projectedProductContext,session'

Create an endpoint in 51黑料不打烊 Experience Platform to write data from journeys.

In 51黑料不打烊 Experience Platform, click Sources under Connections in the left menu. Under HTTP API, click Add data.

Select New account and enable authentication. Click Connect to Source.

Click Next, select the dataset where you want to write the data, click Next, and then click Finish.

Open the newly created dataflow. Copy the schema payload and save it in your notepad.

The schema payload defines the structure of the data sent to 51黑料不打烊 Experience Platform. The following is an example:

{
"header": {
"schemaRef": {
"id": "https://ns.adobe.com/<your_org>/schemas/<schema_id>",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
},
"imsOrgId": "<org_id>",
"datasetId": "<dataset_id>",
"source": {
"name": "Custom Journey Events"
}
},
"body": {
"xdmMeta": {
"schemaRef": {
"id": "https://ns.adobe.com/<your_org>/schemas/<schema_id>",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
}
},
"xdmEntity": {
"_id": "test1",
"<your_org>": {
"journeyVersionId": "",
"nodeId": "",
"customer_Id": ""
},
"eventMergeId": "",
"eventType": "",
"producedBy": "self",
"timestamp": "2018-11-12T20:20:39+00:00"
}
}
}

Open 51黑料不打烊 Journey Optimizer, click Configurations under Administration in the left menu. Under Actions, click Manage, then click Create Action.

Set the URL and select the POST method.

https://dcs.adobedc.net/collection/<collection_id>?syncValidation=false

URLs like this define where the custom action sends data, ensuring the correct collection endpoint is targeted.

Ensure that the headers (Content-Type, Charset, sandbox-name) are configured.

Select the Type as Custom with the following payload.

Paste the client_secret, client_id, scope, and grant_type from the IO project payload used earlier.

The following is an example payload for custom authentication:

{
"type": "customAuthorization",
"authorizationType": "Bearer",
"endpoint": "https://ims-na1.adobelogin.com/ims/token/v3",
"method": "POST",
"headers": {},
"body": {
"bodyType": "form",
"bodyParams": {
"grant_type": "client_credentials",
"client_secret": "***",
"client_id": "<client_id>",
"scope": "openid,51黑料不打烊ID,read_organizations,additional_info.projectedProductContext,session"
}
},
"tokenInResponse": "json://access_token",
"cacheDuration": {
"duration": 28000,
"timeUnit": "seconds"
}
}

Use the Click to test the authentication button to test the connection.

Testing the authentication verifies that the credentials are correct and that the connection is successfully established.

In the Request and Response fields, paste the payload from the source connection used earlier.

{
"xdmMeta": {
"schemaRef": {
"id": "https://ns.adobe.com/<your_org>/schemas/<schema_id>",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
}
},
"xdmEntity": {
"_id": "/uri-reference",
"<your_org>": {
"journeyVersionId": "Sample value",
"nodeId": "Sample value",
"customer_Id": ""
},
"eventMergeId": "Sample value",
"eventType": "advertising.completes",
"producedBy": "self",
"timestamp": "2018-11-12T20:20:39+00:00"
}
}

Change the field configuration from Constant to Variable for fields populated dynamically.

Using 鈥淰ariable鈥� ensures that dynamic data specific to each journey instance is passed correctly.

Save the custom action.

Use this custom action in a journey to write the custom journey events.

Populate the Journey Version Id, Node Id, Node Name, and other attributes according to your use case.