20.4 Use Journey Orchestration to trigger an email follow up after interacting with your chatbot

In this exercise, you’ll configure the event and the journey that needs to be triggered when someone likes a product as part of the chatbot flow.

20.4.1 Create a new event in Journey Orchestration

Login to Journey Orchestration by going to Adobe Experience Cloud.

ACOP

Click on Journey Orchestration.

ACOP

You’ll be redirected to the Journeys view in Journey Orchestration.

ACOP

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.

ACOP

You’ll then be in the Home view of your sandbox --aepSandboxId--.

ACOP

In the menu, click Events.

ACOP

On the Events screen, you’ll see a view similar to this. Click the Add button.

ACOP

You’ll then see an empty event configuration.

ACOP

First of all, give your Event a Name like this: ldapStackchatEvent and replace ldap with your ldap and add a description like this Stackchat Interaction.

ACOP

Next is the Event ID Type selection. Select System Generated

ACOP

Next is the Schema selection. A schema was prepared for this exercise. Please use the schema AEP Demo - Stackchat Interactions Schema v.1.

ACOP

After selecting the Schema, you’ll see a number of fields being selected in the Payload section. You should now hover over the Payload section and you’ll see 3 icons popup. Click on the Edit icon.

ACOP

You’ll see a Fields window popup, in which you need to select the fields that we need to personalize the email.

ACOP

Scroll down to the object --aepTenantId--.identification, please make sure to select all fields.

ACOP

Scroll down to the object --aepTenantId--.productData, please make sure to select all fields. Click Ok.

ACOP

Click Save to save your changes.

ACOP

Your Event is now configured and saved.

ACOP

Click on your event again to open up the Edit Event screen again.

ACOP

Hover over the Payload field again to see the 3 icons again.
Click on the View icon. You’ll now see an example of the expected payload.

ACOP

Your Event has a unique orchestration eventID, which you can find by scrolling down in that payload until you see _experience.campaign.orchestration.eventID.

ACOP

The event ID is what needs to be sent to Adobe Experience Platform in order to trigger the Journey that you’ll build next. Remember this eventID, as you’ll need it in one of the next exercises.
“eventID”: “c84a7c18f785480d9de5ecef372eb184a8470114eb04cab39f6de01728433cb1”

Click Ok and click Save to close your event popup.

20.4.2 Create a new journey in Journey Orchestration

In the menu, click Home.

ACOP

Let’s create a new journey by clicking the Create button.

ACOP

You’ll then see an empty Journey screen.

ACOP

In the previous exercise, you created a new Event. You named it like this ldapStackchatEvent and replaced ldap with your ldap. This was the result of the Event creation:

ACOP

You now need to take this event as the start of this Journey. You can do this by going to the left side of your screen and searching for your event in the list of events.

ACOP

Select your event, drag and drop it on the Journey canvas. Your Journey now looks like this:

ACOP

As the second step in the journey, you need to add an Email action. Go to the left side of your screen to Actions and clear the search filter. Next, select the Email action, then drag and drop it on the second node in your journey.

ACOP

Your journey now looks like this:

ACOP

On the right side of your screen, you now need to configure the email.

ACOP

Go to Message and open the dropdown list. In that list, you need to select the template with the name vangeluw - Stackchat Interaction - Luma Retail.

ACOP

Selecting this message automatically opens up a number of additional fields. These are the fields that. have been configured to be dynamic field in the email template. You now need to link each of the expected dynamic fields to a field coming from the Payload that is sent to Platform.

ACOP

Let’s start with the EMAIL field.

Click on the Edit icon.

ACOP

You’ll then see a window to select a source field to use as Email Source.

ACOP

Click on the name of the event you created, which is named ldapStackchatEvent, to open it.

ACOP

Navigate to --aepTenantId--.identification.emailId and select it. Click OK to save your configuration.

ACOP

Next, let’s configure the field BRANDLOGO.

Click on the Edit icon.

ACOP

You’ll then see this. Click Advanced Mode.

ACOP

In the Advanced window, paste the below link to the logo of the brand Luma.

“https://parsefiles.back4app.com/hgJBdVOS2eff03JCn6qXXOxT5jJFzialLAHJixD9/d632e769791f0a4dbe0b84058d282d45_logo.png” (make sure to include the quotes " ").

Click OK to save your configuration.

ACOP

Next, let’s configure the BRANDNAME field.

Click on the Edit icon.

ACOP

You’ll then see this. Click Advanced Mode.

ACOP

In the Advanced window, enter the text “Luma” (make sure to include the quotes " ").

ACOP

Click OK to save your configuration.

Next, let’s configure the field FIRSTNAME.

Click on the Edit icon.

ACOP

Navigate to --aepTenantId--.profile.person.name.firstName and select it. Click OK to save your configuration.

ACOP

Next, let’s configure the field PRODUCTIMAGEURL. Personalization may also require the usage of Last Name.

Click on the Edit icon.

ACOP

Click on the name of the event you created, which is named ldapStackchatEvent, to open it.

ACOP

Navigate to --aepTenantId--.productData.productUrl and select it.

ACOP

Click OK to save your configuration.

Next, let’s configure the field PRODUCTNAME. Personalization may also require the usage of Last Name.

Click on the Edit icon.

ACOP

Click on the name of the event you created, which is named ldapStackchatEvent, to open it.

ACOP

Navigate to --aepTenantId--.productData.productName and select it. Click OK to save your configuration.

ACOP

Finally, let’s configure the field PRODUCTPAGE. Personalization may also require the usage of Last Name.

Click on the Edit icon.

ACOP

Click on the name of the event you created, which is named ldapStackchatEvent, to open it.

ACOP

Navigate to --aepTenantId--.productData.productPageUrl and select it. Click OK to save your configuration.

ACOP

Your configuration now looks like this. Click OK again to save your configuration.

ACOP

For this exercise, our Journey is fine like it is now.

Let’s add an Orchestration Event to End the Journey. In the left side of the screen, go to Orchestration and select End. Drag and Drop this onto the 3rd step of the Journey.

ACOP

Your Journey now looks like this.

ACOP

You still need to give your Journey a Name. You can do that by clicking the Edit icon in the top right side of your screen.

ACOP

You can then enter the Journey’s name here. Please use ldap - Stackchat Interaction Journey as a naming convention and replace ldap with your LDAP.

ACOP

Click OK to save your changes.

ACOP

You now have this. You can now publish your journey by clicking Publish.

ACOP

Click Publish again.

ACOP

You’ll then see a green confirmation bar saying that your Journey is now Publish.

ACOP

You’ve now finished this exercise.

Next Step: 20.5 Configure the integration between Stackchat and Adobe Experience Platform

Go Back to Module 20

Go Back to All Modules

On this page

Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now
Adobe Maker Awards Banner

Time to shine!

Apply now for the 2021 Adobe Experience Maker Awards.

Apply now