This process describes a “mini” A/A test in a sandbox project without real traffic.
If you have a real project set up with real project, then a long running A/A test is also important to perform. To do that, you will verify that the data that’s being counted in Evolv matches the data in the customer’s Analytics platform as closely as possible.
Assuming you have already followed the steps here, you now have an experiment live on a site. Next, we want to manually create some fake traffic to test that visitors and conversions are being counted.
To do this, navigate a Chrome browser to the site where the integrations are set up, and open developer tools.
Perform the following:
- Click the Network tab and refresh the page. Make sure you see an assets.js file downloaded. This should contain our console.log and confirm that we’re in the right place:
- Now you need to simulate several new visitors coming to the site. You can do this by clicking on the Application tab of the developer console and then select “Clear Storage” to reveal the “Clear site data” button. Click that button and then do a site refresh to simulate a new, unique visitor every time you do it.
- Make about 20-30 new visitors, and about every fifth visitor, navigate to the console and fire a conversion event manually:
Copy the above text into the console and press enter. It should look like this:
- Wait for 2 hours for the data to appear in the Manager.
- If the data still isn't available, wait another day before contacting Support.
- Navigate back to your live Evolv project and click on the “Live” tab. Scroll down to the section called Unique Visitors & Converted Visitors. You should see that the reported number of visitors lines up with the data you have created by manually simulating traffic.
- At this point, any 3rd party analytics tools that you have integrated should also show the traffic data you have created.