Versions
Manage published versions and activate builds
Each publish from the Studio creates a new version for your experience. 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 experience. Each version belongs to exactly one experience, and experiences 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:
- Nuxie creates a new version for the experience (v1, v2, v3, and so on).
- A build job is queued to compile the version into an optimized bundle.
- The new version is set as the experience’s active version.
- 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 experience detail view shows the current build status for each version:
| Status | Meaning |
|---|---|
| Ready | The build succeeded. This version can be served to users. |
| Building | The build is in progress. The version is not yet available. |
| Failed | The build encountered an error. Check the build logs for details. |
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:
- Open the experience detail view and go to the Versions tab.
- Find the version you want to activate. It must have a Ready build status.
- Click the menu on the version row and select Make Live.
The experience 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 experience at an existing built version. This makes rollbacks instant.
Version history
The Versions tab lists every version ever published for the experience, 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 an experience.
Edge delivery
When a version is activated and its experience 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 experiences and have a completed build are included in delivery.
For details on how the SDK receives and renders experiences, see iOS SDK: Presenting Experiences.
Next steps
- Triggers & Goals – Configure when the experience triggers and what success looks like.
- Experiments – Run A/B tests across variants.
- Journeys – Track how users progress through your experiences.