This article describes what an A/A test is and how to launch one in the Manager
What are A/A tests?
An “A/A test” is an empty optimisation that collects visitor and conversion data without rendering any changes.
You can use an A/A test to:
- Validate the Evolv snippet implementation.
- Confirm data is appearing in the Evolv dashboards.
- Check data being captured by third-party analytics tools, like Google Analytics and Adobe Analytics.
- Gauge traffic numbers and conversion rates.
- These figures help you understand how many variants you can test.
- Test context and environment-level code.
Before you can launch your A/A test, ensure you have completed the following steps.
- Install Evolv’s Experience Accelerator snippet on the target website.
- Log in to the Manager.
- Create an environment.
- Create a “Production” environment at a minimum.
- You might also like to create a QA or UAT environment.
- Environments are linked to the ID used when implementing the Evolv snippet.
- Create an audience.
- Customize the audience based on the scope of your A/A test.
- Create an event.
- Define the optimization metric for your test.
- Create an environment.
How to build an A/A test in the Web Editor
Using Evolv’s proprietary Web Editor, follow these steps to create your project.
- Install the Web Editor if you haven’t already.
- Create a new project.
- Create a new context by selecting the CREATE CONTEXT button.
- Paste in a URL into the Reference URL field, where you want the optimization to run.
- We recommend using Full Domain as the Domain Match type.
- Configure the path matching criteria based on the scope of your optimization.
- Add some additional reference URLs where you do and do not want the optimization to run - this helps you validate the page matching criteria.
- Create a variable and call it “noop”.
- The variable name doesn’t impact the test, but it’s helpful to know it’s an A/A test when reviewing the project in the Manager.
- Create a variant and call it “noop”.
- When you create a new variable, the Web Editor automatically creates a control variant.
- After creating the new variant, you should see “control” + “noop” in the variant list.
console.log('My variant is working!')
- Remove the code once you have confirmed the variant is working correctly.
- Add event tracking for your optimization metric.
- Your optimization metric is an event defined in the Manager that the optimization uses to record a conversion.
- Create a new context based on the page where you want to trigger the event.
- If your optimization metric is based on a page visit:
- If your optimization metric is based on a button click or an interaction with another element:
- The click-listener includes a function that triggers the same code that you would fire inside a context.
- Enter QA Mode to test your project.
- Save the project. This will save a .yml file that can be shared or imported to the Evolv Manager.
- Go to the Manager and import the project.
- Move the project to live when you’re ready for the A/A test to start.