In this exercise, you’ll create two custom actions by making use of Adobe Journey Optimizer in combination.
Login to Adobe Journey Optimizer by going to Adobe Experience Cloud. Click Journey Optimizer.
You’ll be redirected to the Home view in Journey Optimizer.
First, make sure you’re using the correct sandbox. The sandbox to use is called --aepSandboxId--
. To change from one sandbox to another, click on PRODUCTION Prod (VA7) and select the sandbox from the list. In this example, the sandbox is named AEP Enablement FY21.
You’ll then be in the Home view of your sandbox --aepSandboxId--
.
In the left menu, scroll down and click Configurations. Next, click the Manage button under Actions.
You’ll then see the Actions list.
You’ll define two actions:
Twilio is a 3rd party provider of SMS Messages. It has an easy-to-use API and we’ll use Adobe Journey Optimizer to trigger their API.
Click Create Action to start adding your action.
You’ll see an empty Action popup.
As a Name for the Action, use ldapSmsTwilio
and replace Ldap
with your LDAP. In this example, the Action Name is joconnorSmsTwilio
.
Set Description to: Send SMS using Twilio
.
For the URL Configuration, use this:
https://l1uikl5kog.execute-api.us-west-2.amazonaws.com/prod/
You don’t need to change the Header Fields.
For transparency, we’re using an AWS API Gateway and AWS Lambda function that sits behind the above URL to handle the authentication and sending of SMSs to Twilio.
Authentication should be set to No Authentication.
For the Action Parameters, you need to define which fields should be sent towards Twilio. Logically, we want Adobe Journey Optimizer and Adobe Experience Platform to be the brain of personalization, so the SMS Message Text and the Mobile Number to send the SMS towards should be defined by Adobe Journey Optimizer and then sent to Twilio for execution.
So for the Action Parameters, click the Edit Payload icon.
You’ll then see an empty popup-window.
Copy the below text and paste it in the empty popup-window.
{
"body": {
"textMessage": {
"toBeMapped": true,
"dataType": "string",
"label": "textMessage"
},
"to": {
"toBeMapped": true,
"dataType": "string",
"label": "mobileNr"
}
}
}
FYI: by specifying the below fields, these fields will become accessible from your Customer Journey and you’ll be able to populate them dynamically from the Journey:
“toBeMapped”: true,
“dataType”: “string”,
“label”: “textMessage” and mobileNr
You’ll then see this:
Click Save.
Scroll up and click Save one more time to save your custom Action.
Your custom Action is now part of the Actions list.
Let’s define your second action now.
We’ll now use an existing Slack Channel and send messages to that Slack Channel. Slack has an easy-to-use API and we’ll use Adobe Journey Optimizer to trigger their API.
Click Create Action to start adding a new action.
You’ll see an empty Action popup.
As a Name for the Action, use ldapTextSlack
and replace ldap
with your LDAP. In this example, the Action Name is joconnorTextSlack
.
Set Description to: Send Text to Slack
.
For the URL Configuration, use this:
https://2mnbfjyrre.execute-api.us-west-2.amazonaws.com/prod
The above URL refers to an AWS Lambda function which will then forward your request to the Slack channel as mentioned above. This is done to protect access to an Adobe-owned Slack channel. If you have your own Slack channel, you should create a Slack App through https://api.slack.com/, you then need to create an Incoming Webhook in that Slack App, and then replace the above URL by your Incoming Webhook URL.
You don’t need to change the Header Fields.
Authentication should be set to No Authentication.
For the Action Parameters, you need to define which fields should be sent towards Slack. Logically, we want Adobe Journey Optimizer and Adobe Experience Platform to be the brain of personalization, so the text to send to Slack should be defined by Adobe Journey Optimizer and then sent to Slack for execution.
So for the Action Parameters, click the Edit Payload icon.
You’ll then see an empty popup-window.
Copy the below text and paste it in the empty popup window.
{
"text": {
"toBeMapped": true,
"dataType": "string",
"label": "textToSlack"
}
}
FYI: by specifying the below fields, these fields will become accessible from your Customer Journey and you’ll be able to populate them dynamically from the Journey:
“toBeMapped”: true,
“dataType”: “string”,
“label”: “textToSlack”
You’ll then see this:
Click Save.
Scroll up and click Save one more time to save your custom Action.
Your custom Action is now part of the Actions list.
You’ve defined events, an external data sources and actions. Now let’s consolidate all of that in one journey.
Next Step: 12.4 Design a trigger-based journey