🍎
Comprehensive Technical Tutorial for AEP
  • Comprehensive Technical Tutorial for Adobe Experience Platform
    • Architecture
    • Video Overview
  • 0 - Getting started
    • 0.0 Which environment do I use?
    • (Deprecated) Install the Chrome extension for the Experience League documentation
    • 0.1 Use Demo System Next to setup your Adobe Experience Platform Data Collection client property
    • 0.2 Create your Datastream
    • 0.3 Set up the website
    • 0.4 Set up the mobile app
    • 0.5 Ingest Data to AEP through the Website
    • 0.6 Ingest Data to AEP through the Mobile App
    • 0.7 Visualize your own Real-time Customer Profile - UI
    • 0.8 See your Real-time Customer Profile in action in the Call Center
    • 0.9 Set up and use the AEP API to visualize your Real-Time Customer Profile
    • 0.10 Install the Experience Platform Debugger Extension
    • 0.11 What if I want to demonstrate basic AEP concepts directly on a live website?
  • 1 - Adobe Experience Platform Data Collection and the Web SDK extension
    • 1.1 Understanding Adobe Experience Platform Data Collection
    • 1.2 Edge Network, Datastreams and Server Side Data Collection
    • 1.3 Introduction to Adobe Experience Platform Data Collection
    • 1.4 Client-side Web Data Collection
    • 1.5 Implement Adobe Analytics and Adobe Audience Manager
    • 1.6 Implement Adobe Target
    • 1.7 XDM Schema requirements in Adobe Experience Platform
    • Summary and Benefits
  • 2 - Data Ingestion
    • 2.1 Explore the Website
    • 2.2 Configure Schemas and Set Identifiers
    • 2.3 Configure Datasets
    • 2.4 Data Ingestion from Offline Sources
    • 2.5 Data Landing Zone
    • Summary and Benefits
  • 3 - Real-time Customer Profile
    • 3.1 Visit the website
    • 3.2 Visualize your own real-time customer profile - UI
    • 3.3 Visualize your own real-time customer profile - API
    • 3.4 Create a segment - UI
    • 3.5 Create a segment - API
    • 3.6 See your Real-time Customer Profile in action in the Call Center
    • Summary and benefits
  • 4 - Query Service
    • 4.0 Prerequisites
    • 4.1 Getting Started
    • 4.2 Using the Query Service
    • 4.3 Queries, queries, queries... and churn analysis
    • 4.4 Generate a dataset from a query
    • 4.5 Query Service and Power BI
    • 4.6 Query Service and Tableau
    • 4.7 Query Service API
    • Summary and benefits
  • 5 - Intelligent Services
    • 5.1 Customer AI - Data Preparation (Ingest)
    • 5.2 Customer AI - Create a New Instance (Configure)
    • 5.3 Customer AI - Scoring Dashboard and Segmentation (Predict & Take Action)
  • 6 - Real-time CDP - Build a segment and take action
    • 6.1 Create a segment
    • 6.2 Review how to configure DV360 Destination using Destinations
    • 6.3 Take Action: send your segment to DV360
    • 6.4 Take Action: send your segment to an S3-destination
    • 6.5 Take Action: send your segment to Adobe Target
    • 6.6 External Audiences
    • 6.7 Destinations SDK
    • Summary and benefits
  • 7 - Adobe Journey Optimizer: Orchestration
    • 7.1 Create your event
    • 7.2 Create your journey and email message
    • 7.3 Update your Data Collection property and test your journey
    • Summary and benefits
  • 8 - Adobe Journey Optimizer: External data sources and custom actions
    • 8.1 Define an event
    • 8.2 Define an external data source
    • 8.3 Define a custom action
    • 8.4 Create your journey and messages
    • 8.5 Trigger your journey
    • Summary and benefits
  • 9 - Adobe Journey Optimizer: Offer Decisioning
    • 9.1 Offer Decisioning 101
    • 9.2 Configure your offers and decision
    • 9.3 Prepare your Data Collection Client property and Web SDK setup for Offer Decisioning
    • 9.4 Combine Adobe Target and Offer Decisioning
    • 9.5 Use your decision in an email
    • 9.6 Test your decision using the API
    • Summary and benefits
  • 10 - Adobe Journey Optimizer: Event-based Journeys
    • 10.1 Configure an event-based journey - Order Confirmation
    • 10.2 Configure a batch-based newsletter journey
    • 10.3 Apply personalization in an email message
    • 10.4 Setup and use push notifications
    • 10.5 Create a business event journey
    • Summary and benefits
  • 11 - Customer Journey Analytics - Build a dashboard using Analysis Workspace on top of Adobe Experie
    • 11.1 Customer Journey Analytics 101
    • 11.2 Connect Adobe Experience Platform Data Sets in Customer Journey Analytics
    • 11.3 Create a Data View
    • 11.4 Data Preparation in Customer Journey Analytics
    • 11.5 Visualization using Customer Journey Analytics
    • Summary and benefits
  • 12 - Ingest & Analyze Google Analytics data in Adobe Experience Platform with the BigQuery Source Co
    • 12.1 Create your Google Cloud Platform Account
    • 12.2 Create your first query in BigQuery
    • 12.3 Connect GCP & BigQuery to Adobe Experience Platform
    • 12.4 Load data from BigQuery into Adobe Experience Platform
    • 12.5 Analyze Google Analytics Data using Customer Journey Analytics
    • Summary and benefits
  • 13 - Real-Time CDP: Segment Activation to Microsoft Azure Event Hub
    • 13.1 Configure your Microsoft Azure EventHub environment
    • 13.2 Configure your Azure Event Hub Destination in Adobe Experience Platform
    • 13.3 Create a segment
    • 13.4 Activate segment
    • 13.5 Create your Microsoft Azure Project
    • 13.6 End-to-end scenario
    • Summary and benefits
  • 14 - Real-Time CDP Connections: Event Forwarding
    • 14.1 Create a Data Collection Event Forwarding property
    • 14.2 Update your Datastream to make data available to your Data Collection Event Forwarding property
    • 14.3 Create and configure a custom webhook
    • 14.4 Create and configure a Google Cloud Function
    • 14.5 Forward events towards the AWS ecosystem
    • Summary and benefits
  • 15 - Stream data from Apache Kafka into Adobe Experience Platform
    • 15.1 Introduction to Apache Kafka
    • 15.2 Install and configure your Kafka cluster
    • 15.3 Configure HTTP API Streaming endpoint in Adobe Experience Platform
    • 15.4 Install and configure Kafka Connect and the Adobe Experience Platform Sink Connector
    • Summary and benefits
Powered by GitBook
On this page
  • 8.4.1 Create your journey
  • Condition 1: Colder than 10° Celsius
  • Condition 2: Between 10° and 25° Celsius
  • Condition 3: Warmer than 25° Celsius
  • 8.4.2 Send messages for path: Colder than 10° Celsius
  • 8.4.3 Send messages for path: Between 10° and 25° Celsius
  • 8.4.4 Send messages for path: Warmer than 25° Celsius
  • 8.4.5 Publish your journey
  1. 8 - Adobe Journey Optimizer: External data sources and custom actions

8.4 Create your journey and messages

Adobe Journey Optimizer - Configure and use the SMS channel within Adobe Journey Optimizer

Previous8.3 Define a custom actionNext8.5 Trigger your journey

Last updated 2 years ago

In this exercise, you'll create a journey and several text messages by making use of Adobe Journey Optimizer.

For this use case, the goal is to send different SMS messages based on the weather conditions of the location of your customer. 3 scenarios have been defined:

  • Colder than 10° Celsius

  • Between 10° and 25° Celsius

  • Warmer than 25° Celsius

For these 3 conditions, you'll need to define 3 SMS messages in Adobe Journey Optimizer.

8.4.1 Create your journey

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 FY22. You'll then be in the Home view of your sandbox --aepSandboxId--.

In the left menu, go to Journeys and click Create Journey to start creating your Journey.

You should first name your journey.

As a Name for the journey, use --demoProfileLdap-- - Geofence Entry Journey. In this example, the journey name is vangeluw - Geofence Entry Journey. No other values must be set at this moment. Click OK.

On the left side of your screen, have a look at Events. You should see your previously created event in that list. Select it, then drag and drop it on the journey canvas. Your journey then looks like this. Click Ok.

Next, click on Orchestration. You now see the available Orchestration capabilities. Select Condition, then drag and drop it on the Journey Canvas.

You now have to define three conditions:

  • It's colder than 10° Celsius

  • It's between 10° and 25° Celsius

  • It's warmer than 25° Celsius

Let's define the first condition.

Condition 1: Colder than 10° Celsius

Click on the Condition. Click on Path1 and edit the name of the path to Colder than 10 C. Click on the Edit icon for the expression of Path1.

You'll then see an empty Simple Editor screen. Your query will be a bit more advanced, so you'll need the Advanced Mode. Click Advanced Mode.

You'll then see the Advanced Editor which allows code entry.

Select the below code and paste it in the Advanced Editor.

#{--demoProfileLdap--WeatherApi.--demoProfileLdap--WeatherByCity.main.temp} <= 10

You'll then see this.

In order to retrieve the temperature as part of this condition, you need to provide the city in which the customer currently is. The City needs to be linked to the dynamic parameter q, just like we saw previously in the Open Weather API Documentation.

Click the field dynamic val: q as indicated in the screenshot.

You then need to find the field that contains the current city of the customer in one of the available Data Sources.

You can find the field by navigating to --demoProfileLdap--GeofenceEntry.placeContext.geo.city.

By clicking that field, it will be added as the dynamic value for the parameter q. This field will be populated by for instance the geolocation-service that you've implemented in your mobile app. In our case we will simulate this with the admin console of the demo website. Click OK.

Condition 2: Between 10° and 25° Celsius

After having added the first condition, you'll see this screen. Click Add Path.

Double click on Path1 and edit the path name to Between 10 and 25 C. Click the Edit icon for the expression this path.

You'll then see an empty Simple Editor screen. Your query will be a bit more advanced, so you'll need the Advanced Mode. Click Advanced Mode.

You'll then see the Advanced Editor which allows code entry.

Select the below code and paste it in the Advanced Editor.

#{--demoProfileLdap--WeatherApi.--demoProfileLdap--WeatherByCity.main.temp} > 10 and #{--demoProfileLdap--WeatherApi.--demoProfileLdap--WeatherByCity.main.temp} <= 25

You'll then see this.

In order to retrieve the temperature as part of this Condition, you need to provide the city in which the customer currently is. The City needs to be linked to the dynamic parameter q, just like we saw previously in the Open Weather API Documentation.

Click the field dynamic val: q as indicated in the screenshot.

You then need to find the field that contains the current city of the customer in one of the available Data Sources.

You can find the field by navigating to --demoProfileLdap--GeofenceEntry.placeContext.geo.city. By clicking that field, it will be added as the dynamic value for the parameter q. This field will be populated by for instance the geolocation-service that you've implemented in your mobile app. In our case we will simulate this with the admin console of the demo website. Click OK.

Next, you'll add the 3rd condition.

Condition 3: Warmer than 25° Celsius

After having added the second condition, you'll see this screen. Click Add Path.

Double click on Path1 to change the name to Warmer than 25 C. Then click on the Edit icon for the expression this path.

You'll then see an empty Simple Editor screen. Your query will be a bit more advanced, so you'll need the Advanced Mode. Click Advanced Mode.

You'll then see the Advanced Editor which allows code entry.

Select the below code and paste it in the Advanced Editor.

#{--demoProfileLdap--WeatherApi.--demoProfileLdap--WeatherByCity.main.temp} > 25

You'll then see this.

In order to retrieve the temperature as part of this Condition, you need to provide the city in which the customer currently is. The City needs to be linked to the dynamic parameter q, just like we saw previously in the Open Weather API Documentation.

Click the field dynamic val: q as indicated in the screenshot.

You then need to find the field that contains the current city of the customer in one of the available Data Sources.

You can find the field by navigating to --demoProfileLdap--GeofenceEntry.placeContext.geo.city. By clicking that field, it will be added as the dynamic value for the parameter q. This field will be populated by for instance the geolocation-service that you've implemented in your mobile app. In our case we will simulate this with the admin console of the demo website. Click OK.

You now have three configured paths. Click Ok.

As this is a journey for learning purpose, we'll now configure a couple of actions to showcase the variety of options marketeers now have to deliver messages.

8.4.2 Send messages for path: Colder than 10° Celsius

For each of the temperature contexts, we'll attempt to send a text message to our customer. We can only send a text message if we have a Mobile Number available for a customer, so we'll first have to verify that we do.

Let's focus on Colder than 10 C.

Let's take another Condition element and drag it as indicated in the screenshot below. We'll verify if for this customer, we have a mobile number available.

As this is just an example, we are only configuring the option where the customer has a mobile number available. Add a label of Has mobile?.

Click on the Edit icon for the Expression for the Path1 path.

In the Data Sources shown on the left, navigate to ExperiencePlatform.ProfileFieldGroup.profile.mobilePhone.number. You're now reading the mobile phone number directly from Adobe Experience Platform's Real-time Customer Profile.

Select the field Number, then drag and drop it to the Condition Canvas.

Select the operator is not empty. Click Ok.

You'll then see this. Click OK again.

Your journey will then look like this. Click on Actions as indicated in the screenshot.

Select the action SMS, then drag and drop it after the condition you just added.

Set the Category to Marketing and select an SMS surface that enables you to send SMS. In this case, the email surface to select is SMS.

The next step is to create your message. To do that, click Edit content.

You now see the message dashboard, where you can configure the text of your SMS. Click the Compose message area to create your message.

Enter the following text: Brrrr... {{profile.person.name.firstName}}, it's freezing. 20% discount on jackets today!. Click Save.

You'll then see this. Click the arrow in the top left corner to go back to your journey.

You'll then be back here. Click Ok.

In the left menu, go back to Actions, select the Action --demoProfileLdap--TextSlack, then drag and drop it after the Message action.

Go to Action Parameters and click the Edit icon for the parameter TEXTTOSLACK.

In the popup-window, click Advanced Mode.

Select the below code, copy it and paste it in the Advanced Mode Editor. Click Ok.

"Brrrr..." + #{ExperiencePlatform.ProfileFieldGroup.profile.person.name.firstName} + " It's freezing. 20% discount on Jackets today!"

You will see your completed action. Click Ok.

This path of the journey is now ready.

8.4.3 Send messages for path: Between 10° and 25° Celsius

For each of the temperature contexts, we'll attempt to send a text message to our customer. We can only send a text message if we have a Mobile Number available for a customer, so we'll first have to verify that we do.

Let's focus on Between 10 and 25 C path.

Let's take another Condition element and drag it as indicated in the screenshot below. We'll verify if for this customer, we have a mobile number available.

As this is just an example, we are only configuring the option where the customer has a mobile number available. Add a label of Has mobile?.

Click on the Edit icon for the Expression for the Path1 path.

In the Data Sources shown on the left, navigate to ExperiencePlatform.ProfileFieldGroup.profile.mobilePhone.number. You're now reading the mobile phone number directly from Adobe Experience Platform's Real-time Customer Profile.

Select the field Number, then drag and drop it to the Condition Canvas.

Select the operator is not empty. Click Ok.

You'll then see this. Click Ok.

Your journey will then look like this. Click on Actions as indicated in the screenshot.

Select the action SMS, then drag and drop it after the condition you just added.

Set the Category to Marketing and select an SMS surface that enables you to send SMS. In this case, the email surface to select is SMS.

The next step is to create your message. To do that, click Edit content.

You now see the message dashboard, where you can configure the text of your SMS. Click the Compose message area to create your message.

Enter the following text: What a nice weather for the time of year, {{profile.person.name.firstName}} - 20% discount on Sweaters today!. Click Save.

You'll then see this. Click the arrow in the top left corner to go back to your journey.

You'll now see your completed action. Click Ok.

In the left menu, go back to Actions, select the Action --demoProfileLdap--TextSlack, then drag and drop it after the Message action.

Go to Action Parameters and click the Edit icon for the parameter TEXTTOSLACK.

In the popup-window, click Advanced Mode.

Select the below code, copy it and paste it in the Advanced Mode Editor. Click Ok.

"What nice weather for the time of year, " + #{ExperiencePlatform.ProfileFieldGroup.profile.person.name.firstName} + " 20% discount on Sweaters today!"

You will see your completed action. Click Ok.

This path of the journey is now ready.

8.4.4 Send messages for path: Warmer than 25° Celsius

For each of the temperature contexts, we'll attempt to send a text message to our customer. We can only send a text message if we have a Mobile Number available for a customer, so we'll first have to verify that we do.

Let's focus on Warmer than 25 C path.

Let's take another Condition element and drag it as indicated in the screenshot below. You'll verify if for this customer, you have a mobile number available.

As this is just an example, we are only configuring the option where the customer has a mobile number available. Add a label of Has mobile?.

Click on the Edit icon for the Expression for the Path1 path.

In the Data Sources shown on the left, navigate to ExperiencePlatform.ProfileFieldGroup.profile.mobilePhone.number. You're now reading the mobile phone number directly from Adobe Experience Platform's Real-time Customer Profile.

Select the field Number, then drag and drop it to the Condition Canvas.

Select the operator is not empty. Click Ok.

You'll then see this. Click OK.

Your journey will then look like this. Click on Actions as indicated in the screenshot.

Select the action SMS, then drag and drop it after the condition you just added.

Set the Category to Marketing and select an SMS surface that enables you to send SMS. In this case, the email surface to select is SMS.

The next step is to create your message. To do that, click Edit content.

You now see the message dashboard, where you can configure the text of your SMS. Click the Compose message area to create your message.

Enter the following text: So warm, {{profile.person.name.firstName}}! 20% discount on swimwear today!. Click Save.

You'll then see this. Click the arrow in the top left corner to go back to your journey.

You'll now see your completed action. Click Ok.

In the left menu, go back to Actions, select the Action --demoProfileLdap--TextSlack, then drag and drop it after the Messages action.

Go to Action Parameters and click the Edit icon for the parameter TEXTTOSLACK.

In the popup-window, click Advanced Mode.

Select the below code, copy it and paste it in the Advanced Mode Editor. Click Ok.

"So warm, " + #{ExperiencePlatform.ProfileFieldGroup.profile.person.name.firstName} + "! 20% discount on swimwear today!"

You will see your completed action. Click Ok.

This path of the journey is now ready.

8.4.5 Publish your journey

Your journey is now fully configured. Click Publish.

Click Publish again.

Your journey is now published.

ACOP
ACOP
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
ACOP
ACOP
Journey Optimizer
Journey Optimizer
Journey Optimizer
Journey Optimizer
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
ACOP
ACOP
Journey Optimizer
Journey Optimizer
Journey Optimizer
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
ACOP
ACOP
Journey Optimizer
Journey Optimizer
Journey Optimizer
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo
Demo