Skip to main content
menu_icon.png

Everything you need to learn Optimizely X in one place: See our resource pages for Web Experimentation and Personalization.

x
Optimizely Knowledge Base

Make the transition to Optimizely X Web

RELEVANT PRODUCTS:
  • Optimizely X Web Experimentation
  • Optimizely X Web Personalization
  • Optimizely X Web Recommendations
  • Optimizely Classic

THIS ARTICLE WILL HELP YOU:
  • Transition your account from Optimizely Classic to Optimizely X
  • Understand which features are migrated automatically and which aren't

The first step in switching from Optimizely Classic to Optimizely X Web Experimentation is easy. Account administrators can enable Optimizely X in the snippet without making any code changes.

This article walks you through the process of transitioning experiments and projects to Optimizely X at a high level and feature by feature.

Curious about what's new in Optimizely X? Here's a comparison between Optimizely Classic and X.

Want to move an existing Optimizely Classic experiment into X? Here's a walkthrough.

Transition methods

Here are two approaches to making the switch to Optimizely X.

Do you have a QA or staging environment?

Yes.

We recommend the hard switchoverThis approach allows you to avoid running the heavier bundled snippet on your production site.

Test any templates you'd like to migrate to Optimizely X in your staging project.

With this approach, you use the lightweight standalone snippet to run Optimizely X only.

No.

We recommend the phased rolloutA phased rollout allows you to migrate slowly.

Finish running Optimizely Classic experiments and ease onto the new tech stack.

You'll use the bundled snippet to run Optimizely X and Optimizely Classic at the same time.The bundled snippet is ~50kB larger to incorporate both configurations, which may affect speed.

You will need Administrator privileges to enable Optimizely X in the snippet settings.

Hard switchover

Here's a  guide to switching to Optimizely X, if you have both staging and production environments. 

Staging project:

  1. Enable the bundled snippet for both Optimizely Classic and X.

  2. Pause all Classic experiments in the staging environment.

  3. Learn to create and QA experiments in Optimizely X.

    We recommend that you join a one-hour, interactive virtual training session to learn the basics of Optimizely X Web Experimentation.

  4. Next, create pages and events for your site.

    Optimizely X introduces pages and events as reusable templates for URL targeting and goals, so you can set up experiments quickly and gather data on visitor behaviors, even when an experiment isn't running. We recommend that you hardcode your top 10 metrics as custom events, so you can easily reuse them without additional QA.

  5. Update any custom integrations you may have been using Optimizely Classic .

  6. Do you have any long-running "hot fixes" or "experiments" where 100% traffic is sent to a single variation? Rebuild these if you'd like to keep running these after switching to X.

    Your visitors' experience will be continuous, but any results you're collecting will restart when you switch.

Production project:

  1. Enable the bundled snippet for both Optimizely Classic and X.

  2. Duplicate your long-running "hot fixes" or "experiments" with 100% traffic to a single variation in Optimizely X.

  3. Create additional pages and events for important parts of your site and key visitor actions.

  4. If you have any updated custom integrations, push them to production.

  5. Pause your experiments in Optimizely Classic.

  6. Enable the Optimizely X standalone snippet to complete the transition.

  7. Build and run experiments in Optimizely X.

Phased Rollout

Here's a guide to switching to Optimizely X if you build, QA, and run all experiments on your production environment. 

  1. Enable the bundled snippet for both Optimizely Classic and X.

  2. Learn to create and QA experiments in Optimizely X.

    We recommend that you join a one-hour, interactive virtual training session to learn the basics of Optimizely X Web Experimentation.

  3. Create pages and events for your site.

    Optimizely X introduces pages and events as reusable templates for URL targeting and goals, so you can set up experiments quickly and gather data on visitor behaviors, even when an experiment isn't running. We recommend that you hardcode your top 10 metrics as custom events, so you can easily reuse them without additional QA.

  4. Update any custom integrations you may have been using Optimizely Classic .

  5. Do you have any long-running "hot fixes" or "experiments" where 100% traffic is sent to a single variation? Rebuild these if you'd like to keep running these after switching to X.

    Your visitors' experience will be continuous, but any results you're collecting will restart when you switch.

  6. Build and run experiments in Optimizely X.

  7. Once remaining experiments have run to completion in Optimizely Classic, pause them.

  8. Enable the Optimizely X standalone snippet to complete the transition.

Transitioning feature by feature

Some features transition from Optimizely Classic to Optimizely X automatically and some need to be manually transitioned.

Pages

In Optimizely X, you'll define URL targeting on pages. Pages are reusable "templates" that can be used across different campaigns and aren’t tied to any single experiment until you add it to the campaign. When manually setting up a page in Optimizely X, select an activation mode for each page from the options shown below:

To set up two experiments with the same URL targeting (for example, across all product detail pages) but different activation modes, you'll need to create two separate pages.

Events

In Optimizely X, goals are called events. They're now more powerful and can be used across different campaigns.

Optimizely Classic goals don't show up in Optimizely X.

For custom events coded for your site, the POST request is still sent. You don't need to make any code changes. Simply add the custom event in Optimizely X:

  1. Select the Implementation dashboard, then click Create New Event.

  2. Then select Custom event

The Optimizely Customer Success team can help you migrate your custom events. If you'd like all your events migrated programmatically, please submit a support ticket.

Audiences

Audiences are shared between Optimizely Classic and Optimizely X. All audiences created in Optimizely Classic will show up in Optimizely X and vice versa.

However, Optimizely Classic audiences that include custom tags don't work in Optimizely X. This audience type has been deprecated.  In Optimizely X, you can use a combination of pages and custom attributes to handle complex targeting requirements.

Also, Optimizely X audiences that include visitor behaviors (a feature available only through Optimizely X Web Personalization) don't work in Optimizely Classic.

API

Optimizely X uses a new version (v2) of the REST API. If you use the v1 REST API, use our developer documentation to update to v2.

There's also a new version of the JavaScript API. Most JS API methods from Optimizely Classic are backwards-compatible. See our developer documentation for more details.

Integrations

Our most popular analytics integrations work in both Optimizely Classic and Optimizely X. Audience and data management platform (DMP) integrations also work in both.

We're actively building more integrations. Check our list of current integrations.

Experiments and results

Experiments in Optimizely Classic and Optimizely X live on their own platforms. Optimizely X experiments don't show up in Optimizely Classic, or vice versa; this means experiments won't be automatically migrated. However, you'll always be able to see your Optimizely Classic experiments and results -- even if you've enabled the Optimizely X standalone snippet.

Here's how to build your Optimizely Classic experiment in Optimizely X.