Before you start a test, we recommend that you go over the following points in order to avoid wasting time debugging it when it’s running:
- Check that the AB Tasty tag is present on all of the site’s pages. If your site is not fully tagged, and one of your tests targets a page where our tag is not present, your modifications will not be applied to that page.
- Verify the target of your test; this is the most common error. You must have a good understanding of the various URL formats on your site to correctly configure URL targeting. Use the “Exactly matches,” “Contains,” “Regular Expression,” “Include,” and “Exclude” operators judiciously to target the correct URLs. Your target must not be too broad or too specific, depending on the desired case.
- Verify the other target options and the possible presence of excluded IPs at the testing or account level.
- Use the preview feature available in the menu of each variation to test your changes on any page or browser. Refer to this article to learn how to use this feature: Verify a test before rollout
- Reset your test to "live" on your live site by changing the target options. To do this, set your test to target only visitors who have a specific cookie (ex: check-test=1), allocate 100% of the traffic to one of your variations, and run the test. Load the page you wish to test, and delete your cookies. Use your browser’s development console to recreate the cookie that will allow you to see the test. Enter the following command in the console: document.cookie = "check-test=1"; Reload the page to see the test, and check that everything is working properly.
- If you can’t see the test with the previous method, make sure the test is correctly targeted. Use the “ABTastyTests” and “variations” commands in the browser console to do this. For more details, read this article: How do I know if a page is showing a test?
- Make sure you have properly defined the test’s objectives, whether they are click objectives (tracking action) in the editor, or URL objectives in the report interface. Remember that even though you can create URL objectives after the fact, you can’t do the same for tracking actions, which must be defined before the test is run.
If you start your test and see errors in the display, keep the following elements in mind when you are debugging:
- If you modify one of your tests while it is running, you must validate the publication of the changes by clicking on the “Publish” button at the top right of the editor. Without this validation, your changes will not be taken into account.
- After you have started a test or validated a change, it may take up to 30 seconds for the script containing your changes to be updated on our CDN. So wait at least 30 seconds before checking whether your changes have had the desired effect.
- Your browser’s cache content and your cookies may disrupt test debugging. Make sure to delete them before trying to see why your changes aren’t showing up.