1. Understand the need for a journey
2. Learn how to create a journey for your segment

1. Field update
2. Add Tags
3. Remove Tags
4. Email notification
5. Task
6. Create Record
7. Convert
8. Webhook
9. Functions

It defines the linkage between the modules indicated in the source and destination states. This enables smooth data flow and facilitates a holistic view of customer interactions and information.  This option can be used in cases where you want to track the specific records on which a transition occurred. For example, say you received a request for a product demo from three different customers through email. You send them webinar invitations, and a week after attending it, one of the three customers purchases the product. So this customer moves from the "contacts" state to the "deals" state. Since moving these states means moving between two modules, by using the connectivity options—look-up or reference—you can trace the path and find the action that propelled the record to the next state.

In the above example, after attending the webinar, the customer makes the payment and moves to the next state (deal). You must add the contact's look-up or give reference of the contact within the deal's record to understand how the two records are interlinked and to know what activity led the record to the next state.

When you link a journey with an account, every contact in the account will receive the initial action (such as an email campaign) in the segment journey. However, only the contact responding first will progress through the entire journey.

How to add a state in a journey

1. Open the segment for which you want to create a journey.
   
2. On the Segment page, from the Manage Criteria drop-down, select Create Journey.
3. In the New Journey section, the segment associated to the journey is already displayed. Enter the name of the journey and the description.
   
   
4. Click Proceed.
   
5. On the displayed journey builder page, click the Add State button.
   
6. On adding a state, the Add State panel opens to the right of the journey builder. You must mention the State name, Description, and the Type of module associated to the state and then click Save.
   
   
7. Upon saving the state, the panel in the right will now display two tabs — State Info and Actions
1. State Info tab will display the details of the state that you entered while creating the state.
   
2. The Actions tab will display three action items — Instant Action, Scheduled Action, and Recurring Action.
   
1. Instant Action - An immediate automated response triggered by a specific event or condition in a workflow or system.
   You can associate an action to the state, that is, what do you want to execute on a contact reaching the state. You can send emails, add tags, add a task, run a webhook function, remove tags, and so on.
   
   
2. Scheduled Action - A pre-planned automated task initiated at a predetermined time or date within a workflow or process.
   It is setting up an automatic action that will be sent to contacts at a specific time as part of a planned marketing campaign.
   
3. Recurring Action - An automated task that repeats at regular intervals or specified patterns within a workflow or system.
   
8. On the builder, you can move the newly added state to the desired position and connect it to the existing state. 
   

How to add a transition in the builder

1. On the builder, click the plus icon in the connector between the module and the state for the first time, or between two states.
2. In the Add Transition panel, enter a transition name, description, and choose a trigger for the transition.
   
   
   
   A transition creates a link between two states. It lets you define the condition at which a record can move from one state to another. For example, a record can move from "Pricing Details" to "Request demo" only if the conditions and actions defined in the "Open email" transition is satisfied.
   
   
3. You can select when a transition should be triggered (this is a mandatory step). To name a few:
   
1. Submission of a webform — A transition will be triggered when a record has entered CRM through a webform. This trigger is available only at the beginning of the journey or for the first transition of a journey.  
2. Creation of a record — A transition will take place whenever a record is created in the specified module and layout.
3. Edit of a record — A transition will be triggered whenever a record is edited. You can also add a condition. For example, whenever the lead status is changed to qualified, a payment link must be sent.
4. Receiving an API call — If you want to invoke any transition from the third-party application, you can select this option and copy the API URL provided by us. Also, you can mention the parameters that should be passed along with each API call. You can select a maximum of six parameters from the following data types: string, number, date, date/time, boolean.
5. Approval of record — A transition will be triggered only if a record is approved. For example, an order will be placed only upon payment approval. You must select to which approval process the record belongs.
6. Rejection of record — A transition will be triggered on rejection of a record. For example, the order will be canceled if the payment fails. You must select to which approval process the record belongs.
7. A date/date time — A transition will be triggered at date or date/time field of a module.
4. If required, you can also set a condition for the transition, that is, you can choose only those records in the accounts module that can go through the transition.
   
   Transition Info - Provides a comprehensive overview of the movement and status changes of records as they progress through different stages, enhancing visibility and decision-making.
   
   
5. Similar to the state action, you can also set the action for the transition, if required.
   
6. On the Connectivity tab, specify the connectivity between the module in source and destination state. It can either be a reference, lookup, or others (condition to choose a contact).
   
   
   

1. Click Set deadline for this journey in the left panel.
   
2. You can enter the number of days after which the state will reach the deadline.
   
   
3. Click Add action to add the action to be performed once the deadline is reached. You can escalate it to another role within the organization and/or move to a state in the same journey.
   
   
4. Click Save to save the state configuration.
   

How to delete transition

1. On the journey builder, select the transition that you want to delete.
   
2. Click the Delete this transition at the bottom of the left panel.
   
3. The following pop-up appears.
   

How to delete a state

1. On the journey builder, select the state that you want to delete.
   
2. Click the Delete this state at the bottom of the left panel.
   
3. The following pop-up appears.
   

1. Deleting a state will remove all associated actions and transitions.
   
2. Once you delete a state, the action cannot be undone.

How to delete a deadline

1. Click the (-) icon in the deadline section on the left panel.
   
2. In the Delete Deadline pop-up that appears, click Delete.
   

How to publish a journey

We will now comprehend the functioning of the journey builder by utilizing the use case scenario that has been under our observation.

Zylker Use Case - Part III

Zylker has created an "Up for renewal" segment. It has now decided to create a journey for this segment. 

Before you begin:

1. Zylker has created a segment for the Renewal process.
2. The "Up for Renewal" segment is open in Segment view.

How to build a journey for the segment

1. On the Segment page, from the Manage Criteria drop-down, select Create Journey.
   
   
2. In the New Journey section, the segment associated to the journey is already displayed. Enter the name of the journey and the description.
   
   
3. Click Proceed.
4. On the Journey Builder page, click Add State and enter the module that would be associated with the journey.
5. Enter the transition criteria and action associated with the transition.
6. Similarly, you can add the required states, transition conditions, and the trigger actions.
7. You can save the journey as a draft and come back to it later when needed. Once you are done with creating the journey, click Publish.
   
   

Result

Zylker has successfully created a journey for the "Up for renewal" segment. With this, you have come to the end of working of Zylker ABM. In the next section, you will see how the journey you created for the segment performs.