> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/journeys-and-automation/journey-settings/journey-exit-criteria.md).

# Journey 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>Journey 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 performed is 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 criteria. 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
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://support.growlytics.in/journeys-and-automation/journey-settings/journey-exit-criteria.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.