Versions

Manage published versions and activate builds

Versions

Each publish from the Studio creates a new version for your campaign. Manage versions, track build status, and choose which version is live.

What is a version?

A version is a published snapshot of your project at publish time. It contains the compiled screens, interactions, triggers, and logic that the SDK needs to render your campaign. Each version belongs to exactly one campaign, and campaigns can have many versions.

Think of versions as releases. Version 1 is your initial publish. Version 2 is an update with tweaked copy. Version 3 adds a new screen. You can always roll back to a previous version.

Publishing creates a version

When you publish a project in the Studio:

1. Nuxie creates a new version for the campaign (v1, v2, v3, and so on).
2. A build job is queued to compile the version into an optimized bundle.
3. The new version is set as the campaign's active version.
4. Once the build succeeds, the bundle is synced from the server and delivered to the SDK.

Each publish always creates a new version. This gives you a complete history of every change.

Build status

Every version goes through a build process after publishing. The Versions tab in the campaign detail view shows the current build status for each version:

Only versions with a Ready status can be activated as the live version.

Activating a version ("Make Live")

The most recently published version is automatically set as the active version. If you want to switch to a different version -- for example, to roll back to a previous release -- use the Make Live action.

To activate a version:

1. Open the campaign detail view and go to the Versions tab.
2. Find the version you want to activate. It must have a Ready build status.
3. Click the menu on the version row and select Make Live.

The campaign immediately starts serving the newly activated version. The updated bundle is synced from the server, and the SDK picks up the new version on the next profile refresh.

Tip: "Make Live" does not create a new version. It simply points the campaign at an existing built version. This makes rollbacks instant.

Version history

The Versions tab lists every version ever published for the campaign, ordered by version number. For each version, you can see:

• Version number (v1, v2, v3...)
• Build status (Ready, Building, or Failed)
• When it was created
• Whether it is the current live version

This history gives you full visibility into every change published to a campaign.

Edge delivery

When a version is activated and its campaign is live, the compiled bundle is synced from the server and delivered to the SDK at the edge. The SDK receives the bundle as part of the user profile response. Only versions that belong to live campaigns and have a completed build are included in delivery.

For details on how the SDK receives and renders flows, see iOS SDK: Presenting Flows.

Next steps

• Triggers & Goals -- Configure when the campaign triggers and what success looks like.
• Experiments -- Run A/B tests across variants.
• Journeys -- Track how users progress through your campaigns.