How versions work
A campaign links to one Experience Release.
Every publish creates a new immutable version.
Editing a published campaign creates a working copy that becomes the next version when you publish.
Create and manage versions
Duplicate a campaign to clone its content and increment the version number.
Use clear names so history is easy to follow, for example: Summer Promo v3 EN+FR.
Archive versions you no longer use. They remain available for history and manual rollback.
Change logs and diffs
The CMS auto generates diffs between campaign versions so you can see what changed.
Experience authors can add a release changelog to provide context that appears alongside your campaign history.
Preview your campaign
Click Preview to open a shareable link that renders the experience with your current draft content.
Preview supports locale switching so reviewers can check translations.
Use preview on a kiosk or desktop to verify layout, asset quality, and interactions.
(Click on the "link" icon to preview the campaign)
Roll back to an earlier version
Open the campaign history, select the previous version, then Publish it again.
There is no automatic expiry. To change what is live, publish the version you want.
Good practice
Save often and validate before sharing a preview so reviewers see a clean draft.
Keep images under 500 KB where possible and total campaign size under 20 MB unless using video.
When coordinating larger changes, create a duplicate, gather approvals via preview, then publish.
Roles and permissions
Admins and Managers can create, edit, preview, publish, archive, and roll back.
Viewers can open previews and read history but cannot modify campaigns.