Create an in-app message in a journey

Transcript

Hi, I’m Nico, Product Manager for Adobe Journey Optimizer. Today I will be showing you how to create an in-app message in a journey. To follow along with this tutorial, you will need to be pre-configured and enabled for in-app messaging on Adobe Journey Optimizer. Please check with your administrator or refer to the documentation if you have any questions. I will start by telling you what in-app messaging is, before I show you how to create an in-app message in a journey. We will discuss how to test a journey containing an in-app, and then with the actual journey publication. An in-app message leverages specific user actions, events, or application states during a user mobile journey to increase overall engagement and customer experience. Unlike push notifications, in-app notifications are a conventional two-way form of communication that provide contextual information when the user is actively engaging with the app. You can control what the user sees, when you want them to see it, and how you think it would be most beneficial. By adding in-app messaging into the journey canvas as a first inbound channel, you can now create customer journeys combining both outbound channels, like an email or push notification, and inbound ones. Let’s deep dive into the tool and create a journey. On the left side navigation, click on Journey. Here you can see a complete repository of all journeys in your sandbox, with the status. To create a new journey, click on Create journey. By expanding the actions section on the left right, you will see a new in-app message activity available. Be aware that this activity is available for any journey, whether it is an audience-triggered one or an unitary. For example, I will define a unitary journey that will start when a specific event is emitted by a profile. Let’s say I have a big sport event scheduled for next weekend, and I want to promote merchandise sales through the app to people currently in that event location. To do such journey, I will select the location event that I know is used to capture a customer entering this event location. I will then define the appropriate namespace. Next, I will open the journey properties and set the right start date and end date based on when the event is supposed to occur. I will then drag and drop an in-app message activity into the journey canvas and start ordering my in-app. First thing you need to do is to select the surface rate to the mobile app I want to target. Please check with your administrator or refer to the documentation for more information about surface creation. If you do not see any surface here, you may not have sufficient rights and will need to check with your admin. Then, I will define my in-app contents. I will not go into details as we have a dedicated video on in-app autorail. Finally, I will define my trigger rules and say that I want that in-app to be triggered every time the user opens the app, but only for three times. As you may have seen, a wait activity has been automatically added after the in-app message. The activity is here to provide some guidance on how in-app works in journey and to avoid frequent user issues. When that in-app will be published, any profile reaching that in-app activity will qualify for the in-app you defined. It doesn’t mean that they will see that the in-app message right away. They will still need to do the actions you defined as trigger rules. This qualification for an in-app will happen when the profile reaches the end of the journey. Therefore, binding a wait activity will allow the profile to not end the journey too soon. You can remove that activity if needed, or could define any time period you want. When I finish designing my in-app, I would like to link the display of that in-app to product purchases, to stop it if the customer purchases a product during the event. For that, I will drag and drop a purchase event I have previously defined that will be triggered every time a customer purchases this type of merchandise. Let’s pause here and discuss what will happen when the journey will be live. As I’ve set a start and an end date, my journey will listen to incoming events only during my sports event. As soon as the customer reaches my event location, they will enter that journey, be qualified for that in-app activity, which means that the app will now wait for the next app launch to display that in-app message, and journey will then wait for a product purchase. If it happens during a two days period, then the profile will reach the end of the journey and be disqualified for that in-app immediately. And if it doesn’t happen, the profile will exceed that journey after two days, which will also disqualify it for the in-app. When you satisfy the journey, you can start testing it with the test mode. Test mode with in-app messaging works similarly to any other type of journeys. You just need to click on a test toggle, wait a few seconds for that in-app to be activated, then click on trigger an event. Select the location event as the event you want to simulate and define the profile identified. In my event, I said it was an ECID, so I paste my test profile ECID. By clicking on send, I will be able to see my test profile following for that journey. I can then validate with my test profile on the mobile app that my in-app is displayed. For that use case, I may need to change the date constraint I’ve defined in my journey properties, as there may not be a Saturday or a Sunday today. Following that validation, I can also trigger a purchase event to validate that my profile will end that journey I do not see in the in-app anymore. For this, I can click on trigger an event, select my purchase event, and use the ECID again to simulate a purchase event for my profile. I can then validate my profile is reaching the end of the journey and that the in-app is not displayed anymore on my device. Be aware that qualification or disqualification of an in-app may take a few minutes. Reporting is also available in test mode if you want to validate reporting data too. You can then stop test mode if your test is over. Be aware that if you specially want to test the in-app content, two options are available on the in-app ordering screen. First, you can simulate the content of that in-app for one or more test profiles. This is done through the simulate content button. Or you can also use the preview on device feature to directly see on your mobile device what your in-app will look like. For this, click on preview on device. Then start. Provide the URL of your app so that clicking on such URL on your device will automatically launch the app. Click on next. Flash the QR code with your mobile device and enter the PIN. For this to work, you will need to have assurance enabled on your app. More information on the SDK documentation. When the connection is successful, you will see a green connected at the bottom of the screen and you will be able to trigger an in-app anytime you click on preview on device. You can then do any modification on your in-app and still be able to trigger a preview when needed. After testing is complete and you’re satisfied with your journey, you can click on publish to set your journey live. Wait a few seconds for your journey to be published and click on the reporting section to see how your journey executes. You know now how to create an in-app in your journey. Thank you for watching.