This Help system uses the terms configuration and authoring to describe the two methods of editing a journey.
Configuration refers to the process of associating supporting assets (such as Campaigns or Segments) to steps in the journey flow. For example, if you have a Send Email step in the flow, you must configure the step by selecting the Messaging Campaign associated with this step. Configuration is required for all journeys, even if you're using a standard journey.
Authoring refers to the process of editing the flow of events in the journey, such as adding or removing steps, drawing connection lines between steps, and so forth. If you're using an "out of the box" standard journey, you may not need to do any authoring; you can simply configure the steps in the standard journey and publish it. However, you need to author the journey if you want to make any changes to the steps that comprise the journey, or if you're building a new journey from scratch.
This Help topic focuses on how to configure a standard journey. For more information on authoring, please see Self Service Journeys.
The Onboarding journey communicates with consumers by means of Email Campaigns created and deployed from Cheetah Messaging.
Note: This topic does not go into details on how to create Campaigns. For more details on this process, please see the Cheetah Messaging Online Help system, or speak with your Technical Services team.
When creating the Email Campaigns, they should be built with the following configurations:
Use EDP or a Messaging table as the data source for the Campaign.
Campaign Type is Event-triggered.
Using EDP as the data source provides additional functionality, such as integrated access to EDP Segments and Loyalty objects, at-send-time decisioning and optimization, and support for Machine Learning models.
The rest of the Campaign configuration follows a normal Campaign setup -- select your Sender Profile, enter the message content, optionally send proofs, then launch the Campaign.
After you create and launch the Campaigns for this journey, you must associate each of them with an Action step in the journey itself. For more details on this process, see "Journey Configuration" below.
Once you have built all of the necessary supporting assets, the final step in the journey setup is to create the journey, and assign the supporting assets to the appropriate steps within the journey. The standard Onboarding journey is available in the Journey Library; this journey serves as a template that you can configure as needed.
Create a New Standard Journey When creating a new journey, the platform allows you to either use an existing standard journey as the starting point, or you can create a new journey from scratch. To create a new journey based on one of the standard journey types:
Note: While you can create multiple instances of each of the standard journeys, only one instance can be published at a time. This restriction will be eliminated in a future release of Journey Designer. |
Within Journey Designer, an Action step refers to a process that the platform executes. The standard Onboarding journey comprises four Send Email Action steps, all of which must be associated with a corresponding Cheetah Messaging Campaign.
Assign a Campaign to an Action Step To associate a Campaign with an Action step:
|
Remove an Action Step Instead of the default Action step, you can optionally remove an unneeded Action step. To remove an Action step:
|
Replace an Action Step Existing Action steps in a journey can be replaced with alternatives in order to meet your business objectives. To swap an existing Action step with a different Action step type:
|
Within Journey Designer, a Wait step is used to allow an appropriate period of time to elapse before executing the next step in the journey. All of the Send Email Action steps within the default Onboarding journey are followed by a Wait step. After this wait time has elapsed, Journey Designer progresses the consumer to the next step. The duration of each of these wait times can be configured to meet your business requirements.
Define Wait Duration To configure a Wait step:
Note: Optionally, you can disable a Wait step if you want the journey to immediately move to the next step; simply set the wait time duration to zero.
|
The final step in the journey configuration process is to save and publish the journey.
Save a Journey To save your journey, either:
When you save your journey, the platform validates that the journey flow is valid. If your journey encounters any of the following errors, a message is displayed indicating the nature of the issue. Correct the issue, and retry the save process.
Note: You can't publish a journey until you have successfully saved it.
|
Publish a Journey When you publish a new journey, the platform changes its status from "Draft" to "Running." The journey is then considered live and in use, and the platform can begin adding consumers to it. To publish a journey:
|
Publish Changes to a Journey Whenever you make changes to a live journey, you must re-publish the journey in order to apply the changes. When you re-publish a journey, all new consumers added to the journey from that point forward will use the new configuration. For consumers currently in the journey, only consumers that have not yet reached the modified step (or steps) will be affected by the new configuration. To publish changes:
Optionally, you can also discard the changes to roll-back to the "last published" iteration of the journey. To discard changes:
|