Optimizely will be sunsetting Full Stack Experimentation on July 29, 2024. See the recommended Feature Experimentation migration timeline and documentation.

Dev GuideAPI Reference
Dev GuideAPI ReferenceUser GuideGitHubNuGetDev CommunitySumbit a ticketLog In
GitHubNuGetDev CommunitySumbit a ticket
These docs are for v2.0. Click to read the latest docs for v3.0.

Set up another Full Stack project

A project is a way of managing experiments within a single application or service that you are developing in. Your account already includes a Full Stack project, so creating another project is an optional step. In most cases, we recommend setting up one project for each application or service. Consider setting up separate projects for different staging environments.

All Full Stack projects look similar, regardless of language. Optimizely provides language-specific code samples via the interface and also keeps you informed of SDK updates. In practice, our Full Stack SDKs are language agnostic, you can use a datafile from any Full Stack project type to initialize an Optimizely client within your app, regardless of which language you use for your project.

Create a Full Stack project

To create another Full Stack project:

  1. In Optimizely, click Create New Project.
  2. Name your new project and optionally add a description.
  3. Click Create Project.
    Congratulations! You have created a new Full Stack project. Now you can create experiments in your new project.
1390

Create Full Stack projects using multiple SDKs

You can use multiple SDKs to run experiments that span different parts of your technology stack. Use any Optimizely Full Stack SDK in any Full Stack project, even if they do not match your primary programming language. Select the primary language based on the application where you will assign visitors to experiments.

For example, imagine you are running experiments in your Python backend and tracking events in a web browser via JavaScript. In this example, you would use Python as the primary language because t your experiment code runs.

📘

Note

You are always free to track conversion events for your experiments in any other part of your technology stack in any language.