- Check for common errors before running an Optimizely Classic experiment
- Use Diagnostic Report to check for snippet status, targeting, and experiment status
What is the Diagnostic Report?
Clicking Options > Diagnostic Report in the Optimizely Classic Editor should bring up a modal dialog that looks something like this:
The first thing you may notice is that there is a big red warning saying that the Snippet is not on the page. If that's the case, then our system was not able to recognize that the Snippet has been implemented correctly on the page. This is not always an indicator that something is broken, just that our system did not get a response from the page in time that our Snippet was on the page.
Once the Snippet is on the page the dialog should look more like this:
The report will give you more information about your experiment which can be used for analytics services, debugging, and summaries.
- Experiment Title: The title of the experiment, this is what you will see on the experiments Home page and how you will recognize your experiment. You can change the title of the experiment by just clicking on the big experiment title when in the Editor.
- Experiment ID: This is the unique ID for this experiment. It is used by our system to identify whether or not the person has seen this particular test before and can be very useful in setting up analytics integrations. This is also a very useful number to send when creating support tickets for a specific test. It should be the same as the ID in the URL when the experiment is loaded in the Editor.
- Editor URL (page loaded in the Editor): This is the page that is currently being loaded in the Editor. It does not need to be the page that the test is running on, it is simply the page that we use to create the changes that you want to execute on whatever pages you specify in the targeting conditions.
- Which Snippet ID is used on this page?: This is your project ID. Each Optimizely project has a unique ID. Our system identifies the ID of the snippet that is on the page that is loaded into the Editor.
- Does the Editor URL match my targeting settings?: In most cases when you load a page into the Editor that's the page that you want to run the test on, however sometimes you use a template page to create the test, but run it somewhere else. Or, you will create the test on a staging server but use the targeting settings to run it in production. If you want to run the test on the page that is loaded in the Editor then this should say Yes. Otherwise it is OK for it to say No.
- Experiment Status: The current status of the experiment.
This section gives you information about your variations. Each variation has a unique id that is used by Optimizely to identify which version of your page each user saw. This information can also be used to send the correct variation name to an analytics service of your choice using Optimizely, the A/B testing tool of choice.