- Optimizely X Web Experimentation
- Optimizely X Web Personalization
- Optimizely X Web Recommendations
THIS ARTICLE WILL HELP YOU:
- Use a thorough QA process to make sure your experiments work correctly before they go live
- Make sure that your changes appear correctly and on-time
- Make sure that visitors are included or excluded as you expect
- Make sure that events are tracking correctly
- QA an Optimizely X Web experiment or campaign (or, learn about QA for mobile experiments instead)
Before you publish an experiment or Personalization campaign live to your visitors, it's important to make sure it looks and works the way you expect. Optimizely X provides a few tools to help you QA your experiments and campaigns.
To learn more, watch this video. Alternatively, scroll down to check out our QA tools.
Basic QA tools
The Preview Tool is your first line of defense in Optimizely X. Use it to check visual changes and functionality without publishing your experiment or campaign.
The Preview Tool allows you to view all the experiments and campaigns on any page on your site; whether unpublished or live to visitors. You can check how your variations and experiences appear for different audiences and verify that events are firing correctly.
The Share Link feature helps you share specific variations with internal stakeholders.
Use the Cross-Browser Test feature to see how your visual changes look in different browsers and on different devices.
The test cookie also helps you QA a running experiment and share it with internal stakeholders, without exposing it to your visitors.
The force variation parameter, with which many Optimizely Classic customers are familiar, works a little differently in Optimizely X. Data from draft and paused experiments are excluded from Optimizely X by default, so a force parameter like
?optimizely_x=VARIATIONIDonly shows data from live experiments.
To preview draft or paused experiments, you can add
&optimizely_token=PUBLICto the force variation parameter above, or use the Share Link or the Preview Tool.
If you'd like to perform more advanced QA or you've found an issue that you'd like to diagnose, the following approaches can help:
The network console helps you verify whether events in a live experiment or campaign are firing correctly. Use it to check that metrics are tracked correctly on your Results page.
The Optimizely log helps you diagnose more difficult issues in a live experiment or campaign. It tells you whether an experiment or campaign activates on the page, whether you qualify for an audience condition, and whether changes on a page are applied.