# Create a User Journey

{% stepper %}
{% step %}
**Create a User Journey**

You can create a new User Journey by clicking the **`+ Create Campaign`** button located in the upper right corner of the **`User Journey`** menu in the Dashboard.

![User Journey list](/files/SOLpofLanJOvMJOFHJUM)
{% endstep %}

{% step %}
**Configure the User Journey**

![](/files/gBixpNduUytQk2E0W1NJ)

1. Panel: You can add steps by directly dragging and dropping items.
   * Channel: Push Message, Friendtalk Message, Alimtalk Message, Text Message, Webhook (Pre-work is required to send KakaoTalk Messages.)
   * Branch: User-based Branch, Event-based Branch
   * Wait: Wait Time
2. Auto Arrange: Clicking this automatically arranges the added items on the screen.
3. User Journey Settings: Basic settings for the journey.

![](/files/IUTQQPiuU4YXuoXlP3vs)

Drag the circle at the bottom of each step block to connect each step.

Clicking on an item opens the detail screen. Complete the required settings for each item.

![](/files/jltXF2fOOEgjubqUbJOd)

**Step 2-1. Set Target, Entry & Exit Conditions**

You must complete the required basic settings to start the User Journey.

![](/files/ViNuVQAiLvp3m5LGGK3l)

![](/files/DXVhZFyNZgnzdsc87A6N)

1. **Target**

You can configure which users will enter the journey. You can select users who satisfy specific properties or users who belong to a specific cohort.

2. **Entry Conditions**

The journey begins when a user performs a specific action or meets a condition. For example, the journey can start automatically when a user registers for the service or visits a specific page.

* Up to 10 entry events can be added.
* The journey starts immediately when an entry event occurs.
* The journey proceeds for users who satisfy the conditions within the configured period.

3. **Exit Conditions (Optional)**

A user exits the journey when they meet a specific condition. For example, users are removed from the journey when they complete a target action (purchase, click, etc.) or when there is no response for a certain period.

**Step 2-2. Branch Settings**

Branch settings is a feature that splits paths based on specific conditions in the User Journey. This allows you to provide customized experiences based on user behavior, attributes, and whether specific events have occurred.

![](/files/LvGFwIMUlTCcXz5fJz1c)

* **User-based Branch**\
  Branches paths based on user attributes (e.g., registration date, region, purchase history, etc.). For example, you can send different messages to VIP customers and regular customers.

![](/files/FPNHmLktnysECILM9LsD)

* **Event-based Branch**\
  Branches the journey based on specific user actions (e.g., button click, add to cart, etc.). For example, you can send different messages to users who made a purchase and those who did not.

![](/files/qpUcMwHqO7Elx8bGfJRu)

{% hint style="info" %}
You can set a name for each branched group. Modify the group name to more easily understand campaign performance.
{% endhint %}

**Step 2-3. Wait Time Settings**

Wait for a specific period before proceeding to the next step. For example, you can wait 24 hours after adding to cart, and then send a message to users who have not purchased.

![](/files/YAnlB6oiQ9CFWSi06Son)

![](/files/J8a5pnL3r9H6sfqa1SEV)

**Step 2-4. Push Message Settings**

This is the step of sending app push notifications to users. Encourage user engagement through personalized messages, which can include product recommendations, discount benefits, reminders, etc.

![](/files/GZjDwOrBV0tTyKTGkOrF)

![](/files/DGkc8PLiJ8UEB2Ri3yNt)

1. **Platform Settings**\
   Supported platforms: Android, iOS
2. **Message Content**\
   Write the message content to send to users. (Title maximum 30 characters, body maximum 30 characters)\
   For Promotional Messages, you must review and comply with the Korea Internet & Security Agency's [App Push Advertising Guidelines](/en/crm-marketing/push-message-guide/promotion-push-guideline.md).\
   \
   Click the {...} button to write a personalized message. In the user message preview at the bottom, enter attribute values directly to preview the message content that will be shown to users.\
   For more details about push message settings, refer to [Writing a Push Message](https://docs.hackle.io/en/crm-marketing/user-journey-guide/pages/jijFoP1pGiiQp2cBF8S9#2-1-메시지-작성).

**Branch Based on Send Results**

For push messages, you can split branches based on the send result to configure the user's next journey. Messages may not be delivered for the following reasons:

* When the user's push token does not exist
* When the user's push token has expired

**Step 2-5. Friendtalk Message**

{% hint style="warning" %}
Before starting Kakao Messages, make sure to review the [Kakao Message Setup Guide](/en/crm-marketing/kakao-message-guide/kakao-message-campaign-setup-guide.md).
{% endhint %}

**Step 2-6. Alimtalk Message**

**Step 2-7. Brand Message**

**Step 2-8. Text Message**

**Step 2-9. Webhook**
{% endstep %}

{% step %}
**Start**

When all settings are complete, click the \[Start] button in the upper right corner to activate the User Journey.

{% hint style="warning" %}
Before starting the journey, make sure all items are properly connected!
{% endhint %}

![](/files/OHrbJf3X9ia86OmcXEyC)

**Editing an Active Journey**

* You can edit the journey even when it is active.
* Click the \[Edit] button in the upper right corner to proceed. Note that when changes are saved, they are **immediately applied** to users.
  {% endstep %}
  {% endstepper %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hackle.io/en/crm-marketing/user-journey-guide/create-user-journey.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.