Triggers & Goals

Control when experiences show and what success looks like

Triggers decide when an experience appears. Goals define what a successful outcome is. Together they power targeting and conversion tracking for every experience.

Triggers

A trigger is the condition that causes an experience to activate for a user. You configure triggers in the Studio on the starting point of your project. When you publish, the trigger is compiled and attached to the version.

Event triggers

An event trigger activates the experience when the SDK receives a specific event. For example, you might trigger a paywall when the user fires a feature_locked event or completes onboarding.

// In your app, fire the event that activates the experience
Nuxie.track("feature_locked")

The SDK evaluates event triggers locally. When a tracked event matches an experience trigger, the version is presented immediately.

You can add property filters to narrow the match. For example, trigger only when feature_locked fires with feature_name == "export".

Segment triggers

A segment trigger activates the experience when a user belongs to a specific segment. This is useful for targeting audiences like “free users” or “users who haven’t opened the app in 7 days.”

Segment triggers are evaluated as part of the user profile. When the profile is fetched, Nuxie checks segment membership and includes the relevant experience if the user qualifies.

See Segments Overview for how to create and manage segments.

Goals

A goal defines what counts as a successful conversion for your experience. Goals power the conversion metrics on the Overview tab and determine when a journey is marked as converted.

Defining a goal

In Studio, goals are authored with explicit Goal actions inside the experience. Add a Goal action at the point where success is actually confirmed.

Common patterns:

• Paywall conversion – Put the Goal action on the $purchase_completed interaction, not on the purchase action itself.
• Onboarding completion – Put the Goal action on the final CTA or completion event.
• Permission success – Put the Goal action on the permission-granted interaction.

Each Goal action has a name. If your experience uses one named goal, hitting it converts the journey. If your experience uses multiple distinct goal names, the journey converts once all of them have been reached.

When you publish, Nuxie compiles those Goal actions into the experience’s lower-level goal definition automatically.

Re-entry policies

Re-entry controls whether a user can enter the same experience more than once. This is configured at the experience level.

Choose “Once” for onboarding experiences that should only appear on first launch. Choose “Every time” for paywalls that should reappear whenever the user hits a locked feature.

Exit conditions

An exit condition determines when a journey ends without the goal being met. Exit conditions prevent users from being stuck in an experience indefinitely.

Common exit conditions:

• Goal met – The user achieved the goal. The journey is marked as converted.
• Completed – The user reached the end of the experience without meeting the goal.
• Expired – The experience expired before the goal was met.
• Cancelled – The user dismissed the experience or navigated away.

The exit reason is recorded on each journey and visible in the experience dashboard. See Journeys for details on how exits are tracked.

How triggers and goals work together

When an experience is live:

1. The SDK receives the experience configuration, including the trigger and goal definition.
2. When the trigger fires (event match or segment membership), a journey starts and the experience is presented.
3. As the user progresses through the experience, explicit Goal actions can fire on the authored success paths.
4. If the user reaches all required Goal actions, the journey is marked as converted.
5. If the user exits without meeting the goal, the exit reason is recorded.

Conversion data flows into the experience Overview tab, where you can see total conversions, conversion rate, and average time to convert.

Next steps

• Versions – Understand how trigger configuration is compiled into versions.
• Journeys – See how individual user progressions are tracked and reported.
• Segments Overview – Create the audience segments used in segment triggers.