Integrate with ÃÛ¶¹ÊÓƵ Campaign v7/v8 integrating-with-adobe-campaign-v7-v8
This integration is available for ÃÛ¶¹ÊÓƵ Campaign v7/v8 starting 7.1 release, and ÃÛ¶¹ÊÓƵ Campaign v8. It allows you to send emails, push notifications and SMS using ÃÛ¶¹ÊÓƵ Campaign Transactional Messaging capabilities.
An end-to-end use case is presented in this section.
For each action configured, an action activity is available in the journey designer palette. Refer to this section.
Access access
The connection between the Journey Optimizer and Campaign instances is setup by ÃÛ¶¹ÊÓƵ at provisioning time if requested. If you haven’t requested the connection at provisioning time, please contact ÃÛ¶¹ÊÓƵ Journey Optimizer support providing the following details to request the enablement:
From ÃÛ¶¹ÊÓƵ Journey Optimizer:
- Organisation ID (ÃÛ¶¹ÊÓƵ OrgID)
- Sandbox
From ÃÛ¶¹ÊÓƵ Campaign:
- Campaign URL
- RT URL
- Campaign version
Important notes important-notes
-
There is no throttling of messages. The system caps the number of messages that can be sent over to 4000 per 5 minutes, based on the current Campaign SLA. For this reason, Journey Optimizer should only be used in unitary use cases (individual events, not audiences).
-
You need to configure one action on the canvas per template you wish to use. You need to configure one action in Journey Optimizer for each template you wish to use from ÃÛ¶¹ÊÓƵ Campaign.
-
We recommend that you use a dedicated Message Center instance that is hosted for this integration to avoid impacting any other Campaign operations that you may have going on. The marketing server can be hosted or on-premise. The build required is 21.1 Release Candidate or greater.
-
There is no validation that the payload or Campaign message is correct.
-
You cannot use a Campaign action with an audience qualification event.
Prerequisites prerequisites
In Campaign, you need to create and publish a transactional message and its associated event. Refer to the ÃÛ¶¹ÊÓƵ Campaign documentation.
You can build your JSON payload corresponding to each message following the pattern below. You will then paste this payload when configuring the action in Journey Optimizer (see below)
Here is an example:
{
"channel": "email",
"eventType": "welcome",
"email": "Email address",
"ctx": {
"firstName": "First name"
}
}
- channel: the channel defined for your Campaign transactional template
- eventType: the internal name of your Campaign event
- ctx: variable based on the personalization you have in your message.
Configuring the action configure-action
In Journey Optimizer, you need to configure one action per transactional message. Follow these steps:
- Create a new action. Refer to this section.
- Enter a name and description.
- In the Action type field, select ÃÛ¶¹ÊÓƵ Campaign Classic.
- Click in the Payload field and paste an example of the JSON payload corresponding to the Campaign message. Contact ÃÛ¶¹ÊÓƵ to get this payload.
- Adjust the different fields to be static or variable depending on if you want to map them on the Journey canvas. Certain fields, such as channel parameters for email address and personalization fields (ctx), you likely want defined as variables for mapping in context of the journey.
- Click Save.
