Cloning is to duplicate an object, or make a copy of it.

Across the Optimize interface, you'll find instances of Copy / Clone - including when looking at Segments, Tags, Tests and Projects.

This article focuses on the latter two, and important things to know about the process.

Cloning tests produces a copy of the experience and places it in the same project.

This is particularly helpful for building iterations of experiments, where under no scenario would you want them both to be live and create a poor user experience.

You'll find this button on the dashboard screen.

Everything to do with your test will get carried over. Naming, variations, code, segments, custom data fields, which editor the test was made in, etc.

The state does not get copied over - all clones default to Pending mode.

It's important to understand which properties belong to a project - you will not be able to modify these independently in your clone.

If you need to modify these independently in your clone, consider cloning your project instead.

The above restrictions mean that it's sometimes more helpful to clone a test into a new project. For example - if you have built a test for one website or country, and need to create a clone that you can run on a new set of pages with its independent set of controls for code, going live, being deactivated etc.

You'll find this button in the dashboard screen:

All properties will get carried over, except for State - this will default to Pending.

Firstly, a user of your website/app can view one experience per project. By cloning into a new project, you open the door to them seeing both of your experiences, if they share the same segment, location, etc.

Also, note that as you've made a new Project with this action, you can change the Project name, description, location etc. independently, and without any knock-on effect on other tests. This was the core use case for building this feature.