In this use case, you will see how to use multiple types of personalization in a single push notification message. Three types of personalization will be used:
The goal of this example is to push an event to Journey Optimizer every time a customer order is updated. A push notification is then sent to the customer with information on the order and a personalized offer.
For this use case, the following prerequisites are needed:
Click the Journeys menu and create a new journey.
Add your entry event, and a Push action activity.
Configure and design your push notification message. Refer to this section.
In the Push activity, click Edit content.
Click the Title field.
Type in the subject and add profile personalization. Use the search bar to find the profile’s first name field. In the subject text, place the cursor where you want to insert the personalization field, and click the + icon. Click Save.
In the Push activity, click Edit content and click the Title field.
Select the Contextual attributes menu. Contextual attributes are only available if a journey has passed contextual data to the message. Click Journey Orchestration. The following contextual information appears:
Expand the Events item, and look for the order number field related to your event. You can also use the search box. Click the + icon to insert the personalization field in the subject text. Click Save.
Now click the Body field.
Type the message and insert, from the Contextual attributes menu, the order item name and the order progress.
From the left menu, select Offer decisions to insert a decisioning variable. Select the placement and click the + icon next to the decision to add it to the body.
Click validate to make sure that there are no errors, and click Save.
Click the Test button, then click Trigger an event.
Enter the different values to pass in the test. Test mode only works with test profiles. The profile identifier needs to correspond to a test profile. Click Send.
The push notification is sent and displayed on the test profile’s mobile phone.
Verify that there is no error and publish the journey.