Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideProduct feedbackGitHubNuGetDev CommunityDoc feedbackLog In

Migrating from Optimizely Classic Web

This topic describes how to migrate from Optimizely Classic Web to Optimizely Web Experimentation.

If you have any questions about migrating to Optimizely Web Experimentation, you can submit a ticket to the developer support team. We'll be happy to assist you.

We're excited to release Optimizely API (2.0), providing read-and-write access to your Optimizely Web Experimentation data and read-only access to your Classic Web data. This version of our REST API has been completely re-built from the ground up. This API has been written to support the new data models in Optimizely Web Experimentation causing the endpoints to vary from Optimizely API (1.0). We have also incorporated many new features requested by developers like pagination, enhanced error handling and improved input validation. This guide will walk you through the key differences between versions.

First, we've added the Campaign model, which is a collection of Experiments that share the same objective. Campaigns should now be leveraged when creating a personalization campaign that shares the same focus. With this addition, Projects will now consist of Experiments and/or Campaigns.

In Optimizely API (2.0), variations are the property of experiments. Variations cannot be queried outside of the experiment context, so there is no /variations endpoint like there was in the Optimizely API (1.0). We have also introduced the concept of a Page that controls where experiments can run. Previously, this was defined in url_conditions in an experiment.

The notion of Goals has transformed into Metrics and Events. Events most closely resemble goals, as they are specific actions you can track. For example, an Event could be button clicks within a page or page views. Metrics define how to add up the data we receive from Events. Audiences remain the same between versions.

In Optimizely API (1.0), you could authenticate with tokens that you could generate on Those "Classic Tokens" are replaced by "Personal Tokens" in the v2 API.

Migration Checklist

If you have any questions, you can submit a ticket to the developer support team. We'll be happy to assist you.

Mapping Optimizely API (1.0) to Optimizely API (2.0)

Optimizely Web ExperimentationOptimizely Classic Web
CampaignsNew in Optimizely Web Experimentation
The field variations on ExperimentsVariations
PageNew in Optimizely Web Experimentation. Previously lived in edit_url and urls_condtions in the Experiment object.
Events, metricsGoals
Experiment ResultsExperiment Results
Campaign ResultsNew in Optimizely Web Experimentation