52 results found
-
qa mode versus preview
AS an experimentation builder
I WOULD LIKE an easy way to fully qa test and share pre-production experiments
BECAUSE i want to validate all the aspects of my experiment and be able to share pre-production model with non-technical partnersFUNCTIONALITY
look for a cookie or querystring parm or hostname and from that set 'qa' to either true or false.false: take no action
true:
parms: xCode, info, remove
xCode sets qa cookie and allows you into the experiment you match the qa mode audience for
info allows for specifically coded console.logs to run
remove - removes qa cookie / environment…1 vote -
Multi-Armed Bandit Results
Can we add a traffic split visualization to the results dashboard? This would let the team verify that the bandit is working as intended and see exactly how traffic is being rerouted to the top-performing variations in real-time.
1 vote -
Word Wrap Option in Visual Editor
When editing HTML - allow the text/code in the HTML box to wrap. This makes it easier to see and edit.
1 vote -
experimentation forced re-evaluation each decision - override UPS / sticky assignment
As an experiment builder
I would like to be able to force re-evaluation of flag/campaign audiences if I want my experiment to float by user properties and am working in web or have a UPS set in feature
So that I can have transactional experiments that will match the user up properly to their current properties and not persist them into something they no longer belong in.
1 vote -
View experimentation sections from editor
It would be nice to access all the experimentation/personalization modules from the editor. In the old editor, we always had the option to click any module from th left, like metrics, shared code, targeting, etc., but now, the editor opens on top of that dashboard, and the only way to go back is by clicking 'return to setup,' which makes it a longer process to go through. It is also very slow, so I take too long checking all the sections of the experiment/personalization. I get that the editor now takes up the whole screen, but adding a drop-down to…
1 vote -
NEW Responsive Mode
I'm glad to see that the Emulator has been improved. But there are some "WTH" issues in the UX. In no particular order...
DON'T blur the content when resizing -- I frequently want to see how objects flow as the browser width changes, this exposes flaws in CSS or coding and I can't see what's happening when It's blurry.
Disabled the editor in the Emulation mode (Add one of the fingers at the top bar to disable it, next to the rotate button) - I need to engage with the site and without it disabled it think I want to…
1 vote -
Experiment Activation and associated changes
AS
an experiment builder in webI WANT TO
be able to make changes to pages associated with the experiment and not have the visitor activate the experiment when those pages loadSO THAT
I can keep changes related to an experiment together while limiting activation of the experiment to a specific page or actionUSE CASE
I have a change for a specific product display page that I want to evaluate. There are associated changes that I will need to make to the cart and every checkout page. In order to make changes to those pages to support this,…1 vote -
Developer experience
I want Optimizely’s new developer experience to support a true IDE-first, GitHub-native workflow. I should be able to do all coding in my own IDE, manage changes through GitHub, and publish through automation and CI/CD workflows without depending on the Optimizely editor for core development tasks. The editor should support preview and collaboration, not replace standard developer tooling and deployment workflows.
1 vote -
I want Optimizely’s new developer experience to support a true IDE-first, GitHub-native workflow. I should be able to do all coding in my ow
Software Engineer
1 vote -
Opal UI - is Awful!!
Opal is very difficult to see -- there's no contrast between it and a page in reporting (or anywhere Opal appears)
Recommend giving her some color! See screenshots.
1 vote -
Bug Fix
Bug Fixes on text editor (mainly shared code)
Native find on page doesn't work reliably (sometimes shows more occurrences than there actually are, doesn't jump to the place in the code when you hit enter)
- Would be great to implement that properly
Starting typing at all makes the current line jump to the bottom of the screen, which is really frustrating and quite confusing.
- Ideally just keep the scroll position what it is when you start typing.
(I'm using Chrome on Mac OS)
1 vote -
Version control
A slightly better interface of what changes have been made before committing. I know you can view history, but it's not that easy to understand. Being able to see lines of code that have changed in each of the shared js, shared css and variations would be very helpful, rather than just the number of lines changed.
1 vote -
Create a dev only toggle that won't show the website preview
I am a developer who uses Optimizely for a lot of experimentation and have to spend a lot of the time inside of the code editor. The new editor creates way too much friction. I don't need my entire website to load and then inject optimizely's scripts. This cant take multiple seconds just to change one line of code.
I would much prefer it if we could have something like a toggle on our profile where we could choose to never show the preview and just show us the variation code in a code editor. I can always copy a…
8 votes -
New Visual Editor - Carry over click tracking from Lagacy Editor
Please make sure to carry over click tracking fucntionality from Lagacy Editor. This is a fundamental function in the current legacy editor and the old legacy editor should not be phased out until this function is added to new editor
5 votes -
New Editor
Hello I have been using Optimizely for over 5 years and greatly enjoyed the product. The new editor that is slated to be fully launched greatly complicates my workflow. Most of the coding and edits I do in this editor I have to use an external editor to write and then copy them into the new Optimizely editor because of the layout and bugs in this new experience.
Here are some of the bugs I have noticed while using the new layout:
-the preview screen the editor is overlayed on distorts the elements and hides the element being edited behind…2 votes -
results page versions
AS An
experiment analystI WANT TO
save the settings of the results page including start/end time, segments, etc... and have it accessible via share link and also as a link displayed on left sideSO THAT
i can share detailed and specific findings with others easily and return to the ones i've created easily.1 vote -
Block Publish When Experiment Uses Archived Event or Metric
We found an experiment can be published even though it referenced an archived event.
Request:
Please add pre-publish guardrails so experiments cannot be published when they reference archived component dependencies.
Expected behavior:
- Block publish if any linked event, metric, or required page dependency is archived
- Show a clear warning with the archived item names
- Provide direct links to fix or replace each archived dependency before publishThis would prevent avoidable debugging and protect experiment data quality.
1 vote -
results display improvements
AS A
experiment creator and reviewerI WANT TO
improve the results page by increasing the context available for visitors that get to the page from a shared results link and may lack context into what the actual experiment is.
1. upload an image of the control and variant to the results section/page per variation or re-use the upload in variations list.
2. include hypothesis - could be input as part of the metrics screen
3. include notes - could be input as part of the metrics input. should allow inclusion of links so that references to other documentation -…1 vote -
stand-alone image upload
AS AN
experiment builder that utilizes the code editor 95% of the timeI WOULD LIKE TO
be able to upload images that are used in the variant without having to create a change in the editor to access the image uploaderSO THAT
my build process makes more sense and I don't create an unecessary change that I then have to delete after I upload the image and get the URI.1 vote -
hiding early results
AS AN
experimentation governance and operations managerI WOULD LIKE TO
be able to 'hide results' for a time by experiment to avoid devs and partners reviewing an experiment and disseminating detailed results before we have anything near conclusive. Having a project wide settable baseline would be good along with the ability to manage it at the experiment layer. Base layer should still be displayed such as visitors, split percentages, SRM, etc... Conversion rates and success metrics should not be shown until the hide time has passed. Admins should always see all metrics.SO THAT
I can avoid negatively impacting…1 vote
.png){kind=link}
- Don't see your idea?