Journeys (V2) Use Cases

Send a confirmation message immediately after a user takes a key action, like placing an order or submitting a form. This type of journey helps reinforce trust and provides instant feedback by delivering personalized messages based on event details.

This use case is ideal for transactional events that should trigger follow-up communication without delay.

1. Set the journey entry condition to Users perform an event.
2. Choose the event that represents the user action (for example, Order_Confirmation).
3. (Optional): Add event property filters if you only want to trigger the journey under specific conditions.
4. Click Build, then add a Send to Destination step to forward the event.
5. Configure destination:
   • Select the destination you want to send the payload to.
   • Enrich the payload with profile traits or journey context as needed.
6. Click Save to publish the journey.

The following example shows a Order_Confirmation event payload that could trigger this journey. You can customize the event name and properties based on your use case.

1
{
2
  "userId": "99",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Order_Confirmation",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "T-Shirt",
9
    "productColor": "green",
10
    "productSize": "Large",
11
    "productPrice": "$55.34",
12
    "event_location": "A",
13
    "cart_ID": "123456",
14
    "scenario": "01 Ordered Product"
15
  }
16
}

Send a personalized nudge when a user starts an action (like filling out an application) but doesn't complete it within a certain time window. This type of journey helps recover drop-offs by checking for a completion event and following up only if it's missing.

This use case is ideal for flows like job applications, signups, demo requests, or onboarding forms.

1. Set the journey entry condition to Users perform an event.
2. Choose the event that indicates the user started the flow (for example, Application_Started).
3. (Optional): Add event property filters if you only want to trigger the journey under specific conditions.
4. Click Build, then add a Hold Until step.
5. In the Hold Until step:
   • Specify the completion event (for example, Application_Completed) as the condition.
   • Set a maximum hold duration.
6. Add a Send to Destination step on the "timeout" branch to send a follow-up message.
7. Configure the destination:
   • Select the destination you want to send the payload to.
   • Enrich the payload with profile traits or journey context as needed.
8. Preview the payload that Segment will send to your destination.
9. Publish the journey.

Expand image

The following example shows both the entry event that starts the journey and the evaluation event that cancels the nudge if the user completes the application.

1
{
2
  "userId": "88",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Application_Started",
6
  "properties": {
7
    "Category": "A",
8
    "Tier": "Premium",
9
    "VIP": true,
10
    "Application_id": "1234",
11
    "scenario": "Trigger campaign with Application Started"
12
  }
13
}

1
{
2
  "userId": "88",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Application_Completed",
6
  "properties": {
7
    "Category": "A",
8
    "Tier": "Premium",
9
    "VIP": true,
10
    "Application_id": "1234",
11
    "scenario": "Complete campaign without a nudge b/c Application was Completed"
12
  }
13
}

Send a personalized follow-up when a user views their cart but doesn't complete the checkout. This journey tracks whether a checkout event occurs within a short window after the cart is viewed. If it doesn't, you can send a reminder to bring them back.

This use case works well for e-commerce sites that want to reduce cart abandonment and recover potential sales.

1. Set the journey entry condition to Users perform an event.
2. Choose the entry event that indicates cart activity (for example, Cart_Viewed).
3. (Optional): Add event property filters to narrow the scope of who enters.
4. Click Build, then add a Hold Until step.
5. In the Hold Until step:
   • Specify Checkout_Completed as the evaluation event.
   • Set a maximum hold duration based on how long you want to wait before nudging (for example, 1 hour).
6. Add a Send to Destination step on the timeout branch to send the cart reminder.
7. Configure the destination:
   • Select the destination you want to send the payload to.
   • Enrich the payload with profile traits or journey context as needed.
8. Preview the payload that Segment will send to your destination.
9. Publish the journey.

The following examples show the entry and evaluation events for this journey pattern.

1
{
2
  "userId": "88",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Cart_Viewed",
6
  "properties": {
7
    "cart_ID": "123",
8
    "scenario": "01 Simple Cart Abandonment",
9
    "checkout_cart": [
10
      {
11
        "productId": "001",
12
        "productName": "T-Shirt",
13
        "productColor": "green",
14
        "productSize": "Large",
15
        "productPrice": "$55.34"
16
      },
17
      {
18
        "productId": "002",
19
        "productName": "Jeans",
20
        "productColor": "blue",
21
        "productSize": "Medium",
22
        "productPrice": "$99.56"
23
      }
24
    ]
25
  }
26
}

1
{
2
  "userId": "88",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Checkout_Completed",
6
  "properties": {
7
    "cart_ID": "123",
8
    "scenario": "01 Simple Cart Abandonment",
9
    "checkout_cart": [
10
      {
11
        "productId": "001",
12
        "productName": "T-Shirt",
13
        "productColor": "green",
14
        "productSize": "Large",
15
        "productPrice": "$55.34"
16
      },
17
      {
18
        "productId": "002",
19
        "productName": "Jeans",
20
        "productColor": "blue",
21
        "productSize": "Medium",
22
        "productPrice": "$99.56"
23
      }
24
    ]
25
  }
26
}

Send a personalized reminder when a user adds items to their cart but doesn't complete checkout, even if they modify their cart along the way. This journey resets the wait timer each time the cart is updated, ensuring that follow-up messages reflect the most recent cart contents.

This use case is ideal for e-commerce journeys where users frequently change items before deciding to purchase.

1. Set the journey entry condition to Users perform an event.
2. Choose the entry event that indicates the cart is started (for example, Product_Added).
3. (Optional): Add event property filters if needed.
4. Click Build, then add a Hold Until step.
5. In the Hold Until step:
   • Specify Cart_Modified as an update event that resets the timer and updates the journey context.
   • Specify Order_Confirmation as the evaluation event that exits the user from the journey.
   • Set the maximum hold duration (for example, 2 hours).
6. Add a Send to Destination step on the timeout branch to send a cart reminder.
7. Configure the destination:
   • Select the destination you want to send the payload to.
   • Enrich the payload with profile traits or journey context as needed.
8. Preview the payload that Segment will send to your destination.
9. Publish the journey.

Expand image

The following example shows the entry event that starts the journey, the update event that modifies the cart, and the evaluation event that would cancel the reminder.

1
{
2
  "userId": "23",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Product_Added",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "T-Shirt",
9
    "productColor": "green",
10
    "productSize": "Large",
11
    "productPrice": "$55.34",
12
    "cart_ID": "12345",
13
    "scenario": "01 Simple Loopback Abandonment"
14
  }
15
}

1
{
2
  "userId": "23",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Cart_Modified",
6
  "properties": {
7
    "productId": "002",
8
    "productName": "Jeans",
9
    "productColor": "Blue",
10
    "productSize": "medium",
11
    "productPrice": "$88.43",
12
    "productCategory": "A",
13
    "cart_ID": "12345",
14
    "scenario": "01 Simple Loopback Abandonment",
15
    "checkout_cart": [
16
      {
17
        "productId": "001",
18
        "productName": "T-Shirt",
19
        "productPrice": "$55.34",
20
        "productColor": "green",
21
        "productSize": "Large"
22
      },
23
      {
24
        "productId": "002",
25
        "productName": "Jeans",
26
        "productColor": "blue",
27
        "productSize": "Medium",
28
        "productPrice": "$99.56"
29
      }
30
    ]
31
  }
32
}

1
{
2
  "userId": "23",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Order_Confirmation",
6
  "properties": {
7
    "productPrice": "$170.78",
8
    "cart_ID": "12345",
9
    "scenario": "01 Simple Loopback Abandonment",
10
    "checkout_cart": [
11
      {
12
        "productId": "001",
13
        "productName": "T-Shirt",
14
        "productPrice": "$55.34",
15
        "productColor": "green",
16
        "productSize": "Large"
17
      },
18
      {
19
        "productId": "002",
20
        "productName": "Jeans",
21
        "productColor": "blue",
22
        "productSize": "Medium",
23
        "productPrice": "$99.56"
24
      },
25
      {
26
        "productId": "003",
27
        "productName": "Sweatshirt",
28
        "productColor": "Black",
29
        "productSize": "Medium",
30
        "productPrice": "$99.08"
31
      }
32
    ]
33
  }
34
}

Send a series of personalized reminders to users who browse multiple products but don't take action, like adding an item to their cart. This journey tracks a sequence of Viewed_Product events and only exits when the user adds a product or reaches the end of the flow.

This use case is helpful for nurturing intent-based activity over time, especially for higher-consideration purchases.

1. Set the journey entry condition to Users perform an event.
2. Choose the entry event that represents product views (for example, Viewed_Product).
3. (Optional): Add property filters to target only certain products or categories.
4. Click Build, then add a Hold Until step.
5. In the Hold Until step:
   • Specify Product_Added as the evaluation event.
   • Set a maximum hold duration (for example, 1 hour).
6. Add a second Hold Until step to repeat the pattern:
   • Again, check for Product_Added.
   • Adjust the hold duration as needed.
7. Add a Send to Destination step at the end of the second hold duration.
   • Enrich the payload with recent event data or profile traits.
8. Preview the payload that Segment will send to your destination.
9. Publish the journey.

The following examples show the entry and evaluation events for this flow.

1
{
2
  "userId": "26",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Viewed_Product",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "T-Shirt",
9
    "productColor": "green",
10
    "productSize": "Large",
11
    "productPrice": "$55.34",
12
    "productCategory": "A",
13
    "session_ID": "12345",
14
    "scenario": "01 Browse Abandonment"
15
  }
16
}

1
{
2
  "userId": "26",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Viewed_Product",
6
  "properties": {
7
    "productId": "002",
8
    "productName": "Jeans",
9
    "productColor": "Blue",
10
    "productSize": "Medium",
11
    "productPrice": "$88.77",
12
    "productCategory": "A",
13
    "session_ID": "12345",
14
    "scenario": "01 Browse Abandonment"
15
  }
16
}

1
{
2
  "userId": "26",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Viewed_Product",
6
  "properties": {
7
    "productId": "004",
8
    "productName": "Socks",
9
    "productColor": "White",
10
    "productSize": "Regular",
11
    "productPrice": "$03.44",
12
    "productCategory": "A",
13
    "session_ID": "12345",
14
    "scenario": "01 Browse Abandonment"
15
  }
16
}

Send a series of follow-up messages when a user starts a flow—like a trial—but doesn't complete a key milestone within a set timeframe. This journey uses multiple Hold Until steps to send nudges at scheduled intervals until the user takes the expected action.

This use case is ideal for trial reminders, onboarding flows, or progressive engagement campaigns.

1. Set the journey entry condition to Users perform an event.
2. Choose the entry event that starts the campaign (for example, Trial_Started).
3. (Optional): Add property filters to narrow who enters the journey.
4. Click Build, then add a Hold Until step.
5. In the Hold Until step:
   • Specify Trial_Ended as the evaluation event.
   • Set a hold duration (for example, 3 days).
6. Add a Send to Destination step on the timeout branch to send the first reminder.
7. Add another Hold Until step and repeat the same logic.
8. Add a second Send to Destination step at the end of that branch.
9. Preview the payloads that Segment will send to each destination.
10. Publish the journey.

The following events show a user starting and (eventually) ending a trial. The re-engagement messages are only sent if the Trial_Ended event doesn't occur before the hold expires.

1
{
2
  "userId": "747",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Trial_Started",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "Basic Plan",
9
    "productCategory": "Enterprise",
10
    "productPrice": "$55.34",
11
    "Account_ID": "12345",
12
    "scenario": "01 Siemens"
13
  }
14
}

1
{
2
  "userId": "747",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Trial_Ended",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "Basic Plan",
9
    "productCategory": "Enterprise",
10
    "productPrice": "$55.34",
11
    "Account_ID": "12345",
12
    "scenario": "01 Siemens"
13
  }
14
}

Re-engage users with a personalized sequence of nudges as they move through multiple funnel stages—such as visiting the site, creating an account, starting a trial, and subscribing. This journey listens for key events at each stage, and if no progress is made within a set time, it triggers follow-ups to bring users back.

This use case is useful for SaaS products, gated onboarding flows, or any multi-step process where users drop off between key actions.

1. Set the journey entry condition to Users perform an event.
2. Choose the initial entry event (for example, Website_Viewed).
3. (Optional): Add property filters to limit entry to specific sessions or pages.
4. Click Build, then add a series of Hold Until steps for each major conversion point.
5. In each Hold Until step:
   • Specify the expected event (for example, Account_Created, Trial_Started, or Subscription_Started).
   • Configure a fallback path using the maximum hold duration.
6. On the timeout branch of each Hold Until step, add a Send to Destination step to send a reminder.
7. After each message, optionally add another Hold Until step to check for the next milestone.
8. Preview the payloads that Segment will send to your destinations.
9. Publish the journey.

Expand image

These examples show key moments in the journey, from entry to conversion milestones. Each Hold Until step corresponds to one of these events.

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Website_Viewed",
6
  "properties": {
7
    "pageViewed": "Home",
8
    "path": "site/home",
9
    "sessionID": "12345",
10
    "scenario": "01 Complex Multi-step"
11
  }
12
}

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Account_Created",
6
  "properties": {
7
    "name": "Tom",
8
    "email": "tom@twilio.com",
9
    "accountID": "09876",
10
    "sessionID": "12345",
11
    "scenario": "01 Complex Multi-step"
12
  }
13
}

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Payment_Method",
6
  "properties": {
7
    "paymentMerchant": "Visa",
8
    "paymentType": "Credit Card",
9
    "accountID": "09876",
10
    "sessionID": "12345",
11
    "scenario": "01 Complex Multi-step"
12
  }
13
}

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Trial_Started",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "Basic Plan",
9
    "productCategory": "Enterprise",
10
    "productPrice": "$55.34",
11
    "sessionID": "12345",
12
    "accountID": "09876",
13
    "scenario": "01 Complex Multi-step"
14
  }
15
}

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Trial_Ended",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "Basic Plan",
9
    "productCategory": "Enterprise",
10
    "productPrice": "$55.34",
11
    "sessionID": "12345",
12
    "accountID": "09876",
13
    "scenario": "01 Complex Multi-step"
14
  }
15
}

1
{
2
  "userId": "999",
3
  "context": {},
4
  "integrations": {},
5
  "event": "Subscription Started",
6
  "properties": {
7
    "productId": "001",
8
    "productName": "Basic Plan",
9
    "productCategory": "Enterprise",
10
    "productPrice": "$55.34",
11
    "sessionID": "12345",
12
    "accountID": "09876",
13
    "scenario": "01 Complex Multi-step"
14
  }
15
}