Overview

Deliver screens to users with campaigns

Campaigns

Campaigns turn your Studio flows into live experiences delivered to your users. A campaign is the container that holds published versions, controls when and to whom screens appear, and tracks how users interact with them.

What is a campaign?

A campaign connects three things:

• A trigger that decides when the campaign activates (an event, a segment, or both)
• A goal that defines what success looks like (a purchase, a signup, or any custom event)
• One or more versions built from your Studio flow

When you publish a project in the Studio, Nuxie creates (or updates) a campaign and builds a new version. That version is compiled into an optimized bundle and delivered from the edge to your users via the SDK.

Campaign lifecycle

Every campaign follows the same path from draft to live:

1. Author -- Design your paywall or onboarding flow in the Studio.
2. Publish -- Hit Publish. Nuxie creates a campaign (if one does not exist for this flow), queues a build, and generates a new version.
3. Build -- The build pipeline compiles your screens, styles, and logic into a bundle the SDK can render.
4. Live -- On the first successful build, the campaign is automatically promoted to live status and begins serving to users who match the trigger.

After the first publish, subsequent publishes create new versions under the same campaign. You can switch between versions at any time from the Versions tab.

Campaign status

A campaign has two possible statuses that control delivery:

When a campaign is live and has a built version, it is included in the configuration bundle synced from the server. Paused campaigns are excluded from delivery entirely.

Tip: The first time you publish a project, the campaign starts as paused and is automatically promoted to live once the build succeeds. After that, you control the status manually.

Auto-promotion

Nuxie automatically sets a campaign to live when its first build completes successfully. This means publishing a brand-new project results in a live campaign without any extra steps. For subsequent versions, the campaign retains its current status.

Dashboard

Manage campaigns from the dashboard under your app. The campaign list shows:

• Name -- The campaign name (derived from your project or set manually).
• Status -- Whether the campaign has a published version or is still in draft.
• Trigger type -- Event-based or segment-based, pulled from the active version.

Click any campaign to open its detail view with four tabs:

• Overview -- Trigger and goal configuration, conversion metrics, and a performance chart.
• Versions -- Version history and build status. Activate any built version with one click.
• Experiments -- A/B tests running within this campaign.
• Journeys -- A record of every user who entered the campaign.

Campaigns and the SDK

The SDK receives campaign configurations as part of the user profile, delivered from the edge. When a user's profile is fetched, Nuxie includes only the campaigns that are live and have a successfully built version. The SDK evaluates triggers locally and presents the appropriate screens.

For details on integrating campaigns in your app, see iOS SDK: Presenting Flows.

Next steps

• Triggers & Goals -- Configure when campaigns appear and how conversions are tracked.
• Versions -- Manage published versions and activate builds.
• Experiments -- Run A/B tests to optimize your paywalls.