Environments are where you deploy experiments, either into production or for QA. Other project changes apply to all environments.
Evolv provides a default “Production Environment”. You can create and define additional environments according to how your deployment process works.
Additional environments are used to QA and verify that experiments work properly in a “Staging Environment” before pushing them to production.
When you’re in the draft stage of a project, you will see the environment you’re currently in, along with that environment’s API key, listed above the three tiles (“Target Audience,” “Optimization Goal,” and “Experience”). This way, you’ll know if you’re configuring a project in the production environment (if configuration changes are moved to the live stage, this may affect many live end users) or in another environment, such as your staging environment.
To configure your project in a different environment, select the dropdown arrow to the left of the “Draft” tab and choose a different environment.
Evolv recommends that you configure a project first in a non-end user-facing environment, such as “Staging,” and make it live within that environment. Once you’ve verified that the experience works as it should in this environment, you can then expose your end users to this experience by making the experience live in the production environment.
To identify environments we use unique Environment Keys.
Environment Keys allow you to match environments across platforms; ensuring that when you deploy to the “Staging Environment” in Evolv, the project is deployed to the corresponding environment in your application.
Environment Keys are applied differently in Client-Side implementations and in Full Stack implementations.