123 results found
-
Device List Clean up - Segment
The device list under segments in Experimentation needs a clean up. I know what segments to use when analyzing experimentation results but the list is so long it looks messy and could use renaming or removal of some of them. For example, I still see Desktop (deprecated) it has been there for many years I think we can remove it if no one is using it? The other one is the Phone. We have iPhone, Other Phones and All Phones. I personally don't know what the difference is between Other Phones and All Phones. we can separate them by name…
1 vote -
New Editor -- Have option to position at top of page and control the background of the editir for visibility
Be able to have the editor at the top of the page. And add controls to alter the visual editor's color so that it can be seen easier on white pages. (Mockup uses red for example).
3 votes -
Enhancing A/B Testing with ES11 Modern JavaScript Features
I am proposing that we upgrade to ES11 to stay aligned with the latest JavaScript standards and leverage modern language features such as optional chaining, nullish coalescing, and Promise.allSettled. These enhancements significantly simplify handling complex asynchronous logic, reduce verbose and repetitive code, and improve overall readability and maintainability of our experiment scripts.
While we understand that upgrading is not strictly required to run experiments, adopting ES11 is vital for our growth and development as devs. It enables us to build more robust and reliable A/B tests, accelerate development and iteration cycles, and minimize technical debt. Keeping pace with evolving web…
11 votesThis will become a project setting option.
-
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 -
property
Today in the Optimizely UI there is a limit of 15 properties per event and we cannot delete properties that have already been added.
At the beginning some of our teams have created events with lots of properties but some were not so relevant in the end, or would be merged with other team's need.
Instead of creating new event each time a property is not necessary (added by error, archived, event reshaped) so that we can have a clean list and not be blocked from adding more properties, we would like to be able to keep existing events, not…
3 votes -
Automatic Screenshot Generation
Create an automatic screenshot generation feature. It would work like this:
When enabled (via a setting that enables a "generate screenshot" button) Optimizely will load each variation - behind the scenes - including the control and create a screenshot based on the target audience. (i.e.: laptop, desktop, tablet, mobile - using average sizes or customer's defined UX design).
The images can be updated manually if needed.
This will save tons of time doing this manually.
2 votes -
Do not remove code when changing activation targets.
Frequently I need to switch my coding / set up from a staging to a production environment. Optimizely warns me and then REMOVES all my code.
This is fine if you are a basic non-technical user.
It would be better if this was an optional change.
Possibly provide a check box and a message in the button (see screenshot) - which would allow me to change the targeting.
13 votes -
Lack of Transparency in Preview Mode
When a variation does not appear in Preview, the tool does not explain why inside the interface.
There is a log, but it requires opening the browser console and reading technical output.
A clear diagnostic message inside the Preview interface would make the QA process much
faster1 vote -
Multi-device Experiments
Most experiments need different images for desktop, mobile, and tablet. Without a shared library, the customer has to either create a separate experience per device — splitting traffic — or write CSS manually.
1 vote -
Change approval workflow in Web Experimentation
I'd like to have a change approval workflow for launching and updating experiments in Web Experimentation. Today I need to use workarounds like applying a QA audience until the experiment is "approved" by the right individuals.
1 vote -
UX Change: Run Time Calculator
Masorange has requested the run time calculator to be usable without having to create an experiment first. Once an experiment is set up, the calculator can be accessed, but it was flagged as difficult to locate and sometimes they want to use the calculator ahead of set-up. The ask is to move it to a more prominent and easily discoverable location.
4 votes -
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 -
Experiment Organization Folders
It would be great to be able to create folders in the experiments list to group items together. (Not the sort feature). Often, I have multiple experiments (separate mobile and desktop project that are the same content) - it would be useful to be able to organize these into groups - like in a file folder system. (See mockup)
7 votesWe are planning to redo some parts of the dashboard and the setup of certain things. As a lot of creation things will be moving into the new VE, we will be taking this into account and I will be reaching out when we get to the dashboard part.
-
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 -
reusable/transportable variants in web experimentation
As a user building variants in web experimentation,
I would like to be able to save and reuse variants across campaigns, pages and projects while deciding at the campaign/page level whether to allow the selected version to stand apart or be kept in sync (copy local versus linked). Localized from linked save could require a new name but retain the link to the original and allow for a button to copy the parent for resync/update needs.
So that I can more easily have a dev, qa, prod environment setup in web experimentation.
This would likely require that variants live outside…
2 votes -
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
.png){kind=link}
- Don't see your idea?