- Optimizely Classic
This article will help you:
- Figure out why you aren’t seeing your variation
- Figure out why you aren’t seeing conversions on a certain variation
- Check the integrity of your variation code
- Check the timing and scoping of your experiment
Are you experiencing any of the following issues?
Your Optimizely experiment is running, but you can’t see your variation (or certain changes you made) on your live page.
Your Optimizely experiment is running, and you see visitors on your Results page, but no conversions in a certain variation.
Usually, this problem has to do with the variation code execution timing or scoping. We’ll walk you through what that means and how to troubleshoot it.
Here’s when this article may not be for you:
You’re not seeing visitors or conversions on the Results page. Or, you’re seeing no results for any of your variations. If that’s the case, see our article on troubleshooting experiment activation.
Your variation content appears, but it's offset or appearing incorrectly. This is more likely an issue with the way the browser is rendering Optimizely's changes. Watch our video or read our article on Editor Best Practices to learn more about how to make more precise changes in the Editor.
1. Make sure the experiment is running on the page, and you're bucketed into the variation
First, confirm that the experiment is active and that you are bucketed into the correct variation. Here’s how to do that:
Make sure that your experiment is in Running status on your Home page.
Check your Diagnostic Report to make sure your snippet is installed and your experiment is live.
Optimizely provides an easy way for determining whether an experiment is running. Go to the URL where you’re running the experiment, and then open your browser's console.
Now, we’ll need to ask Optimizely, “Which experiments are active on this page?“ To do this, examine the Optimizely data object in the next two steps.
Type optimizely.activeExperiments into the console. This will return a list of all experiments currently running on the page for you.
If you see your current experiment ID, you are bucketed into the experiment. You can find an experiment ID by going to your Home page > Overview > Experiments, then click that experiment and scroll down in the right-hand panel.
If you see an empty array ‘[ ]’ then your experiment isn’t active on the page. See our experiment activation article for more information.
Type optimizely.variationNamesMap into the console. This will return a mapping of experiment IDs to variation names for all experiments on the page into which you are currently cookied, both active and inactive.
If this returns the “Original” variation for your experiment, then your experiment is running, but you’re simply looking at the Original variation.
Use the force parameter to toggle to another variation, and see whether it appears.
If there are multiple active experiments, make sure they are not colliding (in other words, making different changes to the same element on the page). If there is interference, you can make simultaneous experiments mutually exclusive.
If you see the correct Experiment ID in activeExperiments AND the correct variation name in variationNamesMap, but this hasn’t resolved your issue, continue to the next section.
2. Check for code issues
If your experiment is running on the page and you’re bucketed into the right variation, but you still can’t see some or all of your changes, the problem may be with your code.
If you run your experiment’s variation code in the console, and you see the changes correctly reflected on the page, then the issue is with timing or scoping, so move on to the next section on timing issues.
3. Check for timing issues
If you don't see any issues with experiment activation or your variation code, the issue may have to do with the order in which Optimizely runs on your page. In other words, the elements you want to change do not yet exist when the page first loads.
Here's how to fix a timing issue that causes variation content not to appear on your live site.
4. Check for scoping issues
If the previous solutions didn’t work, then you’re most likely experiencing a scoping issue. Here’s how to check:
If you see “... is undefined” errors in the console when the experiment runs, $ may refer to something else on the page. For example, there may be another library that assigns significance to $. Try switching $ to either jQuery, optimizely.$ or window.$ in your variation code, then resave the experiment and run it again.
Are you trying to reference jQuery commands which do not exist in Optimizely’s version of jQuery? Optimizely uses jQuery version 1.11.3 by default, and is also backwards-compatible with version 1.6.4. To find out what methods are available in this version, open up your console and type `optimizely.$.fn.` and a list should appear of all available methods. If you don’t see the one you would like to use, set jQuery on the window level (window.$).
Still having trouble? Reach out to the Optiverse Community for additional assistance.