- Optimizely X Web Experimentation
- Optimizely X Web Personalization
THIS ARTICLE WILL HELP YOU:
- Install the Optimizely Assistant Chrome extension
- Use the extension to assess the readiness of your site for experimentation
- Conduct more intensive QA sessions of your experiments before you launch them
The Optimizely Assistant Chrome extension gives users more insight into the nature of any Optimizely activity occurring on their site. It also provides access to a suite of easy-to-use debugging tools. Here's where to get it:
We recommend using this tool in conjunction with other QA tools and techniques to test and vet your experiments in Optimizely before you launch them.
ATTN: Optinauts - To take advantage of internal-only features, install this version instead of the public facing one linked in step 1 below.
Click here or search for the Optimizely Assistant Chrome extension in the Chrome web store.
Click Add to Chrome to add the extension to your browser.
Turn on the extension by clicking on the Optimizely logo to the right of the address bar.
Follow the prompts to login to your Optimizely account. This fetches the list of projects and snippets you have permission to view.
On Windows and Linux, press Control-Shift-J.
On Mac, press Command-Option-J.
Logging in to the Optimizely Assistant extension authorizes you to use the extension for the projects related to your last used account. If you believe the extension is warning you in error about not having the right permissions, we recommend trying the following:
- In a regular Chrome tab, log in to Optimizely with the user you will log in with via Optimizely Assistant
- Switch accounts in Optimizely to the account you'd like to use the extension with
- Authorize the new account in the Optimizely Assistant
- If you've never logged in, simply click "Open Login Pop-up"
- If you've already logged in, you can click on the "Settings" gear icon, then click "Log Out"
- Log in to Optimizely again with the user from step 1
This should authenticate you with the most recent account. If you continue to experience trouble, please reference the Support section below.
Internal Only Features:
Use an email, account, project, experiment or campaign ID to open that entity in your browser.
Use this to internally request services for customers.
Optinaut Support Form
Click in the extension or this link to learn more about forwarding requests to support.
View Unminified Snippet
View an uncompressed version of the snippet currently on the page you're viewing.
Get access to the QBR Dashboard to look at results for your customers.
Account Usage Report
See account usage for the current customer.
Click to quickly log in to Optiverse as yourself.
The chrome extension now has the ability to automatically populate the description field of new JIRA tickets with templates defined in the Optimizely Github repository: https://github.com/optimizely/jira-templates/. The JIRA templates feature can be toggled on/off in the chrome extension settings.
The Optimizely Assistant extension is a suite of utilities and tools that includes a comprehensive console log screen. Users can use it to quickly assess several important factors:
Whether Optimizely is installed on the page
What experiments and campaigns are currently active
Which variations you're bucketed into
Which Optimizely pages are currently active
One-click debugging tools
With the Optimizely Assistant, you also have access to a set of debugging tools that allow you to QA your experiment at a deeper level than the Preview tool:
Add test cookie
This allows you to create or remove a test cookie so you can target an audience to it. Essentially, this will set your experiment live in a way that ensures you are the only one seeing it.
Delete Optimizely data in current browser session
This option clears any Optimizely-related cookies or localstorage key values assigned during the current browsing session. This is helpful if you’ve already been bucketed into an experiment and you no longer want to see that variation.
Use Instant Snippet
This feature can decrease the time between saving and testing your changes when building experiments and campaigns. It does this by using the Amazon S3 version of our snippet, which usually updates right away and before our distributed CDN. This only changes the version for your local Chrome environment, so your users will continue to be served experiences from our Content Delivery Network.
Adding or swapping a snippet is useful if you need to test an Optimizely project you don't have installed in the page's code yet, but want to see how installing it would affect your site. For instance, you can use it if you want to inject the production Optimizely snippet into your site and QA experiments in your own QA environment.
Always use non-cached snippet
Checking this box enables you to immediately view changes you made in Optimizely in your browser. This can be useful for several reasons:
It typically takes a few minutes for a change to propagate from your experiment in Optimizely to Amazon’s servers and out to the CDN.
Custom snippets allow you to configure a longer TTL (time to live) for a snippet. The default setting is two minutes, but you may choose to select a longer TTL to match your users' session duration. Longer TTLs mean end users would have to fetch the Optimizely snippet from the CDN less frequently, but Optimizely users have to wait longer to see changes to experiments.
Strip X-Frame-Options header
This removes any X-Frame Options headers from your site, enabling it to load in the Optimizely Editor.
Disable console logging
Check this box to prevent logs from printing in your console.
By temporarily disabling Optimizely, you can determine which changes are influenced by Optimizely and which aren’t.
Save time by setting and using feature keyboard shortcuts. These can be set in the chrome://extensions, Keyboard shortcuts dialog.
If you experience any issues with the Optimizely Assistant Chrome extension, please contact support.