--- title: Creating the journey slug: naama-hol/GKVR-creating-the-journey description: >- docTags: createdAt: 2024-01-30T23:03:21.354Z --- In this exercise, you'll be creating and testing a journey using all the components you've created in the previous exercises. ## Journey overview To get an overview of all journeys in Adobe Journey Optimizer: 1. In the menu on the left side, under **Journey Management**, click on **Journeys**. You will see a overview with all existing journeys. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/tj_bJ5SjKwK878MvPdqbb_screenshot-2024-07-08-at-234050.png) ## Creating a journey We'll be creating a journey that will send a push notification to customers when they start the PCA Application, then abandon. We want to remind the customer to complete the application process. Click on **Create Journey**. You'll be taken to the **Journey canvas** with the journey properties opened. 1. Set the **name** to `[your name] - PCA Application Journey`. 2. For the other properties we'll keep the default values. 3. Your screen should look like the image below. Click **Save** to save and close the properties. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/odAsFAcRsbO2KoFqWopZy_screenshot-2024-07-08-at-234413.png) You're now in the journey canvas. This is where you'll be creating your journey's logic. In the left menu you have **activities**. There's three types of activities: **Events** are the triggers that can start or continue your journey. **Orchestration** is the logic of your journey. It looks at conditions, audiences, but can also be used to make your workflow wait or end. **Actions** are the results of your journey. This can be messages, profiles updates or API calls. ### Event trigger 1. We're starting our workflow of with an event trigger. From the events tab, choose **your created event (\[yourName]PCAApplication\_Start)** and drag it onto the canvas. *If you did not create an event, use the **PCAApplication\_Start** event.* 2. There's nothing we need to configure for this as we have already done this in the **Configuring Events **section. 3. Click **Save** to close the menu. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/DZIPA9A3SdoEmNZnXTAh3_screenshot-2024-07-08-at-234640.png) ### Event - Application Submit 1. From the Events tab, choose **your created event (\[yourName]PCAApplication\_Submit)** and drag it onto the canvas to the right of the PCAApplication\_S event. *If you did not create an event, use the **PCAApplication\_Submit **event.* 2. Check **Define the event timeout** and set it to wait for `2 days`. 3. Check the box **Set a timeout path**. 4. Your screen should look like the image below. Click **Save**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/HFdoSJDVs-KQCMWG4CXmR_screenshot-2024-07-09-at-000021.png) ### Condition - Is a mobile app user? When the customer starts a PCA application but doesn't submit within 2 days, the first thing we want to check is if the customer has the mobile app in order to communicate via the Push channel. 1. From the orchestration tab, choose Condition and drag it onto the lower branch on the canvas (2 d timeout). 2. Click on the activity to open the detailed view. 1. Set the **label** to `Has mobile app?`. 2. Click on **Path1** and change the label to `Yes`. 3. Click on **Add an expression** to open a window. 1. On the left side, open **Audiences**. Scroll down till you find the audience you created called **\[your name] - Has mobile app** and drag it to the right side. *If you didn't create the audience, use **Lloyds - Has mobile app**.* 2. By default the statement should be on `true`, if not click the toggle. Checks if the title reads `[your name] - Has mobile app audience membership is true` and click **Ok**. 3. Click **Ok** to save the conditions. 4. Check **Show path for other cases than one(s) above** and set the label to `No`. 5. Your screen should look like the image below. Click **Save**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/-Gz3HXj5hRlsCxD5E4Woi_screenshot-2024-07-09-at-000557.png) In our journey we want to focus on the customer that do have the mobile app. ### Push #1 - Application reminder - continue your PCA Application 1. From the actions tab, choose **Push** and drag it onto the canvas at the **Open**-path following the `Yes` branch of the `Has mobile app?` condition. 2. Click on the Push action to open the detailed view. 1. Set the **Label** to `PCA Application Reminder`. 2. Set the **Category** to `Marketing`. 3. Set the **Push surface** to `marketingMessages`. 4. Click on **Edit content** to start designing your email. 1. Set the **Title** to `Complete your application`. 2. To change the **body**, click on the personalisation icon (on the right of the field). A window will open allowing you to write advanced expressions. In this lab we will not add any personalisation to the Push notification text, we will explore this in Part 2 of this Lab when we compose an Email. 3. Click **Cancel** to close the expression editor window. 4. Set the **Body** to `Receive £175 to switch to a new Club Lloyds Current Account today`. 5. To add an image, click on **Add media**. Assets Essentials will open. Navigate to **Bootcamp > Lloyds** and select the image `lloyds-logo-partial.png` and click **Select** in the top right. 6. Your screen should look like the image below. 7. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/RMIlHPHVN03aT95IR37U__screenshot-2024-07-09-at-001734.png) 1. Navigate out of the designer by clicking the arrow on the top left of your screen. 2. Your screen should look like the image below. Click **Save**. ![](https://api.archbee.com/api/optimize/1Jp0iolWv35Z_mkI7oUiT/vL7oSbbL91Jsgn6_uBv5J_screenshot-2024-07-09-at-001907.png) :::hint{type="success"} You have now successfully created Part 1 of the PCA Application journey using the Adobe Journey Optimizer. Next, we will create Part 2, snd test our journey using Test Mode. :::