Skip to main content

Hey, Optimizely X users! Don't waste time looking for resources about Optimizely X Web Experimentation. We've got them for you here

Optimizely Knowledge Base

Manage projects in Optimizely X Web

This article is about Optimizely X Web. If you're using Optimizely Classic, check this article out instead.
relevant products:
  • Optimizely X Web Experimentation
  • Optimizely X Web Personalization
  • Optimizely X Web Recommendations

  • Create and manage Projects and Experiments
  • Add, remove, duplicate, and archive Projects or Experiments
  • Create separate projects for development and production environments 

Once you start using Optimizely, you'll have a growing number of experiments and campaigns to manage. Projects help you keep everything organized.

Projects let you subdivide your Optimizely account into little territories: for different sections of a website, multiple sites, or different products. (If you're using Optimizely X Full Stack, projects work a little differently.)

Each project has its own: snippet, set of experiments, and set of collaborators.

Create a new project

  1. In the sidebar, select Switch Project

  2. Select New Project.

  3. Then, choose Create Web Project.

  4. Then, name your project (you can always change it later) and confirm Create Project.

Rename, archive, and unarchive projects

  1. Select Manage Projects.

  2. Choose your project.

    To rename a project, hover to select the name and edit. 

    To change the status of an active or inactive project, select Archive or Unarchive.

Development and production environments

For many organizations, separate development and production environments allow new features to be built and tested without disturbing production traffic. Use Optimizely projects to separate experiments in your development environment from those in your production environment.

Each project will need its own snippet:

  1. Start by creating a new project for your development environment. Grab the snippet for this project, and install that in the head of your development environment pages.

  2. Next, create a production project with its own snippet. If you wish, you can restrict access to this project to a certain number of "gatekeepers."

You can use the following process to create and run experiments on separate environments:

  1. Create an experiment in your development environment. If your development URLs are the same as those used for your production environment, make sure your production environment does not use the snippet from your development project.

  2. Run and QA your new experiment to make sure that everything works the way you'd like.

  3. Change the targeting of your new experiment to ensure that it runs properly on your production environment URLs.

  4. Duplicate your experiment to your production project. (Only someone who has access to both projects can complete this step.)

Now, start the experiment in your production project when you're ready!