# Journey Settings

This article describes the different journey settings available and how you can configure them.

<figure><img src="/files/jva7FdIvB5LI5Q4rp2wF" alt=""><figcaption><p>Journey Settings</p></figcaption></figure>

### Frequency Capping

Configure if you want to follow frequency capping for this journey's campaigns or not. You can set frequency capping for promotional campaign messages, and for transactional campaign messages, you can ignore frequency capping.

For example, for 'Abandoned Cart' journeys, you can enable frequency capping. But for the 'Ask for Review' journey, you can disable frequency capping.

Know more about Frequency Capping: [Frequency Capping](/account-settings/campaign-settings/setting-up-frequency-capping.md)

### Revenue Tracking

Decide if you want to track revenue for this journey or not. This part is very important since Growlytics, by default, activities performed by customers in response to the last campaign message.&#x20;

<figure><img src="/files/azqAPRbFS39BoJbB3P1M" alt=""><figcaption><p>Revenue Tracking is automatically selected for every journey</p></figcaption></figure>

If the last message is of a 'Non-Follow-Up' Journey, your conversion tracking for other campaigns/journeys will not behave properly. For example, you don't need to enable revenue tracking for a 'Purchase Thank You' Journey.&#x20;

<figure><img src="/files/LQcrYJKBhqFbHIHjKX2U" alt=""><figcaption><p>No need to enable revenue tracking for 'Non Follow-Up' journey</p></figcaption></figure>

### Entry Audience Filters

Set conditions for the customer to enter the journey. This is useful when you are targeting customers of a particular segment.

For example, you have set up a campaign where if the customer has not purchased anything in the last 45 days, they receive an email. However, in this particular journey, you don't want to include a customer who has canceled orders, in the journey. For such a scenario, you can apply a filter of 'Not performed Order Cancelled in the last 45 days'.

<figure><img src="/files/U6u5SeJhIxW982nniWJO" alt=""><figcaption><p>Entry Audience Filter</p></figcaption></figure>

### Exit Criteria

Use Journey Exit Criteria to remove customers from journeys who no longer fit the journey's goal or for whom the journey's content is no longer relevant. This will help make the statistics more meaningful.

<figure><img src="/files/WeCrueV16fJ5yRIs6Yj4" alt=""><figcaption><p>Exit Criteria</p></figcaption></figure>

#### Exit Criteria Use Cases:

* In the 'Abandoned Cart' journey, when a customer makes a purchase, remove the customer from the journey.
* You have a journey to ask for a review after 15 days. But if the customer has already given a review after 2 days, remove the customer from the journey.
* You have a retention journey to ask for a purchase after 45 days. But if the customer has already made a purchase after 45 days, remove the customer from the journey.

#### How to set the exit criteria?

There are two ways to set exit criteria:

1. **When an event is performed by the customer:** Use this option to remove a customer from a journey when he performs any event. For example, in the 'Abandoned Cart' Journey, you can set the 'Purchase' event as an exit criterion. This means whenever a customer makes a purchase, he will be removed from the journey and will no longer receive 'Cart Follow-Up' messages.
2. **When a customer becomes part of a segment:** Use this option to remove a customer from a journey when he becomes part of the segment.

#### Exit Criteria Considerations

* Customers that are removed via exit criteria are logged, at each step of a journey. This will help you identify how many customers were removed using the Exit Criteria.&#x20;


---

# 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://support.growlytics.in/journeys-and-automation/journey-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.