Media
5 items
Description
QA Optimizely Web experiments: force variations, toggle a test cookie, emulate mobile, and view a live event log. Optimizely Web QA Helper is a lightweight panel for QA-ing Optimizely Web Experimentation campaigns on any site. Click the toolbar icon and a panel appears with everything you need to validate an experiment without digging through the console. What it does: • Force variations — see the active experiments on the page and switch a visitor into any variation. Single-page tests re-trigger in place; others reload to re-bucket cleanly. The currently loaded variation is flagged so you always know what you're looking at. • Always-current experiment list — the dropdown updates live as experiments activate or the active page changes (e.g. SPA navigation), so you never have to reopen the panel to refresh it. Active audiences for the page are shown at a glance. • Toggle a QA test cookie — set or clear your project's QA cookie with one click, with the cookie name configurable per site. • Mobile viewport emulation — preview the page at real device dimensions (iPhone, Pixel, iPad, or a custom size). Unlike a simple CSS resize, this uses the browser's DevTools emulation, so the site's responsive @media breakpoints genuinely fire and touch + mobile user-agent are applied. Your forced variation stays active the whole time. • Popup or drawer — float the panel over the page or dock it as a side drawer that pushes the page content beside it. Your preference is remembered per site. • Event log — watch a live log of Optimizely lifecycle and analytics events (campaign decisions, page activations, tracked events) alongside your own QA actions, with category filters and an expandable raw payload for each entry. Best viewed in drawer mode. Settings (cookie name, device) are remembered separately for each site. Project-wide defaults — including the Optimizely snippet variable name for projects that renamed it — are set on the Options page. The extension does its work entirely in your browser. It does not collect, transmit, or sell any data, and it talks to no external servers. Note: mobile viewport emulation uses Chrome's debugger interface, so while it's active Chrome displays a "… is debugging this browser" banner — that's expected, and clicking it off (or toggling mobile mode off) returns the page to normal.