---
title: "Journey Entry Capping"
slug: "journey-entry-capping"
description: "Explains Journey Entry Capping in Insider Architect: limiting how often users enter journeys to curb over-messaging, and how it differs from eligibility."
tags: ["entry capping", "journey entry capping"]
updated: 2026-07-09T15:31:05Z
published: 2026-07-09T15:31:05Z
canonical: "academy.insiderone.com/journey-entry-capping"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://academy.insiderone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Journey Entry Capping

When you have more than one journey, you may not want your users to enter these journeys even if they meet the starter conditions. Journey frequency capping helps you limit the number of entrances to all your journeys.

Users may enter the welcome journey, browse abandonment journey, cart abandonment journey, post-purchase journey, or cross-selling journey. Entry capping helps prevent user annoyance by avoiding long journeys and excessive messaging.

Journey Frequency Capping considers when a user exits a journey by completing it or dropping it. Each exit activity is counted as 1 ticket. Let's say you set the frequency capping as "once a day." When a user exits your journey, they cannot enter the same journey the same day even if they meet the starter condition.

![](https://cdn.document360.io/c6df4583-da94-4cb2-bb8a-be0cbdd11109/Images/Documentation/eeb8552d-90cd-4bee-ab39-257046c011ac.png)

You can reach Journey Frequency Capping through **Architect** > **Settings**. You can specify the maximum number of entrances and the duration. Also, you can override that frequency capping on the launch settings of your specific journey, and you can define another one.

Your title goes hereWhile entry capping limits a user's entrance to the journey, channel frequency capping limits the number of messages they can receive. If a user is capped by the entry capping, they do not enter the journey. If they are capped by frequency capping, the corresponding element is skipped, and the user proceeds to the next element in the journey. 

## Journey Entry Capping vs. User Eligibility

**User** **Eligibility** enables you to choose whether a user can start and finish the journey for a single time as **Only One Time** or more than once whenever they become eligible as **Multiple** **Times**.

**Journey** **Entry** **Capping** considers the case where the user exited the journey by completing it or dropping from it. Each user exit activity counts as 1 ticket. When the user exits the journey, and there is an entry capping on all journeys, such as “the user can enter the journeys 1 time in 1 day”, the user will not enter the journey once they fulfill the [starter](https://academy.useinsider.com/docs/starter-elements) condition of any journey again in 1 day.

While **eligibility** controls the duration, **journey** **entry** **capping** considers the entrances in a specified duration. Eligibility does not take users on the journey again during the specified period, while journey entry capping does not take users on the journey more than a specified number of times within the given duration.

Let's take a look at this example.

> You have a cart abandonment journey. The eligibility duration is five days. Journey Entry Capping is three times in three days.
> 
> The user enters and exits the journey today. They fulfill the same journey's [starter](https://academy.useinsider.com/docs/starter-elements) conditions again two days after exiting the journey. Even if the entry capping allows that user to enter the journey, the eligibility will not allow them to enter since it is set for five days and it has been only two days after the user exited the journey.

## Related

- [Override General Entry Capping for Architect Journeys](/override-general-entry-capping.md)
- [Architect Starter Elements](/architect-starter-elements.md)
- [Exit Criteria for Journeys](/exit-criteria-for-journeys.md)