> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/crm-marketing/user-journey-guide/advanced-settings.md).

# User Journey Advanced Settings

## Journey Re-entry

You can configure the journey so that the same user automatically enters again when they meet the conditions once more.

You can find this in the 'Entry Condition' area of the 'User Journey Settings' node.

![](/files/eVTSGUO5phs0AbkdyD8o)

{% hint style="info" %}
Users who are already in progress in the journey also re-enter when they meet the conditions. In this case, the existing user does not drop off from the journey.
{% endhint %}

## Frequency Capping Settings

Through frequency capping, you can ensure that users do not receive too many similar messages.

You can navigate to the frequency capping settings management page via the button in the user journey list.

![](/files/w5jRNml9DbTXHz2dDKdE)

Hackle provides both total frequency capping and tag-based frequency capping features. For more details on message frequency capping, see [here](/en/crm-marketing/push-message-guide/send/frequency-capping.md).

In a user journey, the frequency capping settings can be found at the bottom of each channel node.

![](/files/5qXyLcYM7bkHFkCpwNpa)

### How frequency capping settings work in a user journey

Frequency capping settings in a user journey work as follows.

#### Tags are set at the journey level

When configuring tag-based frequency capping, please note that tags can be set on the journey and are applied commonly to all channel nodes of the journey.

#### Sends are recorded at the channel node level

Send records are kept at the channel node level. If a user enters a 'Push Message' node and receives a push message, it is treated as having sent one push message. Kakao Message, Text Message, and Webhook work the same way.

For example, let's say you configured it as follows.

* Can receive a Kakao Message with the 'Promotion' tag up to 2 times per day
* The 'Promotion' tag is set on the user journey campaign

Let's say the user journey looks like the picture below, all nodes are affected by the frequency capping settings, and a user who entered has not yet received any Kakao Message with the 'Promotion' tag today.

![](/files/5kQ74Bx4T5km8yYDVy72)

![](/files/lZNiCUeV3VA7TihvX95R)

The user who entered the journey receives the first two messages, but cannot receive the last message due to the frequency capping settings. In this case, they move to the 'Send Failed' area.

#### Frequency capping settings in an in-progress journey

When you add/remove tags or change the frequency capping count in a journey that is already in progress, only users who enter the channel node after the change are affected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/advanced-settings.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.