Triggers & Goals

Control when campaigns show and what success looks like

Triggers & Goals

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

Triggers

A trigger is the condition that causes a campaign 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 campaign 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.

swift

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

The SDK evaluates event triggers locally. When a tracked event matches a campaign 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 campaign 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 campaign 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 campaign. Goals power the conversion metrics on the Overview tab and determine when a journey is marked as converted.

Defining a goal

Goals are configured at the campaign level. By default, new campaigns use a paywall goal that tracks purchases. You can customize the goal to match any event or outcome that matters to your business.

Common goal types:

Purchase -- The user completes a subscription or one-time purchase.
Custom event -- The user fires a specific event you define (e.g., account_created, trial_started).

Goal windows

A goal window sets the time frame in which a conversion counts. If a user triggers the campaign on Monday and your goal window is 7 days, any goal event within that week is attributed to the campaign.

Window setting	Behavior
No window	The goal can be met at any time after the journey starts.
N hours/days	The goal must be met within the specified period after the journey starts.

Goal windows help you measure the true impact of your campaign by limiting attribution to a reasonable time frame.

Re-entry policies

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

Policy	Behavior
Once	The user sees the campaign at most one time. After they complete or exit, they never re-enter.
Every time	The user can re-enter the campaign each time the trigger fires.
Once per window	The user can re-enter after a cooldown period has elapsed since their last journey.

Choose "Once" for onboarding flows 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 a campaign 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 flow without meeting the goal.
Expired -- The goal window elapsed without the goal being met.
Cancelled -- The user dismissed the flow or navigated away.

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

How triggers and goals work together

When a campaign is live:

The SDK receives the campaign configuration, including the trigger and goal definition.
When the trigger fires (event match or segment membership), a journey starts and the flow is presented.
As the user progresses through the flow, Nuxie tracks their actions.
If the user meets the goal within the goal window, the journey is marked as converted.
If the user exits without meeting the goal, the exit reason is recorded.

Conversion data flows into the campaign 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.