Experience Versioning

In Contentstack Personalize, experience versioning allows you to create and manage multiple versions of your experiences. This can be useful for a variety of reasons, such as:

• Testing and Optimization: It allows you to create and test multiple variations of an experience (A/B or multivariate testing) to determine the most effective one, leading to improved performance and conversions.
• Controlled Rollouts: You can gradually roll out an experience to a limited audience before releasing it to everyone, minimizing potential risks and ensuring a smooth transition.
• Flexibility and Iteration: You can pause an experience to make changes, fix bugs, or address issues without disrupting the user journey, enabling iterative improvements and agile development.
• Seasonal Campaigns: Create and schedule different versions of an experience for specific holidays or events.
• Data-Driven Decision Making: By tracking the analytics of different versions, you can gather insights and make informed decisions based on data, optimizing your personalization strategies for better results.

Experience States in a Personalize Project

An experience can have one of the 4 following states:

• Draft: The initial state of an experience. In this state, the experience is not yet live and is not visible to visitors to your site. You can use this state to create and configure your experience, and to test it on a staging or development environment (after activating the experience).

  Note: At any given time, only 1 draft can exist for an experience.

• Active: The state in which an experience is live and visible to visitors to your site. In this state, the experience will run according to the Variants you have configured along with the Entry Variants published via the CMS, and you will be able to track its analytics in the Experience dashboard.

  Note: When you activate an experience draft, the previous active version (if available) is automatically archived.

• Paused: The state in which an activated experience is temporarily stopped. In this state, the experience will not run and the personalization set in the experience will not be visible to the visitors to your site. You can use this state to make changes to your experience or tweak your content personalization strategy.

  Note: When an experience is paused, the Base Entry of the Entry Variant(s) is displayed to your visitors.

• Archived: The state in which a previously active experience is stored but no longer active. You can view the Analytics of an archived experience version via the Version History icon in the right panel and then clicking the Archived version.