Triggers & Goals

Define when a Journey may begin and what counts as success

A trigger makes an Experience eligible to start. A Goal action marks an authored success point inside its Flow. Both are versioned with the Project and reviewed during Publish.

Event triggers

Use an event trigger when the app knows the exact moment the Experience belongs. Fire the copied event through the SDK at that domain entry point:

NuxieSDK.shared.trigger("export_limit_reached")

The name must match the published trigger exactly. Optional property conditions can narrow the event to the intended situation.

An event being accepted does not force presentation. The SDK also considers live delivery, Journey state, re-entry, audience conditions, Experiment assignment, and presentation availability.

Segment triggers

Use a Segment trigger when entry depends on a maintained audience definition. Segment membership is server-seeded in the profile and may also use supported on-device context for evaluation.

Prefer an event trigger for a precise in-app moment and a Segment to qualify the audience. Avoid using a broad app-open event as a substitute for the real entry decision.

Goal actions

Place a named Goal action on the path that proves success. Publish requires at least one valid Goal.

Examples:

Put a purchase Goal after confirmed purchase completion, not merely on the Buy tap.
Put an onboarding Goal after the final useful step, not on the first screen.
Put a permission Goal on the authorized branch, not on the permission request.

If a Flow contains multiple distinct Goal names, the published goal definition records the required authored outcome. The Journey events remain the measurement authority.

Re-entry

Policy	Behavior
One time	The user can enter once.
Every time	A later qualifying trigger can start another Journey.
Once per window	Entry becomes available again after the configured window.

Choose re-entry from the user’s relationship with the moment. Onboarding is commonly one time; a feature-limit upgrade may be every time or windowed.

The Experience can end on its Goal, when the user stops matching, on either condition, or only through explicit authored behavior. Dismissal, expiration, supersession, failure, and operator cancellation are recorded as distinct Journey outcomes where applicable.

Verify the trigger

After connecting the app:

Confirm Connected in Nuxie.
Fire the exact published event.
Observe the trigger result in SDK debug logs or a trigger handler if needed.
Confirm the Experience appears.
Confirm Shown in Nuxie.