Versions and updates
Update a live Experience without another app release.
You can change a published Experience without shipping another app release. Edit the screens, copy, or behavior, then publish an update when you’re ready. Your customers keep receiving the live version while you work.
Each publication saves a version, so you can try a change on your device first or return to an earlier version later.
Publish an update
Prepare the update
Open the Experience, make your changes, and try them in Preview. Click Publish to see what changed and the delivery settings that will go with the update.
Try it on your device
Under Publish to, choose Your device first to publish to the preview environment. Run your development build with the pk_test_ key shown under Debug builds in Connect your app, then send the Experience’s trigger. Your release build uses the pk_live_ key and continues receiving the production version while you try the update.
Go live
After testing, select Go live to make the update available for production delivery. Testing in your app covers the connected actions, purchases, and eligibility rules to try before that step.
If you’re ready to release it straight away, choose Everyone and select Publish update. Nuxie keeps the previous version running until the new build succeeds. If the build fails, customers continue receiving the previous version.
Experience updates use the capabilities already integrated into your app. A new app action or integration still needs the corresponding app code before an Experience can use it.
Delivery of updates
The SDK picks up published changes when it refreshes. Someone who’s already using an Experience can finish their Journey on the version they started with; publishing an update won’t replace the screen they’re looking at.
A new eligible Journey uses the available published version. If you’re testing an update with the same customer, their audience and re-entry rules still apply. See Testing in your app.
Version history
Open the published Experience’s Versions tab to see its previous publications. Each row has a version number, how long ago it was published, and its build status.
Building means Nuxie is still preparing the version. Ready means it can be activated, while Failed means the build didn’t finish successfully. The Live badge identifies the active version for your selected environment.
Restore an earlier version
Open a ready version’s row menu and select Make Live. That version becomes the one delivered to customers. Your current draft stays as it is, so you can continue working on a correction without losing your edits.
Make Live is available for a ready version that isn’t already live. As with any update, it doesn’t replace screens in a Journey already underway.
Experiment updates
The publish panel points out Experiments you’ve modified or removed. Changes affect future delivery, while customers already in a Journey keep the variant they were assigned.
An Experiment keeps its original plan and any later changes to the analysis. If you want a fresh comparison using the same variants, choose Restart test. Copy test creates a separate test instead. Both actions publish the Experience, and results from the different runs stay separate.
See Creating an experiment for restarting and copying tests, and Goals and results for changing what a test measures.