Events and triggers

Choose the app event that starts delivery evaluation. Connect SDK triggers to targeting, track app behavior, and define conversion goals.

Delivery combines an app event, an eligible audience, and the Experience’s re-entry and exit rules. Use the event for the moment, and the audience for who should receive it.

Pick the moment in your app

For a paywall, that might be export_limit_reached. For onboarding, it might be account_created. Use the exact event configured for the Experience and send it from the corresponding app action using your SDK.

Keep authored events free of the $ prefix. Nuxie reserves that prefix for system events.

Send a trigger with your SDK

After SDK setup, send an event when the corresponding app action happens. For example, a photo app could introduce Collections when someone opens that feature. Configure the Experience with the same collections_opened event name.

import Nuxie

NuxieSDK.shared.trigger("integration_test")

import ai.nuxie.sdk.Nuxie

Nuxie.trigger("integration_test")

import { nuxie } from '@nuxie/react-native';

await nuxie.trigger('integration_test');

await nuxie.trigger('integration_test');

await Nuxie.Client.TriggerAsync("integration_test");

var result: NuxieResult = await Nuxie.trigger("integration_test")
if not result.ok:
    push_error(result.error.message)

Nuxie->Trigger(TEXT("integration_test"), {});

Use the client configured in your SDK integration guide. Completing this call confirms the operation according to that SDK’s contract; verify actual presentation on the device. The trigger still respects the audience and re-entry rules below.

Combine the event with targeting

A matching event starts delivery evaluation. The user must also meet the audience and re-entry rules before the Experience runs.

Use Customer properties and Segments to describe the audience. See Eligibility and re-entry for the remaining entry conditions.

Track other app behavior

Events can also describe actions you want to measure, such as finishing a workout. Keep event names stable and put context in event properties. An event property describes that occurrence; a customer property describes the user.

See Analytics and revenue to connect events with outcomes.

Conversion goals

Configure one event with property filters, or entry into or exit from one segment, as the Experience’s goal. Specify an attribution window. Experiences without a goal can publish and report views, interactions, and exits.

Examples:

• For a purchase, select the confirmed commercial outcome and relevant products. A trial start and a confirmed payment are different outcomes. Restore and discovery of existing ownership do not count as new acquisition.
• For onboarding, send an ordinary named event after the final useful step and select that event as the goal. Submit any retained responses before sending the outcome event.
• For permission, select an event emitted after authorization succeeds.

The attribution window starts at the Journey’s first actual screen display, or at entry for a screenless Journey. Each Journey converts at most once. Measurement continues after a skip, dismissal, or execution completion until the window ends. Already belonging to a segment is not a new segment transition.

Valid direct Journey attribution takes precedence. Otherwise, Nuxie selects the most recently shown eligible matching Experience within its window rather than crediting every matching Experience.

Re-entry

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.

Exit behavior

Configure exit conditions separately from conversion. When exit on goal applies, server progression stops. A currently running device portion keeps its screen and handlers, including any thank-you or setup steps, until that portion finishes normally; subsequent portions do not start. Dismissal remains explicit authored behavior. With exit on goal disabled, conversion does not stop execution.

Conversion does not permanently prevent another Journey. Current eligibility and frequency determine whether a later trigger can admit the customer.

Offer eligibility

An onboarding Journey may be useful to a subscriber even when its last screen sells access they already own. Check the specific access offered immediately before showing the offer and before checkout, and provide explicit routes for already-owned and unknown access. An upgrade checks the higher-tier access.

Nuxie uses supported local purchase evidence together with access state to avoid redundant offers before server reconciliation. Existing ownership can bypass an offer without creating conversion. If access remains unknown, an optional offer can be skipped; a protected feature can show retry or unavailable behavior without granting access.