This article includes standard terms and ideas used within the Evolv product suite and optimization program.
- API Key
- Combination of Variants
- Continuous Optimization
- Experience Accelerator
- Full Stack
- Protected Environment
- Search Space
- Web Implementation
API keys help identify the environment in which an event takes place. A unique API key is automatically generated by Evolv when creating an environment. When an event occurs, the Evolv system receives both the event and the API key, and the event is logged as occurring in the appropriate environment.
Audiences are defined groups of people that can be filtered by Evolv traffic allocation systems based on their attributes. This can help you segment your users (within an account) into different categories, such as “Desktop” vs. “Mobile” users or “US” vs. “International” users. These audiences are applied to projects in the Manager, so only relevant users will enter the experiment.
Combination of Variants
A combination of variants - or simply a "combination" - is a specific set of variants that have been selected to be shown to a participant. Think of them as a single coherent user experience. Evolv uses combinations to run experiments - removing low-performing combinations and generating predicted higher-performing ones.
A context is a defined set of conditions in which project variants are applied. Generally speaking, a context is based on URL-matching rules. It can be a single page or multiple pages.
Continuous optimization allows you to add or remove ideas on-the-fly, so you don't lose precious time restarting your project over and over again. Evolv AI's algorithms respond to changes in the project's scope by initializing new ideas and removing combinations with disabled ideas, so you can keep testing and preserve the data you've collected on your best-performing ideas.
Environments are where you deploy experiments. 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 can be used to QA and verify that experiments work properly before pushing them to production.
See Environments for more detail.
An event is an instance of the user behavior that you define as being important to track and optimize, such as “Add item to cart,” “Subscribe to marketing emails,” or “Submit payment info.”
Events exist at the environment level so that they can be shared and re-used across multiple projects.
See how to create an event.
Learn more about the Experience Accelerator.
A Full Stack implementation of Evolv means that you are using Evolv to experiment and optimize digital properties beyond a front-end website. Full Stack allows you to optimize anywhere your customers interact with your brands, such as your website, iOS app, or Android app. It can also allow you to test business logic such as pricing models by hooking up other backend systems to our optimization platform through APIs.
An Organization is a way of grouping projects in the Manager. An account can have multiple organizations.
Most customers only need one Organization, which can span multiple websites, mobile apps, and other Full Stack experiences. Some customers may choose to have more than one, depending on their needs. For example, a customer or partner who manages multiple brands with no relevant traffic overlap would create a separate organization for each brand.
See how to create an organization.
A "phase" is a scoped experiment within your project. It has its own control combination, a unique experiment ID, and a clear start and end date.
Users are uniquely counted within each phase. This means a user can confirm into multiple phases and see the control in one phase and a combination of variants in another. Imagine they are micro-experiments within your over-arching project version.
When a project is launched, it starts in the Initialization phase. This phase is an AB test where each combination contains a single variant.
The purpose of the Initialization phase is to establish baseline data for each of the variants.
When all the combinations in the Initialization phase are mature, the Initialization phase stops and the Optimization phase starts.
During optimization, the system generates combinations that contain variants from different variables, and are automatically deactivated by the system if they aren't performing well.
The Comparison phase is a manually activated phase that lets you compare selected combinations against control.
A project is the user journey you’re trying to optimize, such as “Checkout process” or “email signup flow.” When you first log in to Evolv, the Projects view is loaded. Here you can get a complete overview of all the projects you’re working on within a particular account.
See how to create a project.
You can mark an environment as "protected." Protected environments allow for extra safety by restricting roles that can push changes live. ‘Manager’ and ‘Admin’ may move changes live in these environments. These are environments with real, active users, where you want to be careful about who can make changes.
Users in the Manager are one of four different roles. Roles define the permissions available to a user.
|Reader||No ability to edit anything. Just access to view Projects and their reports.|
|Editor||Users can create and update events, environments, projects, and audiences. You can launch projects in non-protected environments.|
|Manager||Same as ‘Editor’ but able to launch projects in protected environments|
|Admin||Same as ‘Manager’ but able to invite and remove users.|
See how to invite a user to an organization.
Variables are mutually exclusive sets of variants. They should be directly driven by the hypothesis that you are trying to test. If, for instance, you think users are finding the “Add to Cart Button” hard to see and you believe that increasing the contrast between button color and the button text color will make it clearer, improving conversion rates, then you might choose to create a new variable called “CTA Contrast.” Within this variable, you can create any number of variants — for instance, “black button with white text,” “blue button with white text,” and “white button with red text.” In this case, “CTA Contrast” values will vary between different experiences.
See how to create a variable.
Variants are individual ideas within a variable. For example, within a ‘Call To Action Button Contrast’ variable, you may create variants for “black background-white text,” “blue background-white text,” and “white background-red text.”
In the Manager's Draft view, you can toggle variants on and off using the toggle switch next to each variant. You can choose to hide variants that have been disabled, but you cannot delete these variants entirely.
See how to create a variant.
Every time you restart a project, it creates a new version. The first time you launch a project, that is Version 1. A new version is created when you:
- Manually stop and start the project.
- Change the audience or optimization metric.
The project history is available for you to review in the Manager.
A "web implementation" of Evolv means that you are using Evolv to experiment and optimize on the web, but not anywhere else, like in a native iOS or Android mobile app.