When creating an event, Journey Orchestration automatically generates an ID for this event. The system pushing the event should not generate an ID, it should use the one available in the payload preview. See this page.
To configure events to be sent to Streaming Ingestion APIs and to be used in Journey Orchestration, you need to follow these steps:
You then need to configure the data system that pushes events to Streaming Ingestion APIs using the payload you copied:
Here is an example of a Streaming Ingestion APIs event:
{
"header": {
"msgType": "xdmEntityCreate",
"msgId": "c25585b9-252e-431d-b562-e73da70c04e7",
"msgVersion": "1.0",
"xactionId": "f5995abe-c49d-4848-9577-a7a4fc2996fb",
"datasetId": "string - required if you want the data to land in a specific dataset - not mandatory",
"imsOrgId": "XXX@AdobeOrg",
"schemaRef": {
"id": "XXX",
"contentType": "application/vnd.adobe.xed-full+json;version=1"
},
"source": {
"name": "Journeys"
}
},
"body": {
"xdmMeta": {
"schemaRef": {
"id": "XXX",
"contentType": "application/vnd.adobe.xed-full+json;version=1"
}
},
"xdmEntity": {
"_instance_name": {
"person": {
"firstName": "string",
"lastName": "string",
"gender": "string",
"birthYear": 10,
"emailAddress": "string"
}
},
"identityMap": {
"Email": [
{
"id": "string"
}
]
},
"_id": "string",
"timestamp": "2018-05-29T00:00:00.000Z",
"_experience": {
"campaign": {
"orchestration": {
"eventID": "XXX"
}
}
}
}
}
}
To facilitate the identification of the place where to paste the “data” part, you can use a JSON visualization tool such as https://jsonformatter.curiousconcept.com
To troubleshoot Streaming Ingestion APIs, refer to this page.