Making a connection to Adobe allows the necessary configuration to be set up so that postbacks can then be sent from EMMA to Adobe with the relevant information.
Remember that the postbacks that are sent to Adobe are only and exclusively those that are configured in the Customer journey flows and will be sent based on the configuration made in this integration set up.
To connect to Adobe, just follow these steps:
- Go to the section Management > Integrations..
- Add the Adobe specific integration and fill in the connection form. It is Adobe itself that must provide the necessary information to make this connection. In this case the configuration is divided into 3 sections:
¶ Authentication
The fields to be configured in this Authentication section are:
- Authentication URL
- Client ID
- Client Secret
- PKEY Certificate
¶ Integration parameters
The fields to be configured in this Integration parameters section are:
- imsHost
- imsOrgId
- techId
- metaScopes
¶ Requests configuration
- API URL
- Body scheme: The scheme parameters shall have the format {{parameterName}}. Known parameters will be replaced automatically, while the rest of the parameters will appear as variables in the configuration of each postback. Each client has a different message body, this data is provided by Adobe. An example of such a message body would be:
{
"header": {
"schemaRef": {
"id": "<<SCHEMA ENDPOINT>>",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
},
"imsOrgId": "<<IMS ORG ID ADDED IN CONFIG>>",
"source": {
"name": "<<SOURCE CODE NAME>>"
},
"datasetId": "<<DATA_SET_ID>>"
},
"body": {
"xdmMeta": {
"schemaRef": {
"id": "<<SCHEMA URL ENDPOINT>>",
"contentType": "application/vnd.adobe.xed-full+json;version=1.0"
}
},
"xdmEntity": {"model_name":{"my_company":{"campaignId":{{campaignId}},"campaignType":"{{campaignType}}","interactionResult":"{{interactionResult}}","interactionType":"{{interactionType}}"},"identification":{"id":"{{customerId}}"}},"_id":"{{uuidV4}}","eventMergeId":"Sample value","eventType":"emma.notification","producedBy":"self","timestamp":"{{isoDate}}"}
}
}
Note that fields containing <<>> mean that they are dynamic data and have to be replaced in the message body.
The content within the xdmEntity depends on the data model that is configured in the Adobe platform, this is simply an example used to show what the message body would look like.
Any field within the message body that is set to {{}} and does not fall within the EMMA default parameters, will exit as a fillable option when configured in a postback action in Customer Journeys. All EMMA default parameters are overridden when sending postback.
In this guide you can see more info about how to configure postbacks in the routes to notify Adobe and the parameters that can be collected.