Ctrlk

Entry rules

Entry rules define who enters the Journey.

Entry rules are configured on the Start step.

Start step panel showing no entry rules defined and an Add entry rule button
The Start step panel — click + Add entry rule to define who enters the Journey.

What entry rules do

An entry rule decides whether a contact is allowed to join the Journey.

If you configure multiple rules, the Journey uses an operator:

  • OR — a contact enters if any rule matches

  • AND — a contact enters only if all rules match

The operator selector appears only when two or more rules are defined.

Start with one entry rule. Add a second rule only when the business logic genuinely requires it. Combining many rules with AND makes it harder to predict how many contacts will enter.

Available entry rule types

Audience entry

Use this when the contact should enter because they belong to a specific DinMo audience.

Configuration:

  • Select the audience from your Customer Hub

Best for:

  • Lifecycle audiences already managed in DinMo (onboarding cohort, at-risk segment, high-value customers)

  • Flows based on stable group membership that does not change frequently

Event occurrence

Use this when the contact should enter because a tracked event happened.

Configuration:

Field
Description

Event table

The event model to use for the trigger

Minimum occurrences

Optional — require the event to happen at least N times

Event conditions

Optional — filter by event properties (e.g. only purchase events above a certain amount)

Best for:

  • Behavior-driven entry such as purchase, signup, trial start, or cancellation events

  • Flows that should trigger on a specific user action rather than group membership

Limits and operating rules

Start step panel showing a configured entry rule with an audience selected, locked because the Journey is Active, and Allow Journey Repeat toggle
Entry rules are locked when the Journey is Active. Pause the Journey to make changes.
Rule
Value

Maximum entry rules per Journey

10

Minimum required before publishing

1 valid rule

Can edit while Active

No — locked while Journey is Active

Allow Journey Repeat

Allow Journey Repeat lets a contact re-enter the Journey after they have already completed or exited it.

Use this setting only when re-entry is a deliberate part of the lifecycle design.

If Allow Journey Repeat is enabled and the first activation happens immediately (no Wait before Activate), contacts who complete quickly may re-enter and be reactivated faster than intended. Add a Wait step before the first Activate when re-entry is enabled.

Best practices

  • Start with one clear rule before combining multiple rules.

  • Use OR only when the business meaning is unambiguous — "enter if they signed up OR if they made a purchase" should be a deliberate choice, not a default.

  • If re-entry is enabled, add a Wait before the first Activate unless immediate repeat activation is intentional.

  • Use Audience entry when the population is managed as a DinMo audience. Use Event occurrence when the trigger is a specific user action.

Related pages

Last updated