Post-purchase excitement
Pre-requisites
WARNING
The below labs must have been completed before starting this lab
- Postman setup –> Postman installation
- Data Stores – Relational Store in Action –> Profile Target Dimension
- Data Stores – Configure Email Channels --> Configure for Profile
(this step takes up to 3hrs to complete)
If you have not done so, complete these now
CAUTION
This lab requires a subdomain delegated to Adobe in your sandbox. See Setup if you’re self-paced and don’t have one yet.
Lab overview
In this video you learn how the post-purchase excitement use case maps to a Journey, walking through the critical thinking questions and the architecture for sending a personalized shipping notification once an order ships.
Learning objectives
- Build a Journey that starts with a unitary event
- Set up and configure a custom action to call to a 3rd-party system to return information used in a Journey
- Execute a journey by streaming in an event payload
- Test and debug profiles and Journeys
- Validate the intended experience through reporting and logs
- Setup personalization in a simple email and see it in action
Use case description
When a customer places an order, you want to send a confirmation message with order details. Once the order is shipped, you want to trigger a second message with tracking information retrieved dynamically from a 3rd-party API.
Key callouts:
- The initial order confirmation would typically be implemented as a transactional message because customers don’t want to wait for a confirmation after they place an order.
- The order shipped notification could also be implemented using transactional messaging, but it could be built in a journey, allowing for a custom action to retrieve shipping information and enhance the customer communication.
NOTE
In this lab you only build out the Order Shipped message and skip the Order Confirmation message.
recommendation-more-help
blueprints-learn-help-blueprints