Eligibility and re-entry

Control who receives an Experience and how often they can return.

You can control who receives an Experience and how often they see it. Show onboarding once, offer an upgrade whenever someone reaches a limit, or leave a few days between reminders.

The audience and re-entry settings work together. When a matching trigger arrives, Nuxie checks whether the customer belongs in the audience and whether they can start another Journey through the Experience.

Audience

Define your audience with customer conditions or select a reusable Segment. You can use Customer properties, Segment membership, subscription state, and Feature access.

For example, export_limit_reached might trigger an upgrade offer. Set its audience to customers without unlimited exports so people who already have that capability aren’t offered it again.

An offer also checks access before it appears and before checkout. This covers customers whose access changed after they entered the Journey. Offer eligibility explains what happens when they already own the access or it can’t be confirmed.

Re-entry policies

Choose Re-entry in the Experience settings. The policy applies to the customer and Experience across published versions.

One time

The customer can start the Experience once. This works well for an introduction or setup flow you don’t want to repeat. Once they’ve started, dismissing the screens or leaving before completion doesn’t give them another entry.

Every match

A later matching trigger can start another Journey. Use this when the Experience should remain available after a previous visit, such as an upgrade offer shown when a customer reaches an app limit.

Only one Journey for the same customer and Experience can be active at a time. A trigger received while that Journey is running doesn’t queue another visit.

Once per window

Set Every to a positive whole number and choose Minutes, Hours, Days, or Weeks. For example, 7 days allows the customer to return seven days after their most recent Journey started.

The interval counts from the start of the Journey. Completing it, dismissing it, or reaching its goal doesn’t restart the clock.

Returning after a conversion

Reaching a goal doesn’t permanently exclude a customer. Your audience and re-entry policy still decide whether they can return. An onboarding-complete property or Feature access condition can exclude someone after they finish setup or buy the offer.

Pausing the Experience or publishing an update doesn’t clear previous entries. A customer who has already used a one-time Experience remains ineligible under that policy.

Exit rules

You can also control when a Journey stops after it has begun. An exit rule can stop it when the customer reaches the goal or no longer matches its eligibility conditions.

The screen sequence already running finishes first, including any final steps you’ve included. Configure its dismissal path separately. Learn more about exit behavior.

Delivery history

Open the customer’s Journeys tab to see previous visits, their start times, and outcomes. This helps explain why an Experience can appear for a new customer but not for someone who has already used it.

Also check that the Experience is unpaused and within its schedule. A matching event can only start it when these settings, the audience, and re-entry rules allow it. Activity and Journey history explains how to follow an individual run.